flex-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Grove (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLEX-34122) comma separated fonts in fontFamily don't work with embedded fonts
Date Thu, 27 Feb 2014 14:59:19 GMT
Michael Grove created FLEX-34122:

             Summary: comma separated fonts in fontFamily don't work with embedded fonts
                 Key: FLEX-34122
                 URL: https://issues.apache.org/jira/browse/FLEX-34122
             Project: Apache Flex
          Issue Type: Bug
          Components: Embedded Fonts
    Affects Versions: Adobe Flex SDK 4.6 (Release)
            Reporter: Michael Grove
            Priority: Minor

if you specify a fontFamiy with a single entry that is an embedded font, such as

global {
	fontFamily: HPSimplified;

this works correctly.  the HPSimplified font is used when it can render the characters being
displayed, and a fallback, apparently Times New Roman, is used otherwise.

if you specify a fontFamily that is a comma separated list of system fonts, things also appear
to work correctly.

global {
	fontFamily: Arial, Verdana, Times;

Arial will be chosen above.  if i replace Arial with an unrecognized font, like foo, Verdana
will be chosen.

things stop working when my fontFamily indicates preference for an embedded font followed
by system fonts:

global {
	fontFamily: HPSimplified, Arial, Verdana, Times;

here i find that Arial is always used.  i've never seen my embedded font chosen when fontFamily
contains a comma separated list.

my intent is to use the HPSimplified font whenever possible, but failing that, to select the
font to be used in a reliable, deterministic manner.  the only workaround we've come up with
is to programmatically set the fontFamily to a single entry based on the locale (e.g. if en_us
use HPSimplified, if zh_cn use ...).

This message was sent by Atlassian JIRA

View raw message