summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorarseny.kapoulkine <arseny.kapoulkine@99668b35-9821-0410-8761-19e4c4f06640>2010-07-01 12:10:36 +0000
committerarseny.kapoulkine <arseny.kapoulkine@99668b35-9821-0410-8761-19e4c4f06640>2010-07-01 12:10:36 +0000
commit841aefb1207e759de551d3cf4d46e77b54344eaa (patch)
treefde55a154a2995499c0600cc2708db6c3c3dbf40
parente997848bb5f1ea0759ed9bf2543597b9234ff16c (diff)
docs: Minor wording fix
git-svn-id: http://pugixml.googlecode.com/svn/trunk@556 99668b35-9821-0410-8761-19e4c4f06640
-rw-r--r--docs/manual.qbk4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/manual.qbk b/docs/manual.qbk
index 7a0d880..4a76df8 100644
--- a/docs/manual.qbk
+++ b/docs/manual.qbk
@@ -750,13 +750,13 @@ The algorithm used for `encoding_auto` correctly detects any supported Unicode e
[endsect] [/encoding]
-[section:w3c W3C recommendation conformance]
+[section:w3c Conformance to W3C specification]
pugixml is not fully W3C conformant - it can load any valid XML document, but does not perform some well-formedness checks. While considerable effort is made to reject invalid XML documents, some validation is not performed because of performance reasons.
There is only one non-conformant behavior when dealing with valid XML documents: pugixml does not use information supplied in document type declaration for parsing. This means that entities declared in DOCTYPE are not expanded, and all attribute/PCDATA values are always processed in a uniform way that depends only on parsing options.
-As for rejecting invalid XML documents, there are a number of incompatibilities with W3C recommendation, including:
+As for rejecting invalid XML documents, there are a number of incompatibilities with W3C specification, including:
* Multiple attributes of the same node can have equal names.
* All non-ASCII characters are treated in the same way as symbols of English alphabet, so some invalid tag names are not rejected.