> Thank you. Since my primary translation is U.S. English and my primary > audience is the same, then it would make sense that I wouldn't need to > supply a "en_US.po" file since it defaults to this in the same way that > French from France would only need "fr.po" and that "fr_FR.po" would be > redundant. I appreciate your explaining this.
Indeed. You would maintain most of your message strings in en.po, and only if you found that for a particular key there would be a U.S local term be more suitable than the generic term, you would maintain this particular key in the en_US.po file. Same with en_GB. (E.g. you would map a certain key to "french fries" in en_US, and to "chips" in en_GB :). T. ------------------------------------------------------------------------------ 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
