Hi Vincent, Vincent Hennebert <[EMAIL PROTECTED]> wrote:
> >>> [...]I try to convert some svg that contains text > >>> into pdf with Batik (1.6), text is always rendered as > >>> strokes [...] > [EMAIL PROTECTED] a écrit : > > This was broken in the Batik 1.6 release. I am about to > > incorporate the pdf-transcoder.jar from the 0.9alpha1 FOP > > release into the Batik SVN repository. Vincent Hennebert <[EMAIL PROTECTED]> wrote on 11/25/2005 02:31:48 PM: > Ok, when I run the Batik rasterizer with an updated pdf-transcoder.jar from the > Trunk I can get text as text. Good. > But this doesn't work when I run Fop with the same svg included in an fo file. > Am I missing something? I take it this is an FO with inline SVG consisting of an SVG 'image' element referencing the SVG file? With the 0.9alpha1 FOP and Batik 1.6 it turns out this won't work properly. If you bundle Batik from SVN this should work. The problem is that when you reference an image a new BridgeContext is constructed. In Batik 1.6 this was done in a few places 'in line' in the code. Shortly after the 1.6 release this was separated into two methods (createSubBridgeContext - copies over needed state to sub Bridge Context, and createBridgeContext which is used to create the BridgeContext instance that should be used). FOP's new PDFBridgeContext now implements createBridgeContext to provide the sub context but unfortunately this method isn't called from Batik 1.6 (I thought it was), but it is from the SVN version of Batik. I'm thinking it is time for a Batik 1.6.1 and then hopefully when/if Fop 0.9alpha2 is released most of these issues will be resolved for people who only want to point to 'released' versions.
