On 6/26/2016 4:22 PM, Pali Rohár wrote:
So above /Encoding 256 array in PFB file can be different as encoding
vector in ENC file? I thought that they should be same...
indeed
Anyway I tested pdftex and it does *not* use ENC file, encoding takes
from /Encoding 256 array from PFB file. And Linux strace program proved
that no enc file was opened during pdftex run.
then you're lucky that they match
So to mimic pdftex behaviour (and how CSFonts Type 1 are read/parsed) I
would really propose to use /Encoding 256 array from PFB file when ENC
file for font loader is not specified.
it makes no sense to have all kind of assumptions built in for this
rather non standard set of cs fonts
Meaning: Use ENC file if possible, but when user not specified it -->
fallback to /Encoding array in PFB file.
can be done but as said keep in mind that it's non typical
I think it could be useful if that your loader was able to
understand command also when pfb file is not specified. It could
try to load either pfb file (preferred) or fallback to
PK/metafont.
the more hardcoded logic is in there, the harder it is to beat (i can
impose some logic in context but want to stay away from intefreing in
other macro packages logic)
it has (internal/system pdftex.map) database of Type 1 fonts and
only system .. in luatex i never use map files
Ok, so luatex ignores any specified map files?
no, the fontloader does not use/pass that info when using outline fonts
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.com | www.pragma-pod.nl
-----------------------------------------------------------------
