Glyph failover not working with FontLookup as both embedded or device?

Question

I have an embedded font with a unicode range targeted to the latin base set:

unicodeRange = 'U+0020-U+00FF'

When my string includes arabic on a mac or kanji/han (chinese) on windows, the failover fails, as in I get the rectangles instead of a replaced device glyph.

It was my understanding that the FTE in player 10 swapped out failed glyphs for device glyphs per character. This appears to be working, but not for all cases.

On my mac, chinese device glyphs get inserted just fine in the case of this string: "車 and あります Kanji Test"

On windows this string fails by placing the rectangles in place of the chinese characters.

Another example shows arabic on a mac with the rectangles instead of device arabic glyphs: "Arabic Test كيبورد للكتابة بال"

Thanks in advance for any insight.

NOTE:

Using player 10,0,32,18 on a mac and 10.0.42.34 on windows.

Using TLF version 4.0.0.10485

Anonymous · Accepted Answer

This is an intriguing scenario. Some device fonts work for Arabic (Arial, Times New Roman), some don't (Verdana, Myriad Pro). This is when I set the FontLookup to device (FontLookup.DEVICE). None of those fonts if I am not mistaken have Arabic or Chinese glyphs, so the fact that Chinese is successfully replaced but Arabic is not (rectangles) is the disturbing issue.

I have also added some fonts to the fontFamily property, comma-delimited, as fall back options, such as "Verdana, Arial, _sans" but that doesn't work with my strings. I have a hunch after re-reading the fontFamily docs that those fallbacks only work if a font is not found, not as a per glyph replacement strategy.

I believe the rectangles you're seeing with Arabic and device fonts was a known issue that got fixed in Player 10.1. Which made me recall that there were a lot of glyph fallback fixes that were made after the Player versions you're using. You may want to see if the embedded issues you're seeing still happen in the most recent Player 10.1 beta.

And you're right - the font list only works to determine what font gets applied to all of the text. If there are glyphs missing the Player looks up it's own list of fonts to use to display those glyphs.

dave_held · Answer

(I've moved my question to a separate discussion: http://forums.adobe.com/thread/863551) - thanks

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.