On 03/29/2011 12:19 PM, poloshiao wrote:
[...]
> A short conclusion with poller-data:
> There are still sqare characters shown in the documents or Mojibake in the path name.
>
> Wish this disturbing problem will be solved ASAP.
So, this mean, libpoppler is one of those buggy libraries, which cannot
deal with font fall backs in fontconfig.
This needs to be fixed upstream!
Can someone who can reliably reproduce this problem please file a bug
upstream for libpoppler, attach the test document and the fontconfig
configurations, and write a detailed test case what is expected and what
actually happens?
<explanation>
This bug appears because when the document was produced, the fonts which
have been used to produce the document, have not been embedded into the
document. This is bad practice in general, since in such cases the PDF
viewer needs to use system fonts to render the text in the document.
However, the font metrics may not be the same (and usually aren't) as
the ones the original creator of the document has used. As a result the
document will most likely look different than originally intended. This
is the case which happens here.
Poppler-data only provides the font metrics for CID encoded fonts.
Therefor the data will only be used if CID encoded fonts (e.g. the ones
provided by Adobe) have been used to create the pdf.
If the document was created with any other font which is not installed
on the viewer's system, libpoppler tries to use fontconfig to substitute
the font information in the document with what is available on the
system. However, it uses only the first font it finds and doesn't check
if the required glyphs are actually available. This is the bug we are
having here. If the required glyphs are not available, libpoppler should
try the next font in the fontconfig list.
</explanation>
Thanks a lot! :)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 03/29/2011 12:19 PM, poloshiao wrote:
[...]
> A short conclusion with poller-data:
> There are still sqare characters shown in the documents or Mojibake in the path name.
>
> Wish this disturbing problem will be solved ASAP.
So, this mean, libpoppler is one of those buggy libraries, which cannot
deal with font fall backs in fontconfig.
This needs to be fixed upstream!
Can someone who can reliably reproduce this problem please file a bug
upstream for libpoppler, attach the test document and the fontconfig
configurations, and write a detailed test case what is expected and what
actually happens?
<explanation>
This bug appears because when the document was produced, the fonts which
have been used to produce the document, have not been embedded into the
document. This is bad practice in general, since in such cases the PDF
viewer needs to use system fonts to render the text in the document.
However, the font metrics may not be the same (and usually aren't) as
the ones the original creator of the document has used. As a result the
document will most likely look different than originally intended. This
is the case which happens here.
Poppler-data only provides the font metrics for CID encoded fonts.
Therefor the data will only be used if CID encoded fonts (e.g. the ones
provided by Adobe) have been used to create the pdf.
If the document was created with any other font which is not installed
on the viewer's system, libpoppler tries to use fontconfig to substitute
the font information in the document with what is available on the
system. However, it uses only the first font it finds and doesn't check
if the required glyphs are actually available. This is the bug we are
having here. If the required glyphs are not available, libpoppler should
try the next font in the fontconfig list.
</explanation>
Thanks a lot! :) enigmail. mozdev. org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
iQIcBAEBCAAGBQJ NkYE1AAoJENiwmJ tstTzsI20P/ R/kfpCms9Sd38Mg FJAFY3k+ 2JOSDT6Q46LF5+ uUQeLxnaSjQ+ gWjsdx3eCwPB9h9 15B4u1E1 UYfb/HNG3MrjRKC 8vhpOxT5Tvn1ZK6 xHEmYe/ REGZyhA+ zWvc 7GBmNyLJa1ugMjk KMvu05ohq+ o4yPkd9dkZNNqPj h9pJ670Ts ZOu+wXC7uEH1i7R 3ubfZId/ AXAP6UiYHOXQFki ay9QcZiHQP9 +NHYUYuTxyndU9I P63Cga/ IWOpdMlMHGs/ ZBDnXBQlig+ FCJ9 4xA5EvneZbs6L5Z PUgBRS8EpsKU2fU YTKbol2wcc3e0Qk rZS5 ohZndZqD9jEpzRX Qs0LA0L4e5IoOdm zK5/pMywSZl6imV AXGw XpfibxEAo5d2gf2 Y63gIldLJgTF76A Er5A1ZAEb38y2iA BQuRaO8IRmkB 0ToR9aJefyu/ ws0q7e1VgtXIYva Ce9pR+AwuL2llT+ 9VtvrJg NXjbBNdpmNkkTOU yWiAs6oar/ 1A0UnY2JsePTpzK bFaqTk+ K1 oseaW
/PgHsBSPVQNkQvN
vqV0cknJVpIRYNJ
VBGt22X9dHZ2aSB
MpCpWIDA2MwRlZ2
Ws8asgL8BpjMvY1
rZJiAnYDbut6D8z
GeSSS8FYPVtC782
Hqv+O5/
bpLClKQwWKD4BRs
JDya7pNmiGrpOM/
h8QDsh09PRxgU1+
=eGeJ
-----END PGP SIGNATURE-----