Date: Sat, 9 Mar 2002 13:02:07 -0500 (EST) From: Garrett Wollman <wollman@lcs.mit.edu> To: Tomas Pluskal <plusik@pohoda.cz> Cc: freebsd-i18n@FreeBSD.ORG, <freebsd-bugs@FreeBSD.ORG> Subject: Re: multibyte(3) functions not working ? Message-ID: <200203091802.g29I27A56503@khavrinen.lcs.mit.edu> In-Reply-To: <20020309130309.H5448-100000@s096-n062.tele2.cz> References: <200203082129.g28LTf644313@khavrinen.lcs.mit.edu> <20020309130309.H5448-100000@s096-n062.tele2.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Sat, 9 Mar 2002 13:10:23 +0100 (CET), Tomas Pluskal <plusik@pohoda.cz> said: > I have a simple question: according to man pages, the wctomb() function > should convert wide-char to its multibyte equivalent. When I pass a > wide-char (like any non-latin1 character, for example 0x161 in unicode) to > this function, it should return its multibyte equivalent. In the case of the ISO 8859-2 repertoire, all of the wide characters are the same as the narrow characters are the same as the multibyte characters, so wctomb() should not change the value of its argument at all. Somehow, someone has gotten the bizarre idea that wide characters are automatically ISO 10646 -- this is simply not true. (See, e.g., JIS X0208.) The wide character repertoire, like the multibyte encoding, is locale-specific. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200203091802.g29I27A56503>