[jbosstools-dev] More i18n questions

[Sean Flanigan]

Well, I haven't externalized that text yet.  (I'm not a translator, so I 
don't actually translate anything myself.)  If someone chooses to use 
JBoss Tools in (say) Japanese, he/she might expect code generators to 
use Japanese where possible, so that the generated code will be more 
readable.

(I'm not talking about translating the Java keywords in the generated 
code, but the embedded strings, comments and maybe variable names.)

However, the Japanese version of the Hibernate reference guide seems to 
use all-English examples:

http://www.redhat.com/docs/manuals/jboss/jboss-eap-4.2/ja_JP/html/Hibernate_Reference_Guide/Part_1___The_first_Hibernate_Application-Startup_and_helpers.html

What's good for the goose is good for the gander.  I'll mark them as 
non-translatable.

Sean.

On 01/07/09 14:31, feng.qian wrote:
> In the ClientSampleCreationCommand.java ,the english text should not be
> translated to other language.
> Why do you translate them?
>
>> Do you think it makes sense to translate English text embedded in
>> template code?
>>
>> eg in the examples/ module,
>> or in a class like
>> /org.jboss.tools.ws.creation.core/src/org/jboss/tools/ws/creation/core/commands/ClientSampleCreationCommand.java
>>
>>
>> It's not difficult to externalize the English text, but I suppose
>> there could be a problem if a translator used a non-ASCII character
>> and the compiler uses the wrong character set.  Or if the translator
>> chooses a variable name which isn't a legal identifier in Java.
>>
>> Is it worth the trouble (and extra testing)?
>>
>


-- 
Sean Flanigan

Senior Software Engineer
Engineering - Internationalisation
Red Hat