[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [ft-devel] PDF text rendering error

From: suzuki toshiya
Subject: Re: [ft-devel] PDF text rendering error
Date: Tue, 12 Jun 2012 19:35:27 +0900
User-agent: Mozilla-Thunderbird (X11/20080406)

OK, please let us work with same testing program.

I guess you're working for the proprietary software
and you cannot disclose the source to me (and I think
I don't have appropriate developer environment even
if you can disclose the source).

Thus, I will make a patch generating many trace
messages, and a small CUI program just checking
if the font is found to be tricky. Is it acceptable?

Please check if you can build FT2 library with
debug/trace functions, while I'm writing a patch
for debugging.


Johnson Y. Yan wrote:
Toshiya-san, I apply your patch, but still render error, : (.
If the way i call the function is wrong?
FT_Load_Glyph(FtFace, gid, FT_LOAD_NO_BITMAP).

Johnson Y. Yan

发件人: suzuki toshiya
发送时间: 2012-06-11 16:38:11
收件人: Johnson Y. Yan
抄送: freetype-devel
主题: Re: [ft-devel] PDF text rendering error

Attached is my proposal to fix this issue, please try.
In my case (Debian GNU/Linux xpdf-3.02-11), using the
patched freetype library by LD_PRELOAD, xpdf shows
readable result (without patch, the result is unreadable).
suzuki toshiya wrote:
Johnson Y. Yan wrote (2012/06/11 16:03):
Werner and Toshiya-san,

I  put the font as a tricky font to deal with.
static const char trick_names[TRICK_NAMES_COUNT]
                                 [TRICK_NAMES_MAX_CHARACTERS + 1] =
      "DFKaiSho-SB",     /* dfkaisb.ttf */
      "DFKai-SB",        /* kaiu.ttf */
      "HuaTianKaiTi?",   /* htkt2.ttf */
      "HuaTianSongTi?",  /* htst3.ttf */
      "MingLiU",         /* mingliu.ttf & mingliu.ttc */
      "PMingLiU",        /* mingliu.ttc */
      "MingLi43",        /* mingli.ttf */
"BKLGIB+FA" ---------------------------------------- this is the embeded font in th document.
it still render error. .
Including the randomization prefix to the tricky font name list is bad idea.

I opened the embeded font use font lab, found the gid = 2134 is like this, please see the attach bitmap, some of lines form a 0 area areas, then fill the area(have no area), Does freetype made special processing?

Johnson Y. Yan

发件人: Werner LEMBERG
发送时间: 2012-06-11 12:55:42
收件人: yinsen_yan
抄送: freetype-devel; mpsuzuki
主题: Re: PDF text rendering error

Do you mean the font must be rendered use
No, the FreeType *library* must be built with it: Edit ftoption.h to
set this flag, then recompile.
Additionally, hinting must be enabled for this font, this is,
FT_LOAD_NO_SCALE doesn't work here.
Normally, those steps are (more or less) handled automatically by
FreeType, since we maintain a list of `tricky' font like the one you
have encountered in the PDF; see file `ttobjs.c'.  The subsetted font
in question, however, which identifies itself as
FA 丸ゴシックB and FA-RoundGothicB are trademarks of NEC Office Systems,Ltd.
isn't in this list; for the NEC FA fonts (and others), a second
mechanism is used which doesn't work with subsetted fonts.
Toshiya-san, any ideas?

Freetype-devel mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]