Community
Participate
Working Groups
I'm opening this bug to start a discussion on whether this is a problem which needs to be addressed. Translating a cheat sheet which contains commands or actions requires the translator to know which parameters should be translated and which should not. For example in the command below all the parameters should be translated <command returns = "result" serialization="org.eclipse.ui.dialogs.openMessageDialog(title=Select View,buttonLabel0=Package Explorer,message=Select a view ,buttonLabel1=Search View)"/> In the next command the parameter should not be translated. <command serialization="org.eclipse.ui.perspectives.showPerspective(org.eclipse.ui.perspectives.showPerspective.perspectiveId=org.eclipse.jdt.ui.JavaPerspective)"/> While in these two cases the translator might be able to correctly guess which parameters required translation there could be cases which were harder to determine which could result in over translation or under translation. Do we need to establish a convention for passing hints to the translators about which parameters should be translated? If so support shhould be added to the authoring tools.
One idea being considered for 3.3 is the ability to externalize strings into properties files. Not just for cheat sheets but for all UA XML file formats.
Created attachment 51189 [details] Results of running German version of hello world cheat sheet I just did some testing on Eclipse 3.2 using different locales. I will attach examples of the different kinds of problems that can occur. In this case the cheat sheet could not be loaded. I used M20060629-1905
Created attachment 51190 [details] Hello World Cheat sheet, French Translation M20060629-1905 In this case some parts of the cheat sheet, such as the names of the steps were not translated.
This is a variant of Bug 102366, which has been resolved, so I'll consider this bug to be fixed. Bug 102366 did not address commands but the translation hint I added covered both commands and actions. *** This bug has been marked as a duplicate of bug 102366 ***
