Commit e20bb5aa authored by gerd's avatar gerd

Grammar, orthography, ...


git-svn-id: https://godirepo.camlcity.org/svn/lib-pxp/trunk@688 dbe99aee-44db-0310-b2b3-d33182c8eb97
parent 68e38da1
......@@ -137,7 +137,7 @@ instruction, only misc* element misc* or whole documents are possible).
</p>
<p>A long-standing bug has been found in the entity layer.
When an external entity A opens an exteral entity B, and B opens C,
When an external entity A opens an external entity B, and B opens C,
relative paths of C have been interpreted wrong.</p>
</li>
......
......@@ -213,7 +213,7 @@ The attribute "xml:lang" is not supported specially.
(The application can do this.)</p></li>
<li><p>
It is currently not possible to check for interoperatibility with SGML.
It is currently not possible to check for interoperability with SGML.
</p></li>
</ul>
......@@ -240,10 +240,10 @@ and solutions that are detected shortly before or after the release.</p>
been corrected. (This is the only change.)</p>
</li>
<li>
<p>Changed in 1.1.4:</p> <p>This is a bigger bugfix release
<p>Changed in 1.1.4:</p> <p>This is a bigger bug fix release
that addresses the following problems:</p>
<p>The parser does no longer show very bad performance when
large data nodes without linefeeds are parsed.</p>
large data nodes without line feeds are parsed.</p>
<p>Another performance problem with bigger DTDs has been solved,
too. Especially, the XHTML DTD can now be parsed quite quickly.</p>
<p>The interface Pxp_dtd.Entity has been extended, it is now possible
......@@ -263,7 +263,7 @@ overrides the outer xml:space='preserve' as defined in the XML standard.</p>
</li>
<li>
<p>Changed in 1.1.3:</p> <p>This release fixes a single
problem ocurring when PXP is compiled with installed
problem occurring when PXP is compiled with installed
netstring-0.10. (There is not any problem with netstring-0.91.)
</p>
</li>
......@@ -307,7 +307,7 @@ The interfaces have not been modified.</p>
<p>For the most important entity functions there is an
interface Pxp_document.Entity.</p>
<p>Although there are many extensions, the parser has been
speeded up.</p>
sped up.</p>
<p>The parser has been divided up into several packages, and
the directory structure of the distribution has been cleaned
up.</p>
......@@ -315,7 +315,7 @@ The interfaces have not been modified.</p>
One of them bases on Alain Frisch's wlex patch, which reduces
the size of executables if a UTF-8 parser is needed.</p>
<p>The parser works under Cygwin.</p>
<p>Of course several bugfixes. Note that most bugs have been
<p>Of course several bug fixes. Note that most bugs have been
added in the development cycle between 1.0 and 1.1; only
very few problems have been detected in the 1.0 release. I
hope that 1.1 has similar quality.</p>
......
......@@ -24,7 +24,7 @@
<p><em>Problem description:</em>
<code>
"We just install the pxp parser and have trouble in using it.
We always obtained an exception that we can not supress.
We always obtained an exception that we can not suppress.
Do you know if it's a problem of setting configuration options.
# let d = parse_dtd_entity default_config (from_file "DAG.xml");;
......
......@@ -173,7 +173,7 @@ references</title>
Stand-alone documents must not refer to entities which are declared in an
external entity. This parser applies this rule only: to general and NDATA
entities when they occur in the document body (i.e. not in the DTD); and to
general and NDATA entities occuring in default attribute values declared in the
general and NDATA entities occurring in default attribute values declared in the
internal subset of the DTD.
</p>
<p>
......@@ -211,12 +211,12 @@ element type "el" is treated as externally declared.
General entities can occur within the DTD, but they can only be contained in
the default value of attributes, or in the definition of other general
entities. The latter can be ignored, because the check will be repeated when
the entities are expanded. Though, general entities occuring in default
the entities are expanded. Though, general entities occurring in default
attribute values are actually checked at the moment when the default is
used in an element instance.
</p>
<p>
General entities occuring in the document body are always checked.</p>
General entities occurring in the document body are always checked.</p>
<p>
NDATA entities can occur in ENTITY attribute values; either in the element
instance or in the default declaration. Both cases are checked.
......
......@@ -19,7 +19,7 @@ Compilation is non-trivial because:
So the dependency relation of the lexer and the parser is modified;
in particular the "token" type that is normally defined by the
generated parser is moved to a common prdecessor of both lexer
generated parser is moved to a common predecessor of both lexer
and parser.
- Another modification of the standard way of handling parsers is that
......@@ -242,7 +242,7 @@ outputs that the next token must be scanned by Document_type.
It is interesting that this really works. The beginning of every lexical
context can be recognized by the lexer of the previous context, and there
is always a token that unambigously indicates that the context ends.
is always a token that unambiguously indicates that the context ends.
----------------------------------------------------------------------
The DTD object
......@@ -298,7 +298,7 @@ Newline normalization
The XML spec states that all of \n, \r, and \r\n must be recognized
as newline characters/character sequences. Notes:
- The replacement text of entities always contains the orginal text,
- The replacement text of entities always contains the original text,
i.e. \r and \r\n are NOT converted to \n.
It is unclear if this is a violation of the standard or not.
- Content of elements: Newline characters are converted to \n.
......
This diff is collapsed.
......@@ -426,7 +426,7 @@ class type [ 'ext ] node =
* <SIG> AUTO
* <DESCR> Gets the root node of the tree.
* Every node is contained in a tree with a root, so this method always
* succeeds. Note that this method searches the root,
* succeeds. Note that this method searches for the root,
* which costs time proportional to the length of the path to the root.
* <DOMAIN> All node types.
* </ID>
......@@ -613,7 +613,7 @@ class type [ 'ext ] node =
* which means here that their positions are counted seperately.
* All attribute nodes have positions from 0 to m-1; all namespace
* nodes have positions from 0 to n-1.
* - If [obj] is a root, this method raises [Not_found]
* - If [obj] is a root, this method raises [Not_found].
* --
* <DOMAIN> All node types.
* </ID>
......@@ -647,7 +647,7 @@ class type [ 'ext ] node =
* <CALL> obj # [sub_nodes]
* <SIG> AUTO
* <DESCR> Returns the regular children of the node as list. Only
* Elements, data nodes, comments, and processing instructions can
* elements, data nodes, comments, and processing instructions can
* occur in this list; attributes and namespace nodes are not
* considered as regular nodes, and super root nodes can only
* be root nodes and will never be children of another node.
......@@ -947,7 +947,7 @@ class type [ 'ext ] node =
method optional_list_attribute : string -> string list
(* <ID:type-node-optional-list-attribute>
* <CALL> obj # [required_list_attribute] name
* <CALL> obj # [optional_list_attribute] name
* <SIG> AUTO
* <DESCR> Returns the value of the attribute [name] as string list,
* i.e. if the value of the attribute is [Valuelist l], this method
......@@ -1109,7 +1109,7 @@ class type [ 'ext ] node =
* ([c = None]).
*
* Note that the comment string must not include the delimiters
* [<--] and [-->]. Furthermore, it must not contain any character
* [<!--] and [-->]. Furthermore, it must not contain any character
* or character sequence that are forbidden in comments, such
* as ["--"]. However, this method does not check this condition.
* <DOMAIN> Comment nodes.
......@@ -1121,7 +1121,7 @@ class type [ 'ext ] node =
* <CALL> obj # [comment]
* <SIG> AUTO
* <DESCR> Returns [Some text] if the node is a comment node and if
* [text] is the comment string (without the delimiters [<--] and
* [text] is the comment string (without the delimiters [<!--] and
* [-->]). Otherwise, [None] is passed back.
*
* Note: The [data] method also returns the comment string, but it
......@@ -2296,7 +2296,7 @@ type stripping_mode =
* - [`Strip_one]: If there is a whitespace character at the beginning/at
* the end, it will be removed. If there are more whitespace characters,
* only the first/the last is removed. Whitespace characters are space,
* newline, carriage return, tab.
* newline, carriage return, and tab.
* - [`Strip_seq]: All whitespace characters at the beginning/at the end are
* removed.
* - [`Disabled]: Do not strip whitespace.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment