From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu From: "Douglas A. Gwyn" Message-ID: <3B3C833A.18E66768@null.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , <3B10AAC6.996C5C63@null.net>, <3B39E316.12206DFD@ishtek.com> Subject: Re: [9fans] Plan 9 (in)security Date: Fri, 29 Jun 2001 13:57:18 +0000 Topicbox-Message-UUID: c150063e-eac9-11e9-9e20-41e7f4b1d025 Alex Danilo wrote: > So, yes 16 bits is not enough. However 32 bit representations are > discouraged - UTF16 is the way to go if you have to leave UTF8. Actually that is highly debatable -- it depends on the requirement. For a "rune" or wchar_t, since 16 bits are not enough to provide the required functionality, 32 bits is the obvious choice. UTF16 encodes some characters as 2 consecutive units, which is foreign to the notion of rune or wide character.