From mboxrd@z Thu Jan 1 00:00:00 1970 To: 9fans@cse.psu.edu Subject: Re: [9fans] Plan 9 (in)security From: okamoto@granite.cias.osakafu-u.ac.jp MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="upas-nuiiuxxrfozmxljuvcjoshbuyt" Message-Id: <20010702013732.14EBA19A1A@mail.cse.psu.edu> Date: Mon, 2 Jul 2001 10:38:09 +0900 Topicbox-Message-UUID: c24db75c-eac9-11e9-9e20-41e7f4b1d025 This is a multi-part message in MIME format. --upas-nuiiuxxrfozmxljuvcjoshbuyt Content-Type: text/plain; charset="ISO-2022-JP" Content-Transfer-Encoding: 7bit Content-Disposition: inline Some says we need up to 60k chars for Japanese. However, I must say I don't know such huge number of Kanji which eceeds my memory capacity. Most of 64k chars may be in very limited use such in some ancient documents etc. :-) If "computer" must deal with all of those documents, yes, we may have to have 64k chars... The 16 bit limits will meet problem, in practical, to write person's name, some of which are named using wrong Kanji when all Japanese were permitted to have their own family name about 150 years ago. ^_^ Now, we cannot say it's wrong anymore. :-) Sorry, this is off topic. Kenji --upas-nuiiuxxrfozmxljuvcjoshbuyt Content-Type: message/rfc822 Content-Disposition: inline Received: from granite.cias.osakafu-u.ac.jp ([192.168.1.3]) by diabase; Sat Jun 30 06:11:24 JST 2001 Received: from elmo.cias.osakafu-u.ac.jp (elmo.cias.osakafu-u.ac.jp [157.16.103.2]) by granite.cias.osakafu-u.ac.jp (8.9.3/8.9.3) with ESMTP id GAA01373; Sat, 30 Jun 2001 06:10:44 +0900 Received: from mail.cse.psu.edu (postfix@psuvax1.cse.psu.edu [130.203.4.6]) by elmo.cias.osakafu-u.ac.jp (8.9.3/3.7W-01061412) with ESMTP id GAA22096; Sat, 30 Jun 2001 06:10:34 +0900 (JST) Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id 036F3199F4; Fri, 29 Jun 2001 17:10:14 -0400 (EDT) Received: from mail.noos.fr (aragon.noos.net [212.198.2.75]) by mail.cse.psu.edu (CSE Mail Server) with ESMTP id DCD811998A for <9fans@cse.psu.edu>; Fri, 29 Jun 2001 17:09:37 -0400 (EDT) Received: (qmail 12456612 invoked by uid 0); 29 Jun 2001 21:09:36 -0000 Received: from unknown (HELO SOMA) ([212.198.183.192]) (envelope-sender ) by 212.198.2.75 (qmail-ldap-1.03) with SMTP for <9fans@cse.psu.edu>; 29 Jun 2001 21:09:36 -0000 Message-ID: <001f01c100df$a4274ab0$c0b7c6d4@SOMA> From: "Boyd Roberts" To: <9fans@cse.psu.edu> References: , <3B10AAC6.996C5C63@null.net>, <3B39E316.12206DFD@ishtek.com> <3B3C833A.18E66768@null.net> Subject: Re: [9fans] Plan 9 (in)security MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: 9fans-admin@cse.psu.edu Errors-To: 9fans-admin@cse.psu.edu X-BeenThere: 9fans@cse.psu.edu X-Mailman-Version: 2.0.1 Precedence: bulk Reply-To: 9fans@cse.psu.edu List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu> List-Archive: Date: Fri, 29 Jun 2001 23:08:26 +0200 > 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 iirc chinese (mandarin) has some 60k chars. not that they're all used, but for completness's sake yer gonna need 32 bits. btw: to survive in japan you need ~2k chars, but most newspapers get by with ~6k. --upas-nuiiuxxrfozmxljuvcjoshbuyt--