Community
Participate
Working Groups
Further to some email this weekend. Richard has tried placing the translated webapp.properties in the following places: 1) fragment *.jar (just like all other nlsed .properties files) 2) In the fragment plugin directory itself. Unjared and named webapp_es.properties (spanish example) 3) In the <plugin>/nl/es/webapp.properties None of these worked. So please let us know where you expect the translations to live and look at the code that is supposed to pick up these translations.
Dean, 3) should work fine. 2) should also work if webapp.properties does not change its name (i.e no language suffix added). I just tested a number of variations for the da_DK locale (needed to test a different bug), and the "translated" webapp.properties was picked up correctly. The rules are: - translated webapp.properties should keep the same name (no webapp_es.properties). - the translated file should be put in the appropriate localized fragment, or in the main plugin in any of the nl, nl\lang or nl\lang\country directories. I will leave the bug open until you verify it.
Thanks Konrad, I will verify. What build did you test it on? (I think this may be related to a backwards compatability feature that Core put into Friday's build.). Did you test it on a build older or later than Friday? Thanks
I tested with todayøs nightly build, 0610.
Only #3 seems to work on the 0610 build but this is perfectly acceptable. I have changed the builder to compensate and sent the new builder to Richard.
