Karakas Online

7.2.4. Choosing the right font encoding

If you think of a font as being arranged in a table, then the font encoding is nothing else than the way the font's symbols (the “glyphs”) are arranged in the table. If you think of the table as being fixed, then different font encodings arrange the same or different glyphs in different ways in the table's cells. If you mentally number all table cells sequentially, then for each table cell you have a number and a glyph. The number is the font's internal representation (the “encoding”) of the glyph.

Fonts are always encoded in some encoding - that's the nature of a font, being just a table of glyphs. Thus, in order to use a font that contains the glyphs (letters, symbols,...) you need, you must tell pdfjadetex and jadetex which encoding to use. For example, to use the T1 font encoding, the jadetex.cfg file must contain the line

\usepackage[T1]{fontenc}

To use the OT1 encoding, you must have:

\usepackage[OT1]{fontenc}

There are some factors that affect the choice of font encoding:

Note that today other solutions to the font quality problem exist as well: instead of using virtual Type 1 fonts (which is what you do when you use the ae, aecompl and aeguill packages), you may choose to use “true” Type 1 fonts by installing one of the new CM-super, CM-LGC or Latin Modern fonts, see Section 7.2.3.

Last updated Mon Sep 24 01:19:25 CEST 2007 Permalink: http://www.karakas-online.de/mySGML/explain-font-encoding.html All contents © 2002-2007 Chris Karakas