Thanks - that's the right direction to go! There are still so many products out there that refuse to acknowledge that multibyte / wide characters have been a necessity and reality for a long time, and not supporting multibyte strings is the dead end of all such products.
Best regards, Pat Willener Cincom Systems (Japan) Ltd. -----Original Message----- From: Micah Cowan [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 05, 2008 04:26 To: Hrvoje Niksic Cc: Wget Subject: Internationalization [Re: Prerelease: Wget 1.11.1-b2080] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Micah Cowan wrote: | As to wchar_t and mbtowc: I'm curious how many systems we're still | trying to support actually lack these, given that they've been around | since the very first C standard? Note that, as mentioned in the release announcement for GNU Wget 1.11, internationalization is about to become a relatively high priority for Wget, given that IRI support (and, in particular, IDNs) are quickly becoming a concern. Not too much beyond that, Wget may need to do internal transcoding of documents that are not in an ASCII-based format (Wide-character encodings such as UTF-16, or shift-based encodings such as ISO-2022-JP). Given these things, it seems likely that Wget 1.12 and/or beyond will probably not support platforms that lack the basic wide-character and multibyte-character support that was present in the first ISO C standard. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHp2a57M8hyUobTrERApEcAKCOPXO/b9YgQOPv+yRChA38FLiGSwCfd+Rw 6bzVCLaN9V5rhOA0Mck233A= =FRt1 -----END PGP SIGNATURE-----
