Difference between revisions of "Fonts - Old Content"

From Wiki
Jump to navigation Jump to search
m (Symbols link)
(added basic hints by Taco)
Line 19: Line 19:
  
  
==Configuration==
+
=Basic Hints=
 +
 
 +
''Some hints by Taco from the mailing list on 2005-11-20:''
 +
 
 +
Q: How up to date or out of date is the information in [http://www.pragma-ade.com/general/manuals/mfonts.pdf mfonts manual]?
 +
 
 +
A: 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 [http://www.pragma-ade.com/general/manuals/mtexfont.pdf 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 <tt>pdftex.map</tt>.'''
 +
 
 +
(this is at the root of a great many problems reported by users only familiar with PSNFSS)
 +
 
 +
The preferred format for metric files in ConTeXt is
 +
 
 +
<tt><vendor>/<familyname>/<encoding>-<fontname>.tfm</tt>
 +
 
 +
for metrics and
 +
 
 +
<tt><encoding>-<vendor>-<familyname>.map</tt>
 +
 
 +
for the mapping files.
 +
 
 +
*  <fontname> is usually derived from the font source (afm or ttf),
 +
*  <encoding> is a 'controlled' list, (see [[Encodings and Regimes]])
 +
*  <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.
 +
 
 +
=Configuration=
 
* Using [[psnfss]] metrics in ConTeXt
 
* Using [[psnfss]] metrics in ConTeXt
 
* Matt Gushee about [http://havenrock.com/textips/bookfonts.html virtual fonts]
 
* Matt Gushee about [http://havenrock.com/textips/bookfonts.html virtual fonts]
Line 26: Line 62:
 
* Don't forget to look at  [[cont-sys.tex]]!
 
* Don't forget to look at  [[cont-sys.tex]]!
  
===Hints by Language===
+
=Hints by Language=
 
* general: [[Encodings and Regimes]]
 
* general: [[Encodings and Regimes]]
 
* [[Arabian and Hebrew]] (Idris? other ArabTeX specialists?)
 
* [[Arabian and Hebrew]] (Idris? other ArabTeX specialists?)

Revision as of 12:04, 20 November 2005

< Visuals | Symbols >

Font handling in ConTeXt is “strange” for LaTeX users. It's a system of abstraction and aliases, complex and mighty … But there's help:


Basic Hints

Some hints by Taco from the mailing list on 2005-11-20:

Q: How up to date or out of date is the information in mfonts manual?

A: 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 PSNFSS)

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, (see Encodings and Regimes)
  • <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.

Configuration

  • Using psnfss metrics in ConTeXt
  • Matt Gushee about virtual fonts
  • Fonts rely on Encodings and Regimes, and it helps to know what happens underneath the hood, from time to time.
  • In newer distributions, map files belong in …/fonts/map/pdftex/context!
  • Don't forget to look at cont-sys.tex!

Hints by Language