Taco, isn't this a bit too general? All the fonts I have converted with texfont are shared by LaTeX and ConTeXt, and I haven't had any trouble so far. My rule of thumb was: if the font itself (i.e. the tfm) works at the basic level of TeX recognizing and using it, everything else is just a question of a clever use of typescripts (ConTeXt) and font definitions (LaTeX). The only precondition: I gather all the relevant lines into one big mapfile which is read by ConTeXt at runtime (\loadmapfile[my.map]) and has to be enabled via updmap-sys for LaTeX. But AFAICS, the Berry-namimg scheme is not necessary even for LaTeX. Or am I being overoptimistic? Best Thomas On Nov 20, 2005, at 11:27 AM, Taco Hoekwater wrote:

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).

David Arnold wrote:

Wanna send me what you have and I'll annotate it with suggestions, much as we did with Metafun?

sure, suggestions (goes for all manuals) are welcome, Hans