On 10/02/2010 04:36 PM, Ricardo Pérez López wrote: > Interestingly, my chrome.manifest files seems to be already right, i.e. > they contains "es-ES" and not "es_ES":
[...] > So maybe my issue is not the same as yours and language-pack-es is not > affected by this bug. Actually, my issue is about having > "[chrome://global/locale/intl.properties]" instead of right language > names "es-es", "es", "en-us", "en". Arne, what do you think? > That is, because es-ES is one of those locales, where Launchpad stores it as 'es' without country code. Those get matched to es-ES correctly, because those mappings are hardcoded in the po2xpi script. Any other es_* locale will be affected, i.e. any locale, where Launchpad stores it as ll_CC and not just ll. About your chrome settings, I don't know, because we don't set them in the language packs. That setting must come from somewhere else. What I'm wondering though is: this bug has been in po2xpi forever! How come no one reported it earlier? -- Arne Götje (高盛華) <a...@linux.org.tw> PGP/GnuPG key: 1024D/685D1E8C Fingerprint: 2056 F6B7 DEA8 B478 311F 1C34 6E9F D06E 685D 1E8C Key available at wwwkeys.pgp.net. Encrypted e-mail preferred. -- Language variants don't work in Firefox because the language codes are separated with an underscore rather than a hyphen in chrome.manifest https://bugs.launchpad.net/bugs/632760 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
