Hello Michael,
On 30.05.11, Michael SCHINDLER wrote:
> On 30/05/11, Joerg Lehmann wrote:
> > Interesting! This looks like a limitation in the PDF engine(s) of
> > xpdf & Co. A brief look through Adobe's Type-1-font documentation
> > did not reveal the significance of whitespace in the defintion
> > of the encoding array.
>
> Yes, you are totally right. I was about to send the bug report to the
> xpdf developers, but then I realized that in the original pfb file,
> the "dup"s come one per line. So, even if we are not strictly breaking
> the functionality according to the rules of PDF, I thought it would be
> reasonable to add the newline.
Probably there is some kind of unwritten convention to structure the
Type 1 font like is in order to simplify its parsing. Anyway, it does
not make sense to just point to the standard here. The main point is
that files produced with PyX work on as many output devices as possible,
so your change is definitely the right thing to do.
Cheers,
Jörg
------------------------------------------------------------------------------
vRanger cuts backup time in half-while increasing security.
With the market-leading solution for virtual backup and recovery,
you get blazing-fast, flexible, and affordable data protection.
Download your free trial now.
http://p.sf.net/sfu/quest-d2dcopy1
_______________________________________________
PyX-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pyx-devel
