From owner-freebsd-hackers Thu Jun 11 15:36:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17962 for freebsd-hackers-outgoing; Thu, 11 Jun 1998 15:36:17 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from gershwin.tera.com (gershwin.tera.com [207.224.230.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA17659 for ; Thu, 11 Jun 1998 15:35:02 -0700 (PDT) (envelope-from kline@tao.thought.org) Received: from tao.thought.org (tao.tera.com [207.108.223.55]) by gershwin.tera.com (8.8.8/8.8.8) with ESMTP id PAA20328; Thu, 11 Jun 1998 15:34:25 -0700 (PDT) Received: (from kline@localhost) by tao.thought.org (8.8.8/8.7.3) id PAA12768; Thu, 11 Jun 1998 15:34:13 -0700 (PDT) From: Gary Kline Message-Id: <199806112234.PAA12768@tao.thought.org> Subject: Re: internationalization In-Reply-To: <357F75D0.CEBAC766@urc.ac.ru> from Konstantin Chuguev at "Jun 11, 98 12:14:40 pm" To: joy@urc.ac.ru (Konstantin Chuguev) Date: Thu, 11 Jun 1998 15:34:13 -0700 (PDT) Cc: itojun@itojun.org, tlambert@primenet.com, hackers@FreeBSD.ORG Organization: <> thought.org: public access uNix in service... <> X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Konstantin Chuguev: [Charset koi8-r unsupported, filtering to ASCII...] > Jun-ichiro itojun Itoh wrote: > > > > ?? I would prefer going to a full-on Unicode implementation to support > > ?? all known human languages. > > ? This was my first leaning, but I'm increasingly > > ? going toward the ISO families. > > > > Yes, iso-2022 families are quite important for supporting > > asian languages. Unicode is, for us Japanese, quite incomplete and > > unexpandable. > > > Do you mean Unicode does not cover all the CJK characters? > What is "unexpandable"? > > > ? How does the ISO2022 model work here? Isn't it the > > ? same for Japanese and Chinese? > > > > Yes, for Japanese, Chinese and Korean iso-2022 based model (euc-xx > > falls into the category) is really important. However, I > > Why not to support both ISO 2022 and Unicode? Yes, it is more difficult > to > implement. But otherwise we can lose compatibility with other systems. > > > believe that filenames must be kept in C locale for simplicity... > > > IMO, any ASCII-compatible multibyte charset will do. In that case, > if you prefer simplicity, just do not use characters with highest bit > set. > Let me pose the same question, a bit more broadly. Why cannot we support _both_ the ISO and Unicode paradigms? Are these absolutely incompatible systems? Is there some kind of ``religious-war''? Or is it simply too difficult? gary > -- Gary D. Kline kline@tao.thought.org Public service uNix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message