The "Messages libraries" section of the Derby Developer's Guide says that Derby "supports" a number of locales:
- derbyLocale_de_DE.jar German
- derbyLocale_es.jar - Spanish
- derbyLocale_fr.jar - French
- derbyLocale_it.jar - Italian
- derbyLocale_ja_JP.jar - Japanese
- derbyLocale_ko_KR.jar - Korean
- derbyLocale_pt_BR.jar - Brazilian Portuguese
- derbyLocale_zh_CN.jar - Simplified Chinese
- derbyLocale_zh_TW.jar - Traditional Chinese
In fact, in addition to these locales, Derby provides localizations for some others (see http://wiki.apache.org/db-derby/LocalizingDerbyMessages):
- derbyLocale_cs.jar - Czech
- derbyLocale_hu.jar - Hungarian
- derbyLocale_pl.jar - Polish (except for sysinfo)
- derbyLocale_ru.jar - Russian
The term "supports" may overdescribe the situation. Effort has been put into keeping some of these localizations up-to-date, although I don't think that any systematic effort has been put into verifying that any of our non-English locales are really current. Some locales have not been updated recently. Here's the list of locales which received fresh localizations in 10.4 (see http://issues.apache.org/jira/browse/DERBY-3804):
Traditional and Simplified Chinese
This means that the Developer's Guide is claiming that Derby "supports" Portuguese, even though it's clear that those localizations are drifting out of sync with the English messages.
We should correct the "Message libraries" section:
1) We should decide what we mean by "supports". This term could mean
a) Derby provides SOME localized messages for the locale or
b) The localizations are being actively maintained
2) Based on what how we resolve (1), we should add or subtract locales from the list in "Message libraries"
My gut feeling is that we should list all of the locales for which we provide localizations and this section should note that some locales are maintained better than others.