First, excuse me if my english is not a very good one.
I have found a 'potentially' bug in tinyxmlparser.cpp -> method 'TiXmlNode::Identify' -> line 843 (on 2.5.2)
TinyXML check for the header '<?xml'. But in some cases, lines like this '<?xml-something' ('<?xml-stylesheet' for example) can exists and Tinyxml consider this is a 'declaration' type. This sould perhaps be an 'unknown' type.
The solution I use for the moment is simply put a whitespace after the constant string.
replaced 'const char* xmlHeader = { "<?xml" };'
by 'const char* xmlHeader = { "<?xml " };'
I don't know if its an error, I do not know enough XML spec, but in my case (and perhaps in many cases cause XUL use the XML syntax above), their is an error parsing the XML file...
Hope this can help.
Raegis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all,
First, excuse me if my english is not a very good one.
I have found a 'potentially' bug in tinyxmlparser.cpp -> method 'TiXmlNode::Identify' -> line 843 (on 2.5.2)
TinyXML check for the header '<?xml'. But in some cases, lines like this '<?xml-something' ('<?xml-stylesheet' for example) can exists and Tinyxml consider this is a 'declaration' type. This sould perhaps be an 'unknown' type.
The solution I use for the moment is simply put a whitespace after the constant string.
replaced 'const char* xmlHeader = { "<?xml" };'
by 'const char* xmlHeader = { "<?xml " };'
I don't know if its an error, I do not know enough XML spec, but in my case (and perhaps in many cases cause XUL use the XML syntax above), their is an error parsing the XML file...
Hope this can help.
Raegis
Raegis --
Thanks for the note - the bug you refer to is (I think) already filed.
https://sourceforge.net/tracker/index.php?func=detail&aid=1155659&group_id=13559&atid=113559
lee
Ok, thanks, I have'nt seen.
But the bug seems reported since 2005 and the version 2.3.3.
Do you know when it will be corrected ?
Regards
Good question. We cleaned out a lot of (higher priority) bugs in the last release, so it has moved on up the queue.
lee