I like to have a complete XML file for every language just for one reason: It is way more easy for people to translate the application if they have a single file with all labels. If you have to search across 2 files many people will never notice that the file is simply not complete and we need another Language Editor to make sure internationalization can be done easily.
Sebastian 2012/11/27 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > I saw your commit :) > I thought of modifying the logic of our labelDAO: > ever > fill DB with missing labels (if any) > or retrieve English labels if localized ones are absent > > what do you think, is it a good idea? > > > > On Tue, Nov 27, 2012 at 10:11 AM, [email protected] < > [email protected]> wrote: > >> Hi Maxim, >> >> I was kind of tired to manually update all language files whenever I add >> a new label. >> So I wrote a JUnit test that does sync the labels from one language file >> and fills that label up in all XML files. >> >> See: org.apache.openmeetings.test.labels.FillLabels >> >> It will read first the masterLangFile and then all other XML files and >> fill it. >> Practically I have put "english.xml" in the masterLangFile, so you can >> add new labels to the english.xml, run the test, refresh Eclipse and all >> other lang files should have the new label(s) too. >> >> It is also possible to replace existing other labels, just see the array >> variable: replaceIds. >> All Ids, in that array will be synced from the masterLangFile to all >> other languages. >> >> The Junit test also does some tests, for example it fails if it detects >> duplicate labelid's. >> >> Sebastian >> >> -- >> Sebastian Wagner >> https://twitter.com/#!/dead_lock >> http://www.webbase-design.de >> http://www.wagner-sebastian.com >> [email protected] >> > > > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
