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.
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
vincent.hennebert@enseeiht.fr wrote "Don't know it this bug should be closed? " Yes, it should.
batch transition pre-FOP1.0 resolved+fixed bugs to closed+fixed