I think I may have misunderstood your original email. I thought that you wanted multiple levels of fall back: nl-BE falls back to nl, falls back to en. Which is slightly more complicated than one level of fallback nl falls back to the default, English.
But either way, I trust your judgment here. Gertjan van Oosten wrote: > Hi Cameron, > > As quoted from Cameron Shorter <[EMAIL PROTECTED]>: > >> Gertjan, I didn't realise that we would want to support multiple >> language files in one application. >> > > But we always have. Look at the I18N demo, a user can dynamically > switch between the supported languages. > > >> I would have thought that if I was developing an application for a >> specific language, then I would also be required to go through and >> update all messages for that language. >> > > I don't understand; during the meeting on July 24th we wrote this about it: > > 11:11 <CameronShorter> > I assume that you would also want other languages (Eg French) to fall > back to the default (English) > > 11:12 <gjvoosten> > That is another option. Then newly added messages to the default > language would still be available in other languages without having to > add them explicitly; except they would be in English obviously. > > 11:12 <CameronShorter> > right. > > 11:13 <gjvoosten> > What I did before was simply copy all new messages to the other > languages and add an XML comment <!-- TODO: translate --> to them. > The TODO's show up in my task list in Eclipse, so an easy reminder there. > > 11:14 <CameronShorter> > The person writing the widget, and the person doing the translation > will usually be different. So there will always be widgets without > translations for certain languages. > So we should have a fallback to English. > > 11:14 <gjvoosten> > That would be most convenient. > > >> However, if you have a need, then I'm happy for mapbuilder to provide >> the functionality. >> > > It's not about *my* need for it. > > >> I assume that the config file should specify a language list: >> Ie, in your case: >> >> Language=nl-BE, nl, en >> > > What would the benefit of that be? Why not just lang=nl-BE and have > MapBuilder take care of the rest? > > Regards, > -- Cameron Shorter Systems Architect, http://lisasoft.com.au Tel: +61 (0)2 8570 5050 Mob: +61 (0)419 142 254 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ mapbuilder-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
