[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Newsgroup Home]
|
[news.eclipse.platform.rcp] Re: Getting i18n setting from database
|
You probably need to separate out the messages that are displayed intrinsically to the client (e.g. menu items etc.) from those that are returned by the server.
I'm surprised that your server sends back any translated messages though; usually, you'd expect for some kind of code to be returned that could be appropriately understood by the client. For example, HTTP's 404 code is sent back from the server to indicate a missing resource, and then translated by every client into Not Found (or something similar). Why can't you do the same here? It would seem reasonable in this case to return the message using the same message key as the translations that you're maintaining on the client, and in addition, will avoid problems in the future where the NL setting for the server is different from the client.
The only danger is that you may receive a message key for which you have no translation; in which case, you've got the same options as before which is to display the message key or TO_TRANSLATE or some generic error message like 'A message was received but we are unable to translate it into your language'.
Alex.