[FOP-2054] Non-embedded fonts are incorrectly assumed to be single byte, even when they are multi byte

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 2.5
• Component/s: font/unqualified
• Environment: Operating System: All; Platform: All
• External issue ID: 53142
• Assignee: Unassigned
• Reporter: Glenn Adams
• Created: 24/Apr/12 19:47
• Updated: 17/Mar/17 10:05

Description

the following code in o.a.f.fonts.truetype.TTFFontLoader incorrectly assumes that a non-embedded font is a single byte font:

boolean isCid = this.embedded;
if (this.encodingMode == EncodingMode.SINGLE_BYTE)

{ isCid = false; }

if (isCid)

{ multiFont = new MultiByteFont(); returnFont = multiFont; multiFont.setTTCName(ttcFontName); }

else

{ singleFont = new SingleByteFont(); returnFont = singleFont; }

this prevents the use of non-embedded (referenced only) multibyte fonts

the attached input FO file and corresponding FOP configuration make use of the simsun.ttf font (a multibyte font) which can be downloaded from [1]

[1] http://jumal.is.free.fr/SimSun.ttf