Re: Perl i18n/l10n limitations?
[email protected] (Autrijus Tang) Thu, 3 Apr 2003 02:14:50 +0800
| Newsgroups | perl.i18n |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Apr 01, 2003 at 09:35:17PM +0000, Rich wrote: > Built in support seems limited to charsets, collation, and basic number > formatting (printf etc). To query localization information, you have to > rely on POSIX functionality which may or may not be present, and the > information returned varies from platform to platform (what on earth do you > do on Win32?) This is not true. Locale::Maketext uses Win32::Locale and HTTP header parsing where necessary. > The future of perl appears to be utf8, but perlunicode states: "Use of > locales with Unicode is discouraged" - this removes perl's built in support > at a stroke. No, it says that locales.pm is to be discouraged, not using its information for interesting l10n applications. I highly encourage you get aquainted with the Locale::Maketext framework, and its built-in support for transforming things into locale-specific equivalents via language subclasses. Thanks, /Autrijus/
signature.asc
(application/pgp-signature, 187 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+iyiatLPdNzw1AaARAhpFAJ47Oa/X9UpgqgoSsE55rhXNpW8KGACgnMd6 zk++zr99Vezie3MbU7RAMu8= =aH7D -----END PGP SIGNATURE-----