On Sunday 26 June 2016 11:30:44 Hans Hagen wrote:
> On 6/25/2016 3:16 PM, Pali Rohár wrote:
> > Problem is that there are no AFM files for CSFonts (and IIRC never
> > were). CSFonts are written in MetaFont and (from which were
> > generated TFM files) and some subset of CSFonts (those which are
> > often used) were later converted to Type 1 variant... Probably
> > nobody generated yet AFM files for CSFonts as they were not
> > needed, TeX handle just TFM files.
> 
> with an afm file one can also use the fonts in other applications
> than tex

Ok, but I do not think that somebody is interested in CSFonts outside of 
TeX :-) At least I have not hear about it...

> > So if AFM files are really needed and combination PFB+TFM plus
> > MetaFont source code is not enough, how to correctly generate AFM
> > files?
> 
> manual, its a text file

Hm... I thought that there is tools which can generate it. Manually 
writing file is hard and mistakes (in metrics, etc) are often...

> > And why cannot be still used TFM files which contains all kerns and
> > ligature information?
> 
> because one then also needs an encoding vector (an enc file is
> actually a blob of postscript, kind of weird as it could also have
> been a list)

(see my previous email about /Encoding array available in PFB file)

> I'm speaking ConTeXt now: the reason for not bothering about tfm (but
> use afm instead) is that we can use *all* glyphs in a font, not just
> as subset and that made it possible in the early days of luatex to
> use type 1 fonts without bothering about encodings (we only use tfm
> in context for traditional math fonts).

Right, in AFM file (I looked at sent sample by luigi) there is for each 
glyph name metric information. That make sense.

But in case I do not have AFM file and have only TFM + PFB I can use 
only what I have. Unless there is fully automatic conversion tool (which 
get TFM file, PFB file, ENC file, whatever...) which generate AFM file 
correctly.

-- 
Pali Rohár
[email protected]

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to