[ https://issues.apache.org/jira/browse/FOP-2931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17746836#comment-17746836 ]
Dave Roxburgh commented on FOP-2931: ------------------------------------ The given SVG is malformed - href is from the xlink namespace, not svg. My guess is that browsers are tolerant of poorly-written SVG documents. Run against svgwithtextpath.svg, Batik's PNGTranscoder throws a StringIndexOutOfBoundsException as BridgeContext.getReferencedNode() tries to resolve the href attribute. The same error occurs when FOP tries to use Batik to include the SVG. [^test-xlink.svg] is svgwithtextpath.svg made valid. > SVG with a 'TextPath' element does not show in PDF > -------------------------------------------------- > > Key: FOP-2931 > URL: https://issues.apache.org/jira/browse/FOP-2931 > Project: FOP > Issue Type: Bug > Components: fo/inline, foreign/svg > Affects Versions: 2.3 > Reporter: Redhwan Nacef > Priority: Major > Attachments: svgwithtextpath.svg, test-xlink.svg > > > After adding a TextPath element to an SVG, the SVG no longer renders in the > PDF. The SVG works fine on browsers. Wikipedia shows Batik (the SVG renderer > for Apache FOP) is compatible with TextPath: > [https://en.wikipedia.org/wiki/Comparison_of_layout_engines_(Scalable_Vector_Graphics)]. > Attached is a sample SVG. -- This message was sent by Atlassian Jira (v8.20.10#820010)