Hi all,
In short: sipXconfig-web_nl.properties is not read from uploaded localization package, but from deployed sipxconfig.war file. Longer story: We are working on the Dutch translations of the webinterface. I followed the following guides: - http://sipx-wiki.calivia.com/index.php/Installable_Localization_Packages - http://sipx-wiki.calivia.com/index.php/HowTo_Create_a_Localization_Package I did the following to create an up-to-date set of files: - checked out the 4.2 branch of sipXecs - copied all the *.properties files into the correct structure - merged all the translations from http://sipxecs.sipfoundry.org/rep/sipXecs-il8n/nl into the files, so I now have: - all the properties file for 4.2 - that which was already translated for earlier versions integrated into the new files (so we don't have to translate everything) Next, I created the correct tgz file, with the structure like * region_nl * sipxpbx * stdprompts_nl In the sipxpbx dir, there is the sipxconfig_nl.jar file. So far so good, and this file can be uploaded, and most of the translations are in effect. However, the file sipXconfig-web_nl.properties (with some basic translations) is not taken from the sipxconfig_nl.jar file, but from the deployed sipxconfig.war file. It seems strange to me, that the file sipXconfig-web_nl.properties is ALSO present in the source tree of sipxconfig itself. It is the only i18n file in the sipxconfig source tree. I tried building a new sipxconfig.war WITHOUT the sipXconfig-web_nl.properties file in it but then everything is in English. Only when the sipXconfig-web_nl.properties file is overwritten in the war, my translation is used. So the questions: 1) Is this intended behavior? Then it will be necessary to rebuild the sipxconfig.war for all our installations, or to get our translations committed to trunk / branch 4.2. But the whole point to i18n is imho that everyone can easily supply their own translations. 2) Is there another way I'm not aware of? 3) Maybe the more appropriate place for this question is the sipXecs-dev mailinglist? 4) In the spirit of open source, we gladly would make our translations available, where to start? Kind regards, Eelco Brölman ----- Eelco Brölman | Sr. Product Specialist | Telecats bv | KvK Enschede 06069106 _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
