© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
I have to dig pretty deep to come up with any. So far I have:
* "A Windows project might expect its POTFILES.in or whatever to be little-endian UTF-16." But something tells me GNU gettext probably solves that by telling Windows users that it's really a proprietary binary format that just happens to look a bit like text. Which from what I understand is the kind of thing users of proprietary operating systems like to hear anyway.
* "What if a name gets normalized somewhere along the way and ends up not comparing equal to an un-normalized version of the same name?" I have no idea how likely this would be. It could be annoying if it did happen.
Where you say "support more than ASCII" in "language pack export code," I'd like to add that I'm thinking translation domains. I was only joking when I suggested non-ASCII locale names. :-)