[NTG-context] Choosing an encoding - what are the consequences?

Adam Lindsay atl at comp.lancs.ac.uk
Tue Feb 15 15:50:54 CET 2005

Stefan Wachter said this at Tue, 15 Feb 2005 09:38:02 +0100:

>I am on the burdensome path to understanding font handling in ConText. 
>Now I wonder what the consequences are with choosing certain encodings.

I'll give an answer based on what I understand. Mind you, I'm lucky
enough to write almost exclusively in English, where it's not an issue.

>For example if I choose "8a" encoding (called "Adobe standard encoding"):

Okay, as far as I know, ConTeXt doesn't have an 8a/Adobe encoding vector
defined yet.

>1. There are lots of empty slots in this encoding. What does ConText do 
>if a symbol that is to be typeset is not contained in an encoding?

It falls back to the enco-def encoding, where it substitutes or composes
a character from known (or expected) defaults.

>2. Can I ommit the 8a encoding in map files when PDF documents are 
>generated (because it is the Adobe standard encoding)?

Dunno. But it's worth finding out! :)

>3. Somewhere I read that "texnansi" is a preferred encoding. Why?

I think it's got the most useful (to Hans) glyphs packed in there. 
There's the secondary fact that the built-in fonts shipped with most
distributions don't include it, and Hans seems to view most pre-
fabricated TFM files with some suspicion. If you build a local TFM file
with texfont, then you know what you're getting!

But that's only my interpretation.
 Adam T. Lindsay, Computing Dept.     atl at comp.lancs.ac.uk
 Lancaster University, InfoLab21        +44(0)1524/510.514
 Lancaster, LA1 4WA, UK             Fax:+44(0)1524/510.492

More information about the ntg-context mailing list