First off, I solved my issue by using the lastest trunk of fop-0.95.

cbowditch wrote:
> 
> SVG is processed by Batik, so this is really a Batik problem not a FOP
> one. 
> 

SVG is processed by Batik, true, but the issue is indeed with FOP.  In
current release FOP is not aware of SVG 1.2.  The latest trunk is.


cbowditch wrote:
> 
> Batik doesn't properly support svg:flowRoot, which I know Inkscape uses
> when generating/editing SVG there.
> 

In my experience batik-1.7 does render svg:flowRoot "correctly".  But then
again, what is correctly, as the standard is still in draft.  To verify,
download the lastest binary release of batik-1.7 and open the following
document in batik-squiggle;

<svg:svg xmlns:svg="http://www.w3.org/2000/svg"; version="1.2" height="150"
width="100">
         <svg:flowRoot>
            <svg:flowRegion>
                <svg:path d="M100,50L50,300L250,300L300,50z" 
visibility="hidden"/>
            </svg:flowRegion>
            <svg:flowDiv>
                <svg:flowPara>Tomorrow, and tomorrow, and tomorrow; creeps in 
this
petty pace from day to day, until the last syllable of recorded time. And
all our yesterdays have lighted fools the way to dusty death.</svg:flowPara>
            </svg:flowDiv>
        </svg:flowRoot>
</svg:svg>

The latest release of InkScape on the other hand, does fail.


cbowditch wrote:
> 
> You can avoid the error by changing the version attribute on the SVG
> element from 1.0 to 1.2 but Batik still doesn't draw the flowRoot elements
> correctly.
> 

The error is not avoided by that until I started using the trunk of
fop-0.95.


cbowditch wrote:
> 
> I suggest you follow up this issue on [email protected].
> 

Thanks for the suggestion, but there is no need to.  I got things working as
I want now.


Ralph
-- 
View this message in context: 
http://www.nabble.com/EmptyStackException-when-processing-embedded-svg-flowRoot-element-tp25018374p25666937.html
Sent from the FOP - Users mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to