Date: Tue, 13 Jan 1998 12:00:51 +1100 (EST) From: Andrew Kenneth Milton <akm@mother.sneaker.net.au> To: tlambert@primenet.com (Terry Lambert) Cc: jfieber@indiana.edu, daniel_sobral@voga.com.br, hackers@FreeBSD.ORG Subject: Re: Wide characters on tcp connections Message-ID: <199801130100.MAA20601@mother.sneaker.net.au> In-Reply-To: <199801122345.QAA23572@usr08.primenet.com> from "Terry Lambert" at Jan 12, 98 11:45:46 pm
next in thread | previous in thread | raw e-mail | index | archive | help
+-----[ Terry Lambert ]------------------------------
|
| > > I'd like to know if there is any provision on TCP protocol for
| > > wide-character tcp streams.
| >
|
| We can argue about whether ISO 10646 specified wchar_t should be
| 16 or 32 bits... however, it's 16 bits on Windows 95/NT, and so
| if we ever want to interoperate, we should be 16 bits as well.
They didn't specify, they recommended that it be 16 bits internally. HPUX and
Solaris have it as a 32 bit int, even making code sharing with NT
(wow Microsoft did something correctly) a chore. They didn't specify
so that vendors could use a native word size to keep the implementation
quick-ish.
Yes I've read the ISO standard (actually the Australian Standard which
is identical to ISO 10646, but, cheaper to buy by an order of magnitude).
I've also read the Unicode Version 2 book.
Version 2 has a 32 bit UNICODE type as well (geez some people are going
to be annoyed that their language isn't accepted into Unicode, but,
Klingon was).
--
,-_|\ SneakerNet | Andrew Milton | GSM: +61(41)6 022 411
/ \ P.O. Box 154 | akm@sneaker.net.au | Fax: +61(2) 9746 8233
\_,-._/ N Strathfield +--+----------------------+---+ Ph: +61(2) 9746 8233
v NSW 2137 | Low cost Internet Solutions |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199801130100.MAA20601>