Re: default fo namespace, default xml parser

Hello Jack,

Thanks for your feedback!

> 1. Jfor doesn't recognize the "http://www.w3.org/1999/XSL/Format" xml 
> namespace ...
> Rather, the IBuilder objects look for (hard-coded) elements named 
> "fo:page-sequence", "fo:layout-master-set", etc.

You're right, this is something we're aware of but haven't had time to 
fix yet.

> 2. The class name of the XmlReader is hard-coded in the default 
> IConverterOption class.
> I'd rather not add another jar to my project, nor write a custom
> IConverterOption implementation. It would be more convenient if it 
> used the
> java.xml.parsers.SAXParserFactory to find the default parser.

Yes, makes sense too.

Unfortunately I'm already backlogged with integrating several 
contributions and bug fixes, so you shouldn't expect these problems to 
be corrected very soon from our side.

I you want to tackle these problems, however, you're most welcome to 
try it. Please ask questions on the jfor-devel mailing list if you have 
any.

Hope this helps!
--
   Bertrand Delacretaz (codeconsult.ch, jfor.org)
   XML, java, XSLT, Cocoon, FOP, mentoring/programming/teaching
   blogspace http://www.codeconsult.ch/bertrand



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com