No, I did not, but I think the whole thing will be resolved more quickly if I write the necessary patch for SAXON and submit that with the error description. But first, I want to look at the PDF size problem.
On 07.05.2006 14:39:43 Florent Georges wrote: > Jeremias Maerki wrote: > > Hi Jeremias > > > As I suspected, it's a bug in SAXON 8.7.1. > > net.sf.saxon.dom.DOMWriter.attribute() does not convert > > empty Strings (for "no namespace") to null when it calls > > element.setAttributeNS(). > > > Of course, one could argue who exactly is at fault here, > > SAXON or Batik. IMO, Batik did well with the fix to > > accept an empty String and null, but SAXON shouldn't send > > an empty String in the first place. > > > I'd file a bug in the SAXON project. > > Did you report the bug? I can't find it in the Saxon bug > tracker, and Michael doesn't seem to be aware of it. > > I can do it if you want, but while I understand the bug > description, I don't have intimate knowledge of the > different elements involved here. Jeremias Maerki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
