diff options
author | Erlang/OTP <[email protected]> | 2017-03-14 15:59:23 +0100 |
---|---|---|
committer | Erlang/OTP <[email protected]> | 2017-03-14 15:59:23 +0100 |
commit | 4d658008be5a08ddadbe75ebadb9ef124436b76e (patch) | |
tree | c60fe1661ae9b747372a146edadbc8af6ca38036 /lib/xmerl/doc/src/notes.xml | |
parent | 3b72ab9407945eb7037c608ac2826b64ec17cdc6 (diff) | |
download | otp-4d658008be5a08ddadbe75ebadb9ef124436b76e.tar.gz otp-4d658008be5a08ddadbe75ebadb9ef124436b76e.tar.bz2 otp-4d658008be5a08ddadbe75ebadb9ef124436b76e.zip |
Prepare release
Diffstat (limited to 'lib/xmerl/doc/src/notes.xml')
-rw-r--r-- | lib/xmerl/doc/src/notes.xml | 55 |
1 files changed, 55 insertions, 0 deletions
diff --git a/lib/xmerl/doc/src/notes.xml b/lib/xmerl/doc/src/notes.xml index 12e64537ed..652560f60c 100644 --- a/lib/xmerl/doc/src/notes.xml +++ b/lib/xmerl/doc/src/notes.xml @@ -32,6 +32,61 @@ <p>This document describes the changes made to the Xmerl application.</p> +<section><title>Xmerl 1.3.13</title> + + <section><title>Fixed Bugs and Malfunctions</title> + <list> + <item> + <p> + The namespace_conformant option in xmerl_scan did not + work when parsing documents without explicit XML + namespace declaration.</p> + <p> + Own Id: OTP-14139</p> + </item> + <item> + <p> Fix a "well-formedness" bug in the XML Sax parser so + it returns an error if there are something more in the + file after the matching document. If one using the + xmerl_sax_parser:stream() a rest is allowed which then + can be sent to a new call of xmerl_sax_parser:stream() to + parse next document. </p> <p> This is done to be + compliant with XML conformance tests. </p> + <p> + Own Id: OTP-14211</p> + </item> + <item> + <p> Fixed compiler and dialyzer warnings in the XML SAX + parser. </p> + <p> + Own Id: OTP-14212</p> + </item> + <item> + <p> Change how to interpret end of document in the XML + SAX parser to comply with Tim Brays comment on the + standard. This makes it possible to handle more than one + doc on a stream, the standard makes it impossible to know + when the document is ended without waiting for the next + document (and not always even that). </p> <p> Tim Brays + comment: </p> <p> Trailing "Misc"<br/> The fact that + you're allowed some trailing junk after the root element, + I decided (but unfortunately too late) is a real design + error in XML. If I'm writing a network client, I'm + probably going to close the link as soon as a I see the + root element end-tag, and not depend on the other end + closing it down properly.<br/> Furthermore, if I want to + send a succession of XML documents over a network link, + if I find a processing instruction after a root element, + is it a trailer on the previous document, or part of the + prolog of the next? </p> + <p> + Own Id: OTP-14213</p> + </item> + </list> + </section> + +</section> + <section><title>Xmerl 1.3.12</title> <section><title>Fixed Bugs and Malfunctions</title> |