home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!spool.mu.edu!sgiblab!nec-gw!nec-tyo!wnoc-tyo-news!cs.titech!titccy.cc.titech!necom830!mohta
- From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
- Newsgroups: comp.unix.bsd
- Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
- Keywords: Han Kanji Katakana Hirugana ISO10646 Unicode Codepages
- Message-ID: <2628@titccy.cc.titech.ac.jp>
- Date: 6 Jan 93 19:24:56 GMT
- References: <2564@titccy.cc.titech.ac.jp> <1992Dec28.062554.24144@fcom.cc.utah.edu> <2615@titccy.cc.titech.ac.jp> <1993Jan5.090747.29232@fcom.cc.utah.edu>
- Sender: news@titccy.cc.titech.ac.jp
- Organization: Tokyo Institute of Technology
- Lines: 34
-
- In article <1993Jan5.090747.29232@fcom.cc.utah.edu>
- terry@cs.weber.edu (A Wizard of Earth C) writes:
-
- >>>This I don't understand. The maximum translation table from one 16 bit value
- >>>to another is 16k.
- >>
- >>WHAAAAT? It's 128KB, not 16k.
- >
- >Not true for designated sets, the maximum of which spans a 16K region.
-
- Uuuurrrghhhh!!! Ia Ia!
-
- >128k is only necessary if you are to include translation of all characters;
- >for a translation involving all characters, no spanning set smaller than the
- >full set exists. Thus a 128k translation table is [almost] never useful
-
- Then, don't say 16 bit. If you say 16 bit, it IS 128K.
-
- >>>This means 2 16k tables for translation into/out of
- >>>Unicode for Input/Output devices,
-
- >In this particular case, I was thinking an ASCII->Unicode or Unicode->ASCII
- >translation to reduce the storage penalty paid by Western languages for
-
- ASCII <-> Unicode translation does not need any tables. PERIOD.
-
- >>How can you "cat" two files with different file attributes?
- >
- >By localizing the display output mechanism.
-
- Wow! Apparently he thinks "cat" is a command to display content of
- files. No wonder he think file attributes good.
-
- Masataka Ohta
-