Article View: comp.fonts
Article #674Re: font encoding morass
From: Michael Wang
Date: Fri, 21 Aug 1992 17:31
Date: Fri, 21 Aug 1992 17:31
22 lines
1617 bytes
1617 bytes
In article <1992Aug21.054826.4016@adobe.com> delahunt@adobe.com (Jim DeLaHunt) writes: >Well, we weren't talking about this kind of document portability before. >Unicode only pretends to provide portability of *plain text* across >platforms. Think of it as having the advantages and limitations of plain >ASCII text. Formatting and ligature substitution systems like Line Layout >Manager are (as far as I understand) platform-specific, but can support >multiple encoding schemes. The PostScript language can describe formatted >documents in *final form* across platforms. Well, perhaps the intent of Unicode is only to encode plain text, but if you look through some of the glyphs it does encode, I would argue they are there for typographical "richness". For example, look at range U+2100 -> U+214F. These are "letterlike" symbols including some black letter characters and some script characters. Or look at U+2150 -> U+218F. These are additional number forms including roman numerals. Then we have U+2460 -> U+24FF which are the enclosed alphanumerics. And of course in range U+2700 -> U+27BF we have all of ITC's Zapf Dingbats. -- Michael Wang mmwang@adobe.com
Technical Details
Message-ID:
<1992Aug21.173143.25986@adobe.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!decwrl!adobe!mmwangReferences:
<71384@apple.Apple.COM> <1992Aug20.013444.6313@adobe.com> <1992Aug21.054826.4016@adobe.com>Show Full Headers
Complete Article Headers
Newsgroups: comp.fonts Path: arc1-ca.pugleaf.net!sparky!uunet!decwrl!adobe!mmwang From: mmwang@adobe.com (Michael Wang) Subject: Re: font encoding morass Message-ID: <1992Aug21.173143.25986@adobe.com> Sender: usenet@adobe.com (USENET NEWS) Organization: Adobe Systems Incorporated References: <71384@apple.Apple.COM> <1992Aug20.013444.6313@adobe.com> <1992Aug21.054826.4016@adobe.com> Date: Fri, 21 Aug 1992 17:31:43 GMT Lines: 22