xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adam Strzelecki <...@java.pl>
Subject Re: DO NOT REPLY [Bug 37879] - PDF SVG rendering forces stroking text (config setting broken)
Date Tue, 13 Dec 2005 14:58:25 GMT

>> Is there any change to handle them also like simple text ?
>     Assuming you mean chance?  Yes it is possible but
> it is _far_ from trivial.  A 'tspan' is quite a bit
> different from 'text' in particular a tspan inherits it's
> position from previous tspans/text so placement is complex.
>     There are essentially two paths to go down.
>         1) rewrite the existing SVG text support for PDF,
>            implementing what pieces can be implemented as
>            a series of 'drawString' calls.
>         2) Rework the PDFGraphics2D to enable proper output
>            from a GlyphVector - or more correctly a custom
>            version of a GlyphVector as the JDK version does
>          not (I think) provide enough information for transcoding.
Alright.... I'll try to fix my SVG files to use simple text though.
Nevertheless I'll look forward implementation 'tspans' for text
rendering you describe.

>> I believe that with FOP 0.20.5 tspans were handled too (however I might
>> be wrong), because PDF generated with old version were OK.
>     I believe the old version ignored all the problems that 
> sub-tspans with x & y cause and just rendered them as normal
> text.  This might have 'worked' for your case but is why there
> was a 'stroke text' option as it would get many cases wrong.
I see, then maybe you can point out how to simply patch the TRUNK code
to work like 0.20.5 for 'tspans' even it is wrong ?? Of course I wish to
use it internally for myself as I'm generating lot of docbook documents
with SVG drawings with text.

Best regards,
Adam Strzelecki |: nanoant.com :|

View raw message