[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

*To*: "Berthold K.P. Horn" <bkph@ai.mit.edu>*Subject*: Re: Unicode and math symbols*From*: "Martin J. Duerst" <mduerst@ifi.unizh.ch>*Date*: Mon, 3 Mar 1997 11:39:47 +0100 (MET)*cc*: C.A.Rowley@open.ac.uk, BNB@math.ams.org, tex-font@math.utah.edu*Flags*: 000000000000*In-Reply-To*: <199703022246.RAA09318@kauai.ai.mit.edu>*Sender*: mduerst@enoshima

On Sun, 2 Mar 1997, Berthold K.P. Horn wrote: > The correct solution is to not have the system do the conversion > between character codepoints and glyph indices, but to leave that > to the font (which should know best). Quickdraw GX (from Apple) and > TrueType open are approaches to this, although I would prefer > it if the knowledge of the font about the mapping were available > as methods (in the OO sense) and not just as tables. > > I don't agree with this. GX hides under hood much of what a > typesetting application needs to know about (such as ligatures). > The main idea behind GX is to add some apparent typesetting capabilities > to dumb appications. Useless for TeX. I just said that GX and TT Open are going in the right direction. But I agree that they don't go far enough. I already say what I think is needed, see my other mail for more details about this. Regards, Martin.

**Follow-Ups**:**Re: Unicode and math symbols***From:*"Berthold K.P. Horn" <bkph@ai.mit.edu>

**References**:**Re: Unicode and math symbols***From:*"Berthold K.P. Horn" <bkph@ai.mit.edu>

- Prev by Date:
**Re: Unicode and math symbols** - Next by Date:
**Re: Unicode and math symbols** - Prev by thread:
**Re: Unicode and math symbols** - Next by thread:
**Re: Unicode and math symbols** - Index(es):