> I will parse the .pfb files only when no enc is available. We will see
> how it is useful. Worse thing is large number of non-standard glyph
> names used in TeX fonts. We need to map each glyph to Unicode, it is
> not always easy to find a correct mapping.
It turned quite well, it works even
> > Encoding vector is always embedded in Type1 font.
>
> Usually the /Encoding vector in a given Type 1 is only a subset of the
> characters available in the font. The only way to know what is there is
> to parse the entire file. But there are lots of utilities in this area;
> I suspect
> Encoding vector is always embedded in Type1 font.
Usually the /Encoding vector in a given Type 1 is only a subset of the
characters available in the font. The only way to know what is there is
to parse the entire file. But there are lots of utilities in this area;
I suspect something out
Hi all,
I've finally finished the Htfgen project [1]. It's objective is to
automatize the creation of the HTF font mapping files. These files are
used by tex4ht to map character codes in the DVI files to Unicode.
There are two new scripts: scanfdfile and dvitohtf. The first one
searches for
