Pierre van Rooden wrote: > Michiel Meeuwissen wrote: > >default locale is not necessary en, so _en files must be available too. > >(perhaps the normal .properties files can be removed?) > > IIRC the normal .properties files are used if no file can be found for > the given locale. > So even if you have a system with, say, default locale 'es', if you > specify 'en' as a locale, and it can't find the _en file, it should use > the normal property file instead. > So why do we need an _en file if the default file contains this value > and the system defaults to it? It only sounds like more work. > And leaving the normal property files out means that systems with > different default locales fail to load even the default (english) > values, unlesh you explixitly specify 'en' or make custom localized > property files. > Anyway, I *thought* that's how it worked. If not, maybe you can elaborate? >
I thought that too, but I had a failing test-case which was solved by this. I thought the only thing which could differ was my locale, because the case did not fail on another system. I tried this, it solved the problem. Coming to think of it, may be it could have been fixed in 'org.mmbase.util.SortedBundle' too. This is a wrapper around a ResourceBundle to ensure fixed order (which a ResourceBundle has not). I will look into that later then. Michiel -- Michiel Meeuwissen mihxil' Peperbus 107 MediaPark H'sum [] () +31 (0)35 6772979 nl_NL eo_XX en_US _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
