Yes, that's the whole idea of the fall-back handling. For all *common* translations you use the en.po. For all *special* translations you put them in the specialized territorial .po file. So your en.po could carry like 99% of all translations while e.g en_US and en_GB (and en_CA and so on) would only carry the 1% that are special to them.
If then the browser of a user sets the locale to, say, en_GB every key will be first looked up from en_GB.po. For most of the keys there will be no translation in en_GB so it will be looked up from the more "general" en.po. So all the special translations will be picked up from en_GB, while for all others the translation will fall through to en.po. Does that make sense? T. > Wait! Are you saying that if I use a word such as "check" in the > english > version "en.po" file but require a "cheque" for CA and GB that I only need > to provide a translation for just those keys and not the entire set of > words > and phrases from the application? If so, that would be awesome and I > wouldn't need to do all of the work that I am currently doing for each > English speaking country we cater to. > > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/Localization-Help-tp7583926p7583936.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by Windows: > > Build for Windows Store. > > http://p.sf.net/sfu/windows-dev2dev > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
