Red Hat Bugzilla – Bug 509044
[zh] Chinese text replaced by blank characters in PDF
Last modified: 2010-05-20 02:31:19 EDT
Description of problem:
When you build a PDF in zh-CN, the body text appears as blank characters. Chinese characters appear in the headings.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Make any PDF in zh-CN
PDF is built correctly, but the body text appears blank.
Body text should contain Chinese characters.
Created attachment 350038 [details]
Sample PDF in zh-CN
This is because the font changed to a TTC (True Type Collection) and the FOP shipped in fedora can not automatically load TTCs.
The trunk version of FOP can auto load TTCs as detailed at http://xmlgraphics.apache.org/fop/trunk/fonts.html
I've download the pdf, and find out the pdf is not even built correctly.
If the only problem is font, you can still copy-paste the content to gedit
and see the proper text, however, what I got when pasting the Preface 1. (from demo.pdf) is:
\uffff PDF \uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff Liberation \uffff\uffff \uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff Liberation \uffff\uffff\uffff
\uffff\uffff\uffff\uffff\uffff\uffff\uffff HTML \uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff Linux 5 \uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff\uffff
Interesting though, if open this document with acroread, the bookmarks appears correctly, but not context.
Presumably same for Traditional Chinese.
Are there any more detailed procedures to reproduce please?
Publican now avoids this issue -- see BZ#557336
To expose this bug, try building a Chinese PDF on Fedora with a version of Publican prior to 1.4
(In reply to comment #3)
> I've download the pdf, and find out the pdf is not even built correctly.
> If the only problem is font, you can still copy-paste the content to gedit
> and see the proper text, however, what I got when pasting the Preface 1. (from
> demo.pdf) is:
> 1. \uffff\uffff\uffff\uffff
I tried to extract the text from pdf and it seems the encoding is broken.
$ od -xc dump.txt
0000000 7250 6665 6361 0a65 2e31 ef20 bfbf bfef
P r e f a c e \n 1 . 357 277 277 357 277
0000020 efbf bfbf bfef 0abf bfef efbf bfbf bfef
277 357 277 277 357 277 277 \n 357 277 277 357 277 277 357 277
0000040 efbf bfbf bfef efbf bfbf bfef efbf bfbf
277 357 277 277 357 277 277 357 277 277 357 277 277 357 277 277
They are 0x ef bf bf ef bf bf ef bf bf ...
Probably this is duplicated of bug 557336 ?
I think you can output the correct pdf with gedit or openoffice.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
*** This bug has been marked as a duplicate of bug 557336 ***