According to Paul Rohr <[EMAIL PROTECTED]>:
> 2. If anyone knows of an efficient XP "standard" for globalizing strings,
> by all means speak up. To my knowledge, most XP products still use parallel
> platform-specific resources and tools for packaging and maintaining their
> translations.
>
> The fact that we ship the **exact same unmodified** translations on all our
> platforms is unprecedented, AFAIK. I neither know nor care what platform
> translator #42 works on because it doesn't matter. They're cleanly encoded
> in XML, so you can do whatever you want with them. I suppose I could claim
> that this makes *us* the standard, but that'd be silly, so I won't.
>
> PO files are only "standard" on desktops which happen to not run Windows or
> Mac. I haven't assessed that technology to decide whether I think it
> *should* become such a standard. I'm just claiming that it ain't no such
> animal until you or someone else stops lobbying and does the work to make it
> one.
For Mac I plan to provide a tool (probably in Perl) that generates resource file
for translations.
MacOS 8/9 will not be able to have a single binary with all languages without
lot of hacking while MacOS X provide a standard l10n mechanism.
Just my USD 1.84 advice.
Hub
