Hi Adam,
Adam Strzelecki <[EMAIL PROTECTED]> wrote on 12/13/2005 08:17:38 AM:
> > None of your content uses 'simple' text. All of your
> > text uses child tspan's with 'x' & 'y' attributes. This falls into
> > the case of complex text so we stroke the text.
> Booo... so we need to stroke tspans ?
Tspans with 'x' & 'y' attrs yes.
> 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.
> 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.
