At 06:15 PM 3/9/01 +0000, Hubert Figuiere wrote: >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 Ouch. Are you saying that that there's no reasonable way on those MacOS versions to do what we do on Windows and perhaps other platforms, namely: - layout a fixed dialog resource with wide-enough placeholders, and - replace them with strings loaded at runtime from some textish file? (Where textish file could be our existing .strings files, or .po files, or something else.) If so, that sounds utterly broken. Sigh. >while MacOS X provide a standard l10n mechanism. Yeah? Cool. Is it similar to any of the mechanisms we've been discussing, or something else entirely? Paul
- Re: how should we localize ... Paul Rohr
- Re: how should we localize locale names? Paul Rohr
- Re: how should we localize locale names? Tomas Frydrych
- Re: how should we localize locale names? Sam TH
- Re: how should we localize locale names? Tomas Frydrych
- Re: how should we localize locale na... Tim Allen
- Re: how should we localize loca... Tomas Frydrych
- Re: how should we localize locale names? Dom Lachowicz
- Re: how should we localize locale names? Paul Rohr
- Re: how should we localize locale names? Hubert Figuiere
- Re: how should we localize locale names? Paul Rohr
- Re: how should we localize locale na... Hubert Figuiere
- MacOS details (was Re: how shou... Paul Rohr
- Re: how should we localize locale names? Karl Ove Hufthammer
- Re: how should we localize locale names? Joaqu�n Cuenca Abela
- Re: how should we localize locale names? Tom Briggs
- Re: how should we localize locale na... Sam TH
- Re: how should we localize loca... Tom Briggs
- Re: how should we localize ... Michael D. Pritchett
- Re: how should we localize ... Tom Briggs
- Re: how should we localize ... Michael D. Pritchett
