[ 
https://issues.apache.org/jira/browse/FOP-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17641224#comment-17641224
 ] 

Per Cederberg commented on FOP-3042:
------------------------------------

By turning off support for complex scripts, the PDF renders correctly. 
Work-around verified in FOP 2.6 & 2.8, both of which still break if complex 
scripts are enabled. Example configuration line to enable this work-around:
{code:java}
<complex-scripts disabled="true" />{code}
Don't know why this is, but I guess it might explain why I didn't manage to 
replicate this issue in Batik (without FOP).

> SVG text containing certain glyphs isn't rendered
> -------------------------------------------------
>
>                 Key: FOP-3042
>                 URL: https://issues.apache.org/jira/browse/FOP-3042
>             Project: FOP
>          Issue Type: Bug
>          Components: foreign/svg
>    Affects Versions: 2.3, 2.4, 2.6
>            Reporter: Per Cederberg
>            Priority: Major
>         Attachments: CenturyGothicStd.otf, fopconfig.xml, output-fop2.2.pdf, 
> output-fop2.3.pdf, test.xml
>
>
> When rendering an XSL-FO containing an inline SVG with a custom font (Century 
> Gothic), text is only displayed if it doesn't contain the "o" character 
> inside a word. 
> The provided "test.xml" file includes a minimal SVG image that shows this 
> behavior. Everything works correctly from FOP 1.x - 2.2. But starting with 
> FOP 2.3, some text lines might be omitted from the output. Typically lines 
> containing an "o" glyph inside a word. Might also be triggered by other 
> glyphs, as I haven't tested exhaustively with whole alphabet.
> The attached "output-fop2.2.pdf" shows a correct rendering, whereas the 
> "output-fop2.3.pdf" shows rendering in 2.3, 2.4 and 2.6.
> *Disclaimer:* This may actually be a bug in Apache Batik (1.10 and up), but 
> I'm currently unable to reproduce it using their command-line rasterizer tool.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to