[NTG-context] Out of Date? Up to Date?

Taco Hoekwater taco at elvenkind.com
Sun Nov 20 11:27:28 CET 2005


David Arnold wrote:
> All,
> 
> If I read:
> 
> http://www.pragma-ade.com/general/manuals/mfonts.pdf
> 
> How up to date or out of date is the information in this manual?

Hi David,

It looks like it is still quite up-to-date, but some of the
examples it gives may no longer be the very best and latest
way of doing things, and possibly there are some new developments
that do not get as much attention as desired (like texfont, and
the issues arising from font map files). Overall, the document
appears accurate, though.

An important thing to remember is this:

   ConTeXt does not share font metric conventions with LaTeX.

(at one point it started doing so, like supporting the Karl
Berry naming scheme and the psnfss style font family names,
but that has since been abandoned).

Another important thing is that it also does not share font
map files with LaTeX and, specifically,

   ConTeXt does not make pdfetex read pdftex.map.

(this is at the root of a great many problems reported by
users only familiar with nfss)


The preferred format for metric files in ConTeXt is

   <vendor>/<familyname>/<encoding>-<fontname>.tfm

for metrics and

   <encoding>-<vendor>-<familyname>.map

for the mapping files.

   <fontname> is usually derived from the font source (afm or ttf),
   <encoding> is a 'controlled' list,
   <vendor> and <familyname> are user-supplied (at install time).

There are ways to trick ConTeXt into using different conventions,
but if you do that you are likely to run into trouble (as you
have experienced).

Greetings,

Taco



More information about the ntg-context mailing list