>>>- Since the i18n code is in keel-common, it'd be really cool to
>>>share the same resources between both the Keel client and server
>>>sides, if one wanted to.
>>Yes. And it's already possible. I have begun to translate some
>>server side exception messages.
>OK...that's great, I'll start using this capability soon.
atm all the messages would be translated in the user language. One
question is: wouldn't be useful to split them in 2 sets:
- those that can be shown to the user: must be always translated
- those for the "administrator", ie messages that will go only in log
files or to console.
For this 2d set, what about a flag in the getMessage calls that force
them to be translated in a language specified by the application