On Thursday 05 October 2006 17:50, Lars Ivar Igesund wrote:
> Manuel Mall <manuel <at> apache.org> writes:
> > On Thursday 05 October 2006 17:20, Lars Ivar Igesund wrote:
> > > Manuel Mall <manuel <at> apache.org> writes:
> > > > The fo below works just fine for me. No errors parsing, etc..
> > > > This is with the trunk version of fop, xerces xml parser and
> > > > jdk 1.5.0_06.
> > > >
> > > > What is your environment?
> > >
> > > I use FOP 0.92beta, Xerces 2.6.2 and JDK 1.5.0_08 on Linux.
> >
> > That's pretty much the same as me with the exception that I am
> > using the latest trunk version of fop. However, I just tried your
> > fo file against 0.92beta and again it appears to work fine. No
> > parsing errors.... Are you sure you don't have another xml parser
> > somewhere the jdk picks up in preference to xerces?
>
> That is possible, I guess. Hmm, XPP3 is in there, and whatever
> ServiceMix use for it's XML parsing (might actually be Xerces, as I
> didn't put it there).
>
> Also, when searching the net for that particular error message, I got
> some hits related to invalid documents,
> http://www.mail-archive.com/fop-dev%40xmlgraphics.apache.org/msg05025
>.html, also reasonable recent. Can it be related to validation levels?
>
> I'm still very curious about the first issue I had, btw.
>

If I followed this correctly your first issue was the error message:

WARN  - FOTreeBuilder                  - Mismatch: 
instream-foreign-object 
(http://www.w3.org/1999/XSL/Format) vs. svg (http://www.w3.org/2000/svg)

You then removed the xslt translation and concentrated only on the .fo. 
In the end you posted an .fo which works for me but not for you, that 
is it is still throwing a similar error.

My 'gut' feel is that its one and the same problem. Your XML parser gets 
confused with the namespaces. If you get the simple .fo working in your 
environment then the rest will likely work as well.

> Regards,
> Lars Ivar Igesund
>

Manuel

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to