home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!mintaka.lcs.mit.edu!ai-lab!wheat-chex!glenn
- From: glenn@wheat-chex.ai.mit.edu (Glenn A. Adams)
- Newsgroups: comp.std.internat
- Subject: Re: Dumb Americans (was INTERNATIONALIZATION: JAPAN, FAR EAST)
- Keywords: Unicode ISO10646 CharacterEncoding
- Message-ID: <1ippo5INN7b3@life.ai.mit.edu>
- Date: 10 Jan 93 18:26:13 GMT
- Article-I.D.: life.1ippo5INN7b3
- References: <1993Jan9.024546.26934@fcom.cc.utah.edu> <1in2c8INNmbj@life.ai.mit.edu> <2675@titccy.cc.titech.ac.jp>
- Organization: MIT Artificial Intelligence Laboratory
- Lines: 17
- NNTP-Posting-Host: wheat-chex.ai.mit.edu
-
- In article <2675@titccy.cc.titech.ac.jp> mohta@necom830.cc.titech.ac.jp (Masataka Ohta) writes:
- >On the other hand, one can't use process code for interchange, unless
- >you are living in the closed world, because other applications won't
- >accept it.
-
- Oh, how about ASCII? It makes a pretty decent process *and* interchange
- code for English text.
-
- >You should be crazy. If you are mapping a file under possibly networked
- >environment (these days, all environments are so), you can't use multiple
- >octet fixed width code because of endeaness. Don't say signature, because
- >it makes everything complex and, thus, slow, and your reasoning to map
- >files should be for efficiency and for simplicity.
-
- Signatures are a far cry simpler than variable length encodings.
-
- Glenn Adams
-