From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20110626075745.GA395@polynum.com> References: <20110620111845.GA540@polynum.com> <76aac2169637c7af09dcd0b368aa0c7a@ladd.quanstro.net> <20110621105626.GA536@polynum.com> <20110625065017.GA638@polynum.com> <522e1e2a38aa18c291305563d362abfe@ladd.quanstro.net> <20110625150327.GA425@polynum.com> <20110625171134.GA3661@polynum.com> <20110626075745.GA395@polynum.com> Date: Sun, 26 Jun 2011 21:01:13 -0400 Message-ID: From: Michael Kerpan To: tlaronde@polynum.com Content-Type: text/plain; charset=ISO-8859-1 Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX] Topicbox-Message-UUID: f6ae8b22-ead6-11e9-9d60-3106f5b1d025 On Sun, Jun 26, 2011 at 3:57 AM, wrote: > I don't know what "automagic" ligatures are; but ligatures are here in > the kerTeX fonts, user having nothing special to do to have them. Small > caps are here. Using the system fonts is here too, at least for T1 > fonts: afm2tfm(1) makes them available. For other fonts format, > writing a whatever2tfm(1) will do the job. In general using a simple Type 1 font isn't going to get you things like true small caps, ligatures (beyond maybe the basic "fi" and "fl") or the ability to choose between old-style and lining figures. The 256 glyph limit means that you had to split things up into multiple fonts, This works well enough for simply creating a PostScript file that will be fed straight to a laser printer, but for creating searchable PDF files, it's far from ideal. In TeX, it also require a lot of manual work above and beyond what would be needed to get those features using Computer Modern. With OpenType support (and using OpenType fonts, of course), typographic features become as easy to use with third-party fonts as they are with Computer Modern. > And "archaic" is definitively a marketing sentence, not a scientific > judgement: "Euclid? Well... it was perhaps good for the epoch..." True enough. it's more my opinion than anything else. Still, it must be an opinion shared by someone else, given the widespread use of "fontspec" wherever available compared to the older methods. >> The problem is that these modern implementations are HUGE. On the >> average Linux system, TeX, LaTeX and other paraphernalia seem to take >> up well over 1 GB these days. I've given up on TeX because it's just >> so darn big. > > So have I. > kerTeX is 1/100th of the current TeX distributions and is C89, that is > the most portable. It lacks some Heirloom troff features, but it is for > text and mathematics, includes a font designer: METAFONT, a figure > designer: MetaPost and a bunch of debugging utilities, coding utilities > (WEB), fonts and a state of the art documentation. I'm not disparaging your work. In fact I think its pretty good. I was mainly trying to point out the problems that have arisen in some "modern" TeX distros in the past. > So I stick to kerTeX. And I have recorded what _you_ propose to do ;) > Since you seem to claim that the way _you are engaged in_ is easier than > the road I have taken, you should have finished before I have finished > kerTeX, rendering it /* sigh */ obsolete... I doubt that, as tounge-in-cheek suggestions seldom seem to turn into working ideas (at least when they come from me)