[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: checksum inconsistencies for virtual postscript fonts on CTAN
- To: Sebastian Rahtz <firstname.lastname@example.org>, email@example.com
- Subject: Re: checksum inconsistencies for virtual postscript fonts on CTAN
- From: "Berthold K.P. Horn" <firstname.lastname@example.org>
- Date: Mon, 27 Jul 1998 19:38:23 -0400
- Cc: email@example.com, firstname.lastname@example.org
- In-Reply-To: <9740-Mon27Jul1998135814email@example.com>
- References: <199807271232.MAA29572@mail-out-4.tiac.net><199807271037.MAA09988@late5.e-technik.uni-erlangen.de><199807271232.MAA29572@mail-out-4.tiac.net>
At 01:58 PM 98/07/27 +0100, Sebastian Rahtz wrote:
> > By the way, consider downloading lw35nfsx.zip instead of lw35nfss.zip
> > It is 150k instead of 800k and provides most of the same capabilities
> > at much lowered complexity. And no checksum nightmares between
>The devil is in the detail, of course. That word "most".
>LY1 is fine, great, but it isn't T1. The aim of the stuff I generated
>was to support OT1 and T1 encoding.
Oh sure, if your focus is on implementing OT1 and T1..
But somehow this is a lower level detail of the _real_ aim, which is
to provide ready-made accented characters so hyphenation can
work in TeX. And that higher level aim is well-served by LY1 :-)
Berthold K.P. Horn
Cambridge, MA mailto:firstname.lastname@example.org