Bug 37879 - PDF SVG rendering forces stroking text (config setting broken)
Summary: PDF SVG rendering forces stroking text (config setting broken)
Status: CLOSED FIXED
Alias: None
Product: Fop - Now in Jira
Classification: Unclassified
Component: svg (show other bugs)
Version: trunk
Hardware: All All
: P4 regression
Target Milestone: ---
Assignee: fop-dev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-12 19:46 UTC by Adam Strzelecki
Modified: 2012-04-01 06:37 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Adam Strzelecki 2005-12-12 19:46:20 UTC
Config setting:

    <renderer mime="image/svg+xml">
      <strokeText value="false"/>
    </renderer>

... is virtual, since there is no code that uses that.

But most regression to FOP 0.20 is that when generating PDF, embeded SVG text is
forced to be stoked, and it seems there is no way to avoid it.
This bug makes files using SVG images with some text grow a lot.

Normally file which should be 300KB is 1MB and 70% of the file are strokes of
text from SVG files.

There is also bug related to that in
src/java/org/apache/fop/svg/PDFBridgeContext.java which may be related. In
registerSVGBridges() you check for fontInfo and linkTransform, that are not yet
uninitialized while super(...) is executing in constructor... however since this
function is called from super (BridgeContext) and it is STATIC.. this CODE will
never be called.

There is also no code for binding PDFTextPaineter like in 0.20.5. But I tried to
bind it to the context in PDFSVGHandler but ended up with PDF with no text on
SVG files.. however I must confess this PDF was 70% smaller :)

Please FIX it.. this is serious regression comparing to FOP 0.20.5. Thanks.
Comment 1 Vincent Hennebert 2005-12-13 10:52:01 UTC
This is broken in fop-0.90 with the provided Batik jar. It should work with the
svn versions of /both/ Fop and Batik. You may look at [1] and [2] for details. I
think this is the only solution for now if you need this functionality.

Regarding the strokeText option, it has not been implemented in the Trunk
because its usefulness is doubtful (see [2]). Text will be rendered as text
whenever possible, strokes will only be used as fallbacks.

HTH

[1] http://marc.theaimsgroup.com/?l=fop-dev&m=113293237123386&w=2
[2] http://marc.theaimsgroup.com/?l=fop-dev&m=113301057529277&w=2
Comment 2 Chris Bowditch 2005-12-13 11:30:28 UTC
vincent.hennebert@enseeiht.fr wrote

"Don't know it this bug should be closed? "

Yes, it should.
Comment 3 Glenn Adams 2012-04-01 06:37:57 UTC
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed