From 58be69c574390715e4f72ed7e835b236958f9d9c Mon Sep 17 00:00:00 2001
From: "arseny.kapoulkine"
Date: Mon, 8 Jan 2007 16:24:53 +0000
Subject: Removed comments (cppguru does not want them), refactored
chartype_symbol parsing, documentation fixes
git-svn-id: http://pugixml.googlecode.com/svn/trunk@28 99668b35-9821-0410-8761-19e4c4f06640
---
docs/index.html | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
(limited to 'docs')
diff --git a/docs/index.html b/docs/index.html
index 4066dc4..c843bdb 100644
--- a/docs/index.html
+++ b/docs/index.html
@@ -42,7 +42,7 @@
Introduction
pugixml is just another XML parser. This is a successor to
pugxml (well, to be honest, the only part
-that is left as is is wildcard matching code, the rest was either heavily refactored or rewritten
+that is left as is is wildcard matching code; the rest was either heavily refactored or rewritten
from scratch). The main features (call it USP) are:
@@ -59,7 +59,7 @@ mode, with the exception of DTD related issues and XML namespaces)
like expat will; it will try to recover the state even if meeting an error (like finding matching
tags for closing ones); it will parse files with data in wrong encoding; and so on)
- clean interface (a heavily refactored pugxml's one)
-- more or less unicode-aware (actually, it assumes UTF-8 encoding of the input data, though
+
- more or less Unicode-aware (actually, it assumes UTF-8 encoding of the input data, though
it will readily work with ANSI - no UTF-16 for now (see Future work), with
helper conversion functions (UTF-8 <-> UTF-16/32 (whatever is the default for std::wstring & wchar_t))
- fully standard compliant code (approved by Comeau
@@ -238,16 +238,16 @@ be just skipped:
- If parse_pi is on, then processing instructions (<? ... ?>) are put into DOM
-tree (with node type node_pi, otherwise they are discarded. Note that for now the prolog
+tree (with node type node_pi) otherwise they are discarded. Note that for now the prolog
(<?xml ... ?>) is parsed as a processing instruction.
Default value: off
In W3C mode: on
- If parse_comments is on, then comments (<!-- ... -->) are put into DOM
-tree (with node type node_comment, otherwise they are discarded.
+tree (with node type node_comment) otherwise they are discarded.
Default value: off
In W3C mode: on
- If parse_cdata is on, then the content of CDATA section (<![CDATA[[ ... ]]>)
-is put into DOM tree (with node type node_cdata, otherwise it is discarded.
+is put into DOM tree (with node type node_cdata) otherwise it is discarded.
Default value: on
In W3C mode: on
- If parse_ws_pcdata is off, then the content of PCDATA section (it's the plain text
@@ -282,7 +282,7 @@ and for attribute values (replacing <lt; with <, c; with L, etc.).
- If parse_wnorm_attribute is on, then the whitespace normalisation is done for attribute
values (this includes replacing any space-like character by a space character, converting sequences of
spaces into a single space and trimming of leading/trailing spaces)
-
Default value: on
+
Default value: off
In W3C mode: off
- If parse_wconv_attribute is on, then the whitespace conversion is done for attribute
values (this is a subset of whitespace normalization, and includes only replacing space-like characters
@@ -324,7 +324,7 @@ These are:
A couple of words on flag usage. The parsing options are just a set of bits, with each bit corresponding
to one flag. You can turn the flag on by OR-ing the options value with this flag's constant:
- parse_w3c | parse_wnorm_pcdata
+ parse_w3c | parse_wnorm_attribute
or turn the flag off by AND-ing the options value with the NEGation of this flag's constant:
--
cgit v1.2.3