9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Michael Kerpan <mjkerpan@kerpan.com>
To: tlaronde@polynum.com
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] [RFC] fonts and unicode/utf [TeX]
Date: Sun, 26 Jun 2011 21:01:13 -0400	[thread overview]
Message-ID: <BANLkTi=WQCj2vL0j=G4FW08FDy_KrYpDMQ@mail.gmail.com> (raw)
In-Reply-To: <20110626075745.GA395@polynum.com>

On Sun, Jun 26, 2011 at 3:57 AM,  <tlaronde@polynum.com> 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)



  reply	other threads:[~2011-06-27  1:01 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-16 12:17 tlaronde
2011-06-16 16:49 ` Russ Cox
2011-06-16 17:37   ` tlaronde
2011-06-16 18:43     ` Bakul Shah
2011-06-16 19:20       ` tlaronde
2011-06-16 17:43 ` tlaronde
2011-06-17 14:18 ` Joel C. Salomon
2011-06-17 15:37   ` tlaronde
2011-06-17 18:07     ` Joel C. Salomon
2011-06-17 18:37       ` tlaronde
2011-06-19 14:21     ` erik quanstrom
2011-06-19 14:07 ` erik quanstrom
2011-06-19 16:34   ` tlaronde
2011-06-19 18:01     ` tlaronde
2011-06-19 22:38     ` erik quanstrom
2011-06-20 11:18       ` tlaronde
2011-06-20 21:53         ` erik quanstrom
2011-06-21 10:56           ` tlaronde
2011-06-24 23:05             ` Mauricio CA
2011-06-25  6:50               ` tlaronde
2011-06-25 12:19                 ` erik quanstrom
2011-06-25 15:03                   ` tlaronde
2011-06-25 15:11                     ` erik quanstrom
2011-06-25 16:33                       ` tlaronde
2011-06-25 16:34                     ` Mauricio CA
2011-06-25 17:11                       ` tlaronde
2011-06-25 18:43                         ` Michael Kerpan
2011-06-26  7:57                           ` tlaronde
2011-06-27  1:01                             ` Michael Kerpan [this message]
2011-06-27 11:48                               ` tlaronde
2011-06-27 12:36                                 ` erik quanstrom
2011-06-27 14:38                                   ` Karljurgen Feuerherm
2011-06-27 17:20                                   ` tlaronde
2011-06-27 17:34                                     ` erik quanstrom
2011-06-27 18:01                                       ` tlaronde
2011-06-27 21:17                                         ` Michael Kerpan
2011-06-28 11:25                                           ` tlaronde
2011-06-27 23:45                                     ` Karljurgen Feuerherm
2011-06-27 23:48                                       ` erik quanstrom
2011-06-28 11:19                                       ` tlaronde
2011-06-28 11:32                                         ` tlaronde
2011-06-28 12:16                                         ` erik quanstrom
2011-06-29 23:43                                         ` Karljurgen Feuerherm
2011-06-30 13:02                                           ` tlaronde
2011-06-30 13:14                                             ` erik quanstrom
2011-06-30 13:47                                               ` tlaronde
2011-06-30 14:51                                             ` Karljurgen Feuerherm
2011-06-30 15:22                                               ` Michael Kerpan
2011-06-30 16:25                                               ` tlaronde
2011-06-30 16:31                                                 ` erik quanstrom
2011-06-30 17:00                                                   ` tlaronde
2011-06-30 17:12                                                     ` tlaronde

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='BANLkTi=WQCj2vL0j=G4FW08FDy_KrYpDMQ@mail.gmail.com' \
    --to=mjkerpan@kerpan.com \
    --cc=9fans@9fans.net \
    --cc=tlaronde@polynum.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).