Thanks again for the proposition, and sorry for answering so late.
Well, even when doing what you said, there is still the problem that recognized_string or original_string contains rubbish in many cases.
In the meantime, I managed to write my own XML processor which recognizes all the syntactic elements of an XML document (according to the XML 1.0 specification at the latest revision), even when these are arbitrarily nested; incorrect nesting (i.e. a malformed document) is recognized and reported.
As required by my application, no entities or other syntactic elements are interpreted, replaced or specially treated otherwise. Since all my documents are UTF-8, my processor does not evaluate or respect the encoding of an XML document.
This is just what I needed, so I am tagging this thread as solved now.
Thanks for all the help again,
Nocturnus
In reply to Re^4: Seeking for advice: XML parsing with special requirements
by Nocturnus
in thread Seeking for advice: XML parsing with special requirements [Solved]
by Nocturnus
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |