Re: Namespaces for attributes in instream objects

2008-01-24 Thread Max Berger
Andreas, On Mon, 2008-01-14 at 20:04 +0100, Andreas L Delmelle wrote: > > See what happens there. Judging from the code, the attributes > > without a prefix are added to the node via the generic > > org.w3c.dom.Element#setAttribute(). This was indeed the problem. AttributeNodes added with "se

Re: Namespaces for attributes in instream objects

2008-01-14 Thread Andreas L Delmelle
On Jan 14, 2008, at 19:04, Andreas L Delmelle wrote: On Jan 14, 2008, at 14:23, Max Berger wrote: - If it is not, where do i need to start looking for the bug? Jeuclid completely ignores namespaces in attributes, so it is either in the fop/plugin interface, fop itself, or the xerces parser?

Re: Namespaces for attributes in instream objects

2008-01-14 Thread Andreas L Delmelle
On Jan 14, 2008, at 14:23, Max Berger wrote: Hi Max, I've just recently encountered a possible "bug" in the jeuclid plugin for fop. Just checking (would make tracking it a bit easier): Do you have any idea if this ever worked, and if yes, when this stopped working? (or: Do you remember havi

Re: Namespaces for attributes in instream objects

2008-01-14 Thread Jeremias Maerki
I use attributes in the default namespace in Barcode4J and have no problems there. I've just updated my local JEuclid working copy and tried once again to build it or set it up in Eclipse but I failed. Once again. I have no nerves for Maven and won't waste one more second of my life on a Maven-enab

Namespaces for attributes in instream objects

2008-01-14 Thread Max Berger
Dear Fop-Devs, I've just recently encountered a possible "bug" in the jeuclid plugin for fop. A complete .fo file is added at the end of the mail. In this file there is a foreign math object: x , which, as you can se