From owner-FreeBSD-tech-jp@jp.freebsd.org  Thu Dec 28 11:13:30 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id LAA25966;
	Thu, 28 Dec 2000 11:13:30 +0900 (JST)
	(envelope-from owner-FreeBSD-tech-jp@jp.FreeBSD.org)
Received: from mfo00.iij.ad.jp (mfo00.iij.ad.jp [202.232.2.117])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id LAA25959
	for <FreeBSD-tech-jp@jp.freebsd.org>; Thu, 28 Dec 2000 11:13:29 +0900 (JST)
	(envelope-from okuyamak@dd.iij4u.or.jp)
Received: from dd.iij4u.or.jp (dd.iij4u.or.jp [210.130.0.14])
	by mfo00.iij.ad.jp (8.8.8/MFO1.3) with ESMTP id LAA00440
	for <FreeBSD-tech-jp@jp.freebsd.org>; Thu, 28 Dec 2000 11:13:29 +0900 (JST)
Received: from localhost (wyoming.yamato.ibm.com [203.141.89.171])
	by dd.iij4u.or.jp (8.8.8+2.2IIJ/4U1.1) with ESMTP id LAA13245
	for <FreeBSD-tech-jp@jp.freebsd.org>; Thu, 28 Dec 2000 11:13:28 +0900 (JST)
Date: Thu, 28 Dec 2000 10:47:29 +0900 (JST)
Message-Id: <20001228.104729.74750261.okuyamak@dd.iij4u.or.jp>
To: FreeBSD-tech-jp@jp.freebsd.org
From: Kenichi Okuyama <okuyamak@dd.iij4u.or.jp>
In-Reply-To: <20001227220201.A62912@nagual.pp.ru>
References: <3A4A35BA.FB9856C0@FreeBSD.org>
	<20001227124812.D28522@peorth.iteration.net>
	<20001227220201.A62912@nagual.pp.ru>
X-Mailer: Mew version 1.95b91 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=koi8-r
Content-Transfer-Encoding: quoted-printable
Reply-To: FreeBSD-tech-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: FreeBSD-tech-jp 3004
Subject: [FreeBSD-tech-jp 3004] Re: Unicode support in cd9660 [patch
 for review]
Errors-To: owner-FreeBSD-tech-jp@jp.freebsd.org
Sender: owner-FreeBSD-tech-jp@jp.freebsd.org
X-Originator: okuyamak@dd.iij4u.or.jp

>>>>> "=E1=FE" =3D=3D =E1=CE=C4=D2=C5=CA =FE=C5=D2=CE=CF=D7 <ache@nagua=
l.pp.ru> writes:
=E1=FE> This is general method of telling kernel how to convert names f=
rom Unicode
=E1=FE> to any local charset, not particulary to Russian one. Anybody f=
eel free to
=E1=FE> add their own single bytes charsets tables.

I recommmend not to do so.
There have been enough of "single byte support only" stuffs that
happened to be cause of later troubles.

As I mentioned before, The very key reason why single byte support
only happened to be cause of later troubles, is because we stint
bits. We stint bits so that we can fill everything within single
byte, and as a result, we find no way to recognize one single byte
supportive from other, and even if we could, we can not tell if it's
case of multi-byte codeset or not.

This tells us very important information.


"If you can add more bits, Always add them".
"If you can think about more bits, always add them".
"NEVER think about only single byte world".
---- =

Kenichi Okuyama@Tokyo Research Lab, IBM-Japan, Co.=
