Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!mcsun!ukc!ox-prg!culhua!Damian.Cugley From: Damian.Cugley@prg.ox.ac.uk (Damian Cugley) Newsgroups: comp.text.tex Subject: Re: Proposed Computer Modern 256-char sets (Re: ISO Latin 1) Message-ID: Date: 8 Oct 90 15:15:13 GMT References: <8691@jarthur.Claremont.EDU> <8770@jarthur.Claremont.EDU> Sender: news@prg.ox.ac.uk Organization: Oxford University Computing Laboratory, UK Lines: 22 In-reply-to: dhosek@frigga.claremont.edu's message of 1 Oct 90 17:46:50 GMT From: Hosek, Donald A. Message-Id: <8770@jarthur.Claremont.EDU> > Umm, did you know that it's possible to use TeX fonts on a > Macintosh like any other font? Well in that case you'd have to use the standard MacEncoding in order to get Mac's KeyCaps routine to get the quotes, ligatures etc. in the right place? Or can KeyCaps be reconfigured for different encodings? Here a "chars 32-126 are as ASCII" approach is inevitable because almost all the keyboard keys stand for themselves (I'd still cheat and use '` as quotes not quote/backquote myself, except in the tripewriter font). This is an example of the fundamental problems with having a fixed encodoing for characters built into a font - and is one of the places where PostScript wins over TeX hands-down. A given PostScript font can be rearranged in whatever order you like because glyphs are acessed using symbollic names; with TeX you'd have to build into the METAFONT code the necessary admin to produce characters in an ASCII-style ordering. Damian