On 2/24/16, 3:26 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Ok ... now this is strange. I found out that my resource bundle generator >needed a small change. >The original appended the messages to the messages_en.properties. So the >generated output is automatically appended to the stuff checked in in the >messages_en.properties from the src/main/resources directory. That sounds >sensible. > >But when comparing the output of the en with the other languages I could >see that these all contain internationalized resources for all of the >resources the messages_en.property does after adding the generated ones. >I had no idea where they came from. Unfortunately it seems as if the >other resources contain values for both the static and the generated >properties. That looks really ugly. So if we add a new Problem type, the >English properties is extended, but the others have to be manually? Is >there a test to demonstrate which other properties need internationalized >values? Otherwise I think we could get into serious trouble when running >Falcon on a machine with "fr", "jp" or "zh_CN" as locale. Probably the >compiler will generate NullPointerExceptions internally and produce >nonsense-error messages as it did for me. I expect that missing localized errors isn't handled properly, especially now at Apache where we don't have a dedicated localization team like we did at Adobe. I have always wondered if it is truly valuable to have the compiler error message localized. All of the other keywords in the language are effectively English. Should we just lock it down to English for now? -Alex
