[luatex] luatex - font encoding for type 1 fonts

[Pali Rohár]

On Friday 24 June 2016 16:03:11 Hans Hagen wrote:
> On 6/24/2016 2:18 PM, Pali Rohár wrote:
> > On Friday 24 June 2016 14:14:24 Hans Hagen wrote:
> >> On 6/24/2016 2:10 PM, Pali Rohár wrote:
> >>> On Friday 24 June 2016 14:01:25 Hans Hagen wrote:
> >>>> On 6/24/2016 1:33 PM, Pali Rohár wrote:
> >>>>>> (2) the several
> >>>>>> cs related packages don't seem to come with afm files,
> >>>>> 
> >>>>> Not several, but all! Metrics are stored in ftm files, e.g.
> >>>>> csr10.tfm. For each font there is metafont source code, tex
> >>>>> metrics and for some also type1 variant (as pfb file):
> >>>>> csr10.mf csr10.tfm csr10.pfb
> >>>> 
> >>>> afaiks no afm files
> >>> 
> >>> And why do you need afm files? Are not TeX metrics (tfm) enough?
> >> 
> >> then you can just load the font (given that the afm matches the
> >> pfb)
> > 
> > AFM file contains just font metrics, right? Why is TFM file (which
> > contains also metrics) usable? What I trying understand is where is
> > the problem as until now TFM + PFB was enough...
> 
> because afm/pfb files contain info about what characters we have
> while the tfm file only has metrics (in which case one also needs to
> interpret the encoding vector)

Do you have some link about description of AFM and TFM files?

IIRC, PFB file has vector of glyph names. So from this information can 
be generated encoding font table as for each glyph name can be assigned 
unicode character. And this could work for any Type 1 font in PFB format 
Or I'm missing something?

-- 
Pali Rohár
pali.rohar at gmail.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://tug.org/pipermail/luatex/attachments/20160625/51262605/attachment.bin>