|
From: | Johnson Y. Yan |
Subject: | Re: [ft-devel] PDF text rendering error |
Date: | Mon, 11 Jun 2012 15:03:01 +0800 |
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 */
"DFKaiShu",
"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. .
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
> TT_CONFIG_OPTION_BYTECODE_INTERPRETER?
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
BKLGIB+FA-RoundGothicB
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?
Werner
|
ping.bmp
Description: Binary data
1_BKLGIB+FA.ttf
Description: Binary data
[Prev in Thread] | Current Thread | [Next in Thread] |