[news.eclipse.platform.rcp] Re: Getting i18n setting from database

[jsetya@xxxxxxxxx (Setya)]

Alex,

> There's three aspects to the translations:

> 1) Picking a key to use (e.g. com.foo.FileMenu)
> 2) Picking a default translation (e.g. File)
> 3) Generating translations for 'File' in other languages

> You'll need to decide on at least 1) whilst developing your program, even if 
the other translations don't exist yet. As for the default translation, people 
often use English or their first language, and then supply translations for 
others at a later stage. If you don't want to do 2) at the same time as doing 
1) then you could always use either the key itself (e.g. com.foo.FileMenu) or 
a known token (e.g. TO_TRANSLATE).

> Realistically, I don't recommend the use of the database to generate the 1) 
or 2) steps above. You should have this compiled and checked in to your 
version control system; instead, use the database to generate the separate 
translation files for each language as you need them (and once you've done 
that, check the translated files in too). 

Thank you very much for your advice & links.

On the client side of our application (GUI) we often need to display 
messages that come from the server side (EJB). 

In this situation we have to options :
1. Have the server return the translated messages which means we have to 
maintain the translation in client & server.
2. Have the server return only the message key and let the client 
translate the message through the key so we only have to maintain the 
translation at the client, but still we have to maintain the key at both 
sides.

Which approach is the best ?

Regards,

Setya