Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!uwm.edu!bionet!agate!linus!linus!linus!mbunix!eachus From: eachus@aries.mitre.org (Robert I. Eachus) Newsgroups: comp.sys.amiga.advocacy Subject: Re: Announcement--new "Unicode" standard Message-ID: Date: 27 Feb 91 04:49:50 GMT References: <39545@cup.portal.com> <37010002@hpfcdc.HP.COM> Sender: news@linus.mitre.org (News Service) Organization: The Mitre Corp., Bedford, MA. Lines: 30 In-Reply-To: koren@hpfcdc.HP.COM's message of 25 Feb 91 16:19:28 GMT Nntp-Posting-Host: aries.mitre.org In article <37010002@hpfcdc.HP.COM> koren@hpfcdc.HP.COM (Steve Koren) writes: (A lot of good information from the Unix viewpoint skipped, as you may have noticed, I am involved mostly with the ISO standards.) > In the Unix world, there has been support for 16 bit character sets > for many years now... Except in filesystem names! A number of vendors are trying to also support 16-bit character set filesystems (with tar files etc., totally unportable back to 8-bit filesystems). But a few years ago, I only knew of one company (Stratus) trying for full ISO 2022 support (mixed 1, 2, and 3 byte characters) in the names of files. Although the fille names were still limited to, I think, 30 bytes in canonical form, the switchover really slowed down a number of filesystem primitives. Do you know of anyone else who has done a good (and compatible) wide character set filename system? An interesting thought is that it might not be too difficult to build an Amiga file system (and matching shell) which provided support for say JIS X0208 or some other 16 bit set... -- Robert I. Eachus Our troops will have the best possible support in the entire world. And they will not be asked to fight with one hand tied behind their back. President George Bush, January 16, 1991