Quote:
|
Originally Posted by KevinH Max, Thanks for your note. We've done a bit of thinking about how to better solve the localization issue as well. Our current plan (and the reason I've been warning folks that a change is coming) is to use Java property files as the base resource for the strings. We chose this path since it has worked well for java folks for over a decade and most programmers/localizers these days are familiar with them. We get sparse overrides for free and have a simple servlet that generates the . js files automatically. Didn't involve any changes to our . js code and was quite simple to implement if you already knew java property files. I know this doesn't address all your concerns and recommendations but we can revisit this if localizers really have trouble. Early this week I'll post the current property files so you can take a look. We'd appreciate your input and comments. |
OK, no problems.
I'm waiting for next release, for the moment i'm trying to have a italian/spanish environment working and best localized.
best,
MaX