xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "M.Hilpert (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FOP-2604) FOP 2.0: Font not found depending on SVG XML
Date Wed, 04 May 2016 07:13:12 GMT
M.Hilpert created FOP-2604:

             Summary: FOP 2.0: Font not found depending on SVG XML
                 Key: FOP-2604
                 URL: https://issues.apache.org/jira/browse/FOP-2604
             Project: FOP
          Issue Type: Bug
          Components: foreign/svg
    Affects Versions: 2.0
         Environment: Windows 7 64 Bit, Java 8 64 Bit.
            Reporter: M.Hilpert

FOP 2.0 introduced the ability that SVGs now can use the fonts configured via the standard
FOP user_config.xml.

This works only for specific SVGs but not for all. We have 2 basic "SVG types" in our XSL-FO
documents: both are generated differently. But both reference the same font:

A) <g stroke-miterlimit="1" stroke-width="0.5" font-size="8px" font-family="'HelveticaNeueLT
Com 45 Lt'" stroke-linecap="round" stroke-linejoin="round">

B) <g style="fill:rgb(46,38,94); text-rendering:geometricPrecision; font-size:9px; shape-rendering:crispEdges;
font-family:'HelveticaNeueLT Com 45 Lt'; stroke:rgb(46,38,94);">

As you see, both SVGs have the very same font name "HelveticaNeueLT Com 45 Lt". However, only
A) seems to use the font definition of FOP, but B) doesn't. We multi-checked this by changing
FOP font configs and un-/installed the font on Windows.

As a "workaround", we still need to install the fonts additionally in the Windows system for
B) to still find the font.

My guessing is, that the different SVG code of both cases is the reason. Perhaps FOP does
not consider the B) case to search the font in it's fop_userconfig-xml and therefore "falls
back" to search in the installed system fonts.

This message was sent by Atlassian JIRA

View raw message