-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Jun 29, 2006, at 12:58 PM, emf wrote:
We will use UTF-8 exclusively on WUI, with the caveat that I will be sniffing any charset information contained in emails and attempt displaying (individual) emails with the charset referenced.
I'm sure this was ages ago, but IIRC, UTF-8 was discussed at some point and the decision was made not to use it because it's support was pretty spotty in the browsers of the time. I'm sure this has improved vastly now and UTF-8 makes the most sense.
Pretty please, I need to set up a copy of someone's translation toolchain; can someone using OS X or Linux as their work operating system work with me to get an *exact* replica of their toolset?
I want to make translating as painless as possible but from what I can tell so far gettext is very low level and I suspect that people use more than just it to translate... am I right?
Have you gotten any love on this issue Ethan? To be honest, I'm not a translator (heck, I barely speak English despite years of at least 2 other languages in high school and college :). When I was working out the basic i18n support I implemented a stupid rot13 translation using nothing more sophisticated than XEmacs and the gettext tools.
Please, can any i18n'ers help Ethan out with a better tool set?