1 Sep 2005 01:49
RE: creating a PDF document containing UTF-8 characters
Melih Ovadya <movadya <at> jaspersoft.com>
2005-08-31 23:49:58 GMT
2005-08-31 23:49:58 GMT
Thank you Jeremias, I followed the instructions and now I can make it work
by embedding the font in the document.
Looking at the samples in userconfig.xml, this is how I register the fonts:
<font metrics-file="ttfarialuni.xml"
embed-file="C:\WINDOWS\Fonts\ArialUni.ttf" kerning="yes">
<font-triplet name="ArialUni" style="normal" weight="normal"/>
<font-triplet name="ArialUni" style="normal" weight="bold"/>
<font-triplet name="ArialUni" style="italic" weight="normal"/>
<font-triplet name="ArialUni" style="italic" weight="bold"/>
</font>
</fonts>
What happens if I omit the embed-file tag? After the PDF is created, on the
client machine, how will it find the right font to display the characters in
that case? With this flag, does FO include whole font in the PDF, or just a
subset to be able to display the Unicode characters?
Regards,
melih
>
>
>
So there is a feature in PDF to store the actual content as UTF-8 without the font embedded, and to tell the PDF
viewer to use whatever fonts it can find to render the document? Because that's what we really need to solve
the problem.
Particularly in our system, we can't guarantee that the person generating the PDF has the same fonts as the
person reading it. And worse, we can't even guarantee that the person generating it has ARIALUNI.TTF (as
it's not freely redistributable.) So embedding fonts in any fashion doesn't solve the problem, and
neither does font substitution at the time of generation.
I was thinking that the lack of font substitution at the time of rendering was more of an issue with PDF, but if
you say it's an issue with FOP then I'll take your word for it because I don't know PDF well at all, just its
damage to society.
RSS Feed