xml:space namespace error
The attribute xml:space="preserve" as found on Inkscape's flowDiv causes an XML Namespace Error when being parsed by PyXML's SAX2 reader. Any of my python effects should display this error.
Is this our problem or PyXML's?
Aaron Spike
On 6/19/05, aaron@...749... <aaron@...749...> wrote:
Is this our problem or PyXML's?
Certainly not ours. XML spec says clearly that the xml: prefix need not be defined, it is reserved.
bulia byak wrote:
On 6/19/05, aaron@...749... <aaron@...749...> wrote:
Is this our problem or PyXML's?
Certainly not ours. XML spec says clearly that the xml: prefix need not be defined, it is reserved.
Sorry, I'm not sure how that bit of information supports your answer to my question. But I'm not sure I was very clear either, so I will try to be a little more verbose.
Inkscape creates somthing like this for flowtext:
<flowRoot id="flowRoot1"> <flowRegion id="flowRegion2" /> <flowDiv xml:space="preserve" id="flowDiv3"> <flowPara id="flowPara4"> flowing text here </flowPara> </flowDiv> </flowRoot>
Notice the "xml:" prefix on space. This causes the PyXML parser to raise a NamespaceErr exception. If I remove the "xml:" it raises no exception.
Is the way we are doing this absolutely correct?
Aaron Spike
aaron@...749... wrote:
bulia byak wrote:
On 6/19/05, aaron@...749... <aaron@...749...> wrote:
Is this our problem or PyXML's?
Certainly not ours. XML spec says clearly that the xml: prefix need not be defined, it is reserved.
Sorry, I'm not sure how that bit of information supports your answer to my question. But I'm not sure I was very clear either, so I will try to be a little more verbose.
Inkscape creates somthing like this for flowtext:
<flowRoot id="flowRoot1"> <flowRegion id="flowRegion2" /> <flowDiv xml:space="preserve" id="flowDiv3"> <flowPara id="flowPara4"> flowing text here </flowPara> </flowDiv> </flowRoot>
Notice the "xml:" prefix on space. This causes the PyXML parser to raise a NamespaceErr exception. If I remove the "xml:" it raises no exception.
Is the way we are doing this absolutely correct?
Aaron Spike
PyXML is possibly choking on the fact that there is no xmlns:xml="some namespace URI" prefix defined before the xml: prefix is used in the document. Not only is that namespace declaration not needed, it is illegal. The XML spec has an implied URI which cannot be redefined.
Bob
Bob Jamison wrote:
PyXML is possibly choking on the fact that there is no xmlns:xml="some namespace URI" prefix defined before the xml: prefix is used in the document. Not only is that namespace declaration not needed, it is illegal. The XML spec has an implied URI which cannot be redefined.
Oops. I was wrong about "illegal," but it cannot be redefined.
Bob
On Sun, 2005-06-19 at 21:22 -0500, Bob Jamison wrote:
aaron@...749... wrote:
bulia byak wrote:
On 6/19/05, aaron@...749... <aaron@...749...> wrote:
Is this our problem or PyXML's?
Certainly not ours. XML spec says clearly that the xml: prefix need not be defined, it is reserved.
Sorry, I'm not sure how that bit of information supports your answer to my question. But I'm not sure I was very clear either, so I will try to be a little more verbose.
Inkscape creates somthing like this for flowtext:
<flowRoot id="flowRoot1"> <flowRegion id="flowRegion2" /> <flowDiv xml:space="preserve" id="flowDiv3"> <flowPara id="flowPara4"> flowing text here </flowPara> </flowDiv> </flowRoot>
Notice the "xml:" prefix on space. This causes the PyXML parser to raise a NamespaceErr exception. If I remove the "xml:" it raises no exception.
Is the way we are doing this absolutely correct?
Aaron Spike
PyXML is possibly choking on the fact that there is no xmlns:xml="some namespace URI" prefix defined before the xml: prefix is used in the document. Not only is that namespace declaration not needed, it is illegal. The XML spec has an implied URI which cannot be redefined.
So this bug should be pushed upstream to PyXML, correct?
Jon
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 6/19/05, aaron@...749... <aaron@...749...> wrote:
Jon Phillips wrote:
So this bug should be pushed upstream to PyXML, correct?
Probably, but not until I am sure what the bug really is.
As I wrote, using xml: prefix is valid anywhere in any XML document without needing to declare it in any way. So our XML is valid, and therefore anyone who chokes on it has a bug.
And by the way this is pretty serious bug because it makes it impossible to use any Python effects on documents with text. Even though it's not our fault, but we need to think of a workaround. I just tried adding
xmlns:xml="http://www.w3.org/XML/1998/namespace"
to the root <svg> but this did not help at all (same error). And besides adding this declaration makes the document fail in Batik (even though it's still valid as far as I understand).
Just in case, here's the spec on namespaces: http://www.w3.org/TR/REC-xml-names/
bulia byak wrote:
And by the way this is pretty serious bug because it makes it impossible to use any Python effects on documents with text. Even though it's not our fault, but we need to think of a workaround. I just tried adding
xmlns:xml="http://www.w3.org/XML/1998/namespace"
to the root <svg> but this did not help at all (same error). And besides adding this declaration makes the document fail in Batik (even though it's still valid as far as I understand).
Just in case, here's the spec on namespaces: http://www.w3.org/TR/REC-xml-names/
I'm starting to think the failure with PyXML isn't because of the "xml:" prefix but rather because of the "xmlns:xml" declaration itself.
When I run a minimal svg:
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <!-- xmlns:xml="http://www.w3.org/XML/1998/namespace" --> <svg xmlns:xml="http://www.w3.org/XML/1998/namespace" xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg"
</svg>
Through a minimal python script:
#!/usr/bin/env python import sys, xml.dom.ext.reader.Sax2 reader = xml.dom.ext.reader.Sax2.Reader(validate=0) stream = open(sys.argv[-1],'r') document = reader.fromStream(stream) stream.close()
I get the error when ever I include the 'xmlns:xml="http://www.w3.org/XML/1998/namespace"' declaration in the root.
The reason that I initially related the problem to the presence of the "xml:" prefix is that when Inkscape sees the prefix it adds the namespace declaration. And if there is no prefix found in the file the namespace declaration is ommited on save. So when I removed the prefix, Inkscape was sending a file without the xml namespace declared to the extensions, even though the namespace declaration was present in the original file I was looking at.
If that declaration chokes Batik too, should we make a point of omitting it all together?
Aaron Spike
On 6/20/05, aaron@...749... <aaron@...749...> wrote:
I'm starting to think the failure with PyXML isn't because of the "xml:" prefix but rather because of the "xmlns:xml" declaration itself.
Wow! I did not notice that Inkscape inserts xmlns:xml itself. I was absolutely sure we can't do such a foolish thing :)
This only happens with flowtext, not regular text. Of course then it's our problem, we must remove that (it's not a bug strictly speaking, but it's better not to have this).
Mental: I have a vague memory of you writing the code to supply namespace declarations based on prefixes used. If I remembered this correctly, can you please fix that code to never include a declaration for xml: prefix?
Quoting bulia byak <buliabyak@...400...>:
On 6/20/05, aaron@...749... <aaron@...749...> wrote:
I'm starting to think the failure with PyXML isn't because of
the "xml:"
prefix but rather because of the "xmlns:xml" declaration
itself.
Wow! I did not notice that Inkscape inserts xmlns:xml itself. I was absolutely sure we can't do such a foolish thing :)
Whoops. Ow. My bug.
I thought I'd remembered to take care of that and omit 'xml' from the list of namespace bindings emitted in repr-io...
-mental
Quoting bulia byak <buliabyak@...400...>:
Mental: I have a vague memory of you writing the code to supply namespace declarations based on prefixes used. If I remembered this correctly, can you please fix that code to never include a declaration for xml: prefix?
Please file a bug so I don't forget. I'm pulled in a lot of directions these days.
-mental
Quoting "aaron@...749... " <aaron@...749...>:
Inkscape creates somthing like this for flowtext:
<flowRoot id="flowRoot1"> <flowRegion id="flowRegion2" /> <flowDiv xml:space="preserve" id="flowDiv3"> <flowPara id="flowPara4"> flowing text here </flowPara> </flowDiv> </flowRoot>
Notice the "xml:" prefix on space. This causes the PyXML parser to raise a NamespaceErr exception. If I remove the "xml:" it raises no exception.
Is the way we are doing this absolutely correct?
Yes. The PyXML parser is in error.
-mental
participants (5)
-
unknown＠example.com -
aaron＠...749... -
Bob Jamison -
bulia byak -
Jon Phillips