Philipp Lohmann - Sun Germany wrote:
Giuseppe Castagno wrote:
do you think a new RFE issue can be opened about this topic? I think
it should, unless there is already one opened targeting at this and I
wasn't able to find it.
Sure, feel free.
I'll build a stand-alone test case with the free IPA fonts I talked
about while starting the thread and then I'll open a new issue: RFE,
component gsl, subcomponent code.
If I got you right: are you thinking to force the use of a reader
provided font, the closer to the one needed, the better?
And _that_ is the non trivial part, discovering the closer one?
The form fields already carry a font attribute; however in the produced
PDF we need the PostScript name of the font, not just the family. For
our own fontsubsets we simply define that name, for a system font we
would need the correct PostScript name or the reader will end up with
not finding the font.
The tricky part would be if we have to choose an encoding IMHO, this is
trivial for western fonts (WinAnsiEncoding will do the trick), but there
is no clear way for encodings other than ansi1252. But the PDF reference
says, the encoding is optional, if omitted the "font's encoding" will be
used, so perhaps there is no real problem here. I just worry about this
fuzzy "encoding of the font" since e.g. most truetype fonts have a
multitude of encodings builtin. But perhaps we can treat this as a black
box and simply omit the Encoding entry of the font dictionary.
thanks for the hints, I'll have a look at the code. In any case this
will be useful for me to build up a better understanding of fonts in PDF.
--
Kind Regards, and have a nice week-end.
Giuseppe Castagno
Acca Esse http://www.acca-esse.eu
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
