home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.std.internat
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!news.acns.nwu.edu!merle.acns.nwu.edu!hpa
- From: hpa@merle.acns.nwu.edu (H. Peter Anvin N9ITP)
- Subject: Re: Radicals Instead of Characters
- Message-ID: <1993Jan22.151917.12160@news.acns.nwu.edu>
- Sender: usenet@news.acns.nwu.edu (Usenet on news.acns)
- Nntp-Posting-Host: unseen3.acns.nwu.edu
- Reply-To: hpa@nwu.edu (H. Peter Anvin)
- Organization: You must be kidding!
- References: <MELBY.93Jan21144739@dove.yk.fujitsu.co.jp> <1jlngtINNqnk@life.ai.mit.edu> <ISHIKAWA.93Jan22200347@ds5200.personal-media.co.jp>
- Date: Fri, 22 Jan 1993 15:19:17 GMT
- Lines: 23
-
- In article <ISHIKAWA.93Jan22200347@ds5200.personal-media.co.jp> of comp.std.internat,
- ishikawa@personal-media.co.jp writes:
- > I just need some clarification or opinions from netnews readers.
- > In article <1jlngtINNqnk@life.ai.mit.edu> glenn@muesli.ai.mit.edu (Glenn A. Adams) writes:
- >
- > Keep in mind that there is no necessary relation between a 16-bit character
- > encoding and a 16-bit font...
- >
- > Is the last statement understood by many netnews readers, and is it
- > shared by UNICODE proponents? I had a vague understanding about this,
- > and yet it was a revelation to read such a clear statement.
- >
-
- This is indeed shared by UNICODE proponents, at least it better be!
- There are scripts within UNICODE, such as Arabic, that *cannot* be
- represented 1:1 between UNICODE points and glyphs (although there *is*
- a set of glyphs in the Compatibility Zone, it only covers the basic
- Arabic language, not the complete coverage of the script.) Arabic
- characters can have up to four forms: standalone, initial, medial and
- final, plus that some ligatures are apparently mandatory. In
- addition, there are diacritical marks to be accounted for, just as in
- Latin script.
-
-