Language-independent properties
Cantor, Scott
cantor.2 at osu.edu
Tue Nov 22 08:56:27 EST 2016
> One suggestion.
> It seems useful to comment out some properties, which are language-
> independent (e.g. 'idp.logo' and event/exception to error key mappings).
> Otherwise, deployers must modify all the property files they deployed to
> take effect.
I'm probably going to need an example to understand what's not working as intended. My assumption is you'd do it in messages/messages.properties and I thought that was the global override if you don't want the default in the system version. I probably just don't know the sequence it's actually using so if you walk me through an example it will help. Maybe there's just a problem in how it's all declared to the system.
The general question of how to handle the "official" translations is certainly open. I was thinking it made sense to put them in user land but that may be wrong and certainly isn't necessary.
We just have to set some ground rules. The installer won't remove files in system/ it doesn't know about, but we don't want to accidentally step on anything either.
I really wouldn't think you'd need to start adding more message sources though, I assumed "user" and "system" would be enough.
-- Scott
More information about the i18n
mailing list