Posted to tcl by mr_calvin at Thu Oct 05 08:43:43 GMT 2017view raw
- Index: doc/dom.xml
- ==================================================================
- --- doc/dom.xml
- +++ doc/dom.xml
- @@ -334,11 +334,11 @@
- <commanddef>
- <command><cmd>dom</cmd> <method>createNodeCmd</method>
- <m>?-returnNodeCmd?</m> <m>?-tagName name?</m> <m>?-jsonType jsonType?</m> <m>?-namespace URI?</m> <m>(element|comment|text|cdata|pi)Node</m> <m>commandName</m></command>
- <desc>This method creates Tcl commands, which in turn create
- tDOM nodes. Tcl commands created by this command are only
- - avaliable inside a script given to the domNode methods
- + available inside a script given to the domNode methods
- <m>appendFromScript</m> or <m>insertBeforeFromScript</m>. If
- a command created with <m>createNodeCmd</m> is invoked in
- any other context, it will return error. The created command
- <m>commandName</m> replaces any existing command or
- procedure with that name. If the <m>commandName</m> includes
- Index: doc/domDoc.xml
- ==================================================================
- --- doc/domDoc.xml
- +++ doc/domDoc.xml
- @@ -151,13 +151,13 @@
- </commanddef>
- <commanddef>
- <command><method>asHTML</method> <option>?-channel
- channelId?</option> <option>?-escapeNonASCII?</option> <option>?-htmlEntities?</option> <option>?-doctypeDeclaration <boolean>?</option></command>
- - <desc>Returns the DOM tree serialized acording to HTML rules
- + <desc>Returns the DOM tree serialized according to HTML rules
- (HTML elements are recognized regardless of case, without end
- - tags for emtpy HTML elements etc.) as string or sends the
- + tags for empty HTML elements etc.) as string or sends the
- output directly to the given channelId. If the option
- <m>-escapeNonASCII</m> is given, every non 7 bit ASCII
- character in attribute values or element PCDATA content will
- be escaped as character reference in decimal representation.
- If the option <m>-htmlEntities</m> is given, a character is
- @@ -167,11 +167,11 @@
- the document. The default is, to do not. The DOCTYPE name will
- always be the element name of the document element without
- case normalization. An external entity declaration of the
- external subset is only emitted, if the document has a system
- identifier. The doctype declaration will be written from the
- - avaliable information, without check, if this is a known
- + available information, without check, if this is a known
- (w3c) HTML version information or if the document confirms to
- the given HTML version.</desc>
- </commanddef>
- <commanddef>
- @@ -279,17 +279,17 @@
- <desc>Returns the internal subset of the doctype declaration of the
- document, if there is one, otherwise the empty string. If there is a value
- given to the method, the internal subset of the document is set to this
- value. Note that none of the parsing methods preserve the internal subset
- of a document; a freshly parsed document will always have an empty internal
- -subset. Also note, that the method doesen't do any syntactical check on a
- +subset. Also note, that the method doesn't do any syntactical check on a
- given internal subset.</desc>
- </commanddef>
- <commanddef>
- <command><method>cdataSectionElements</method> <m>(?URI:?localname|*) ?<boolean>?</m></command>
- - <desc>This method allows to control for which element nodes
- + <desc>This method allows one to control for which element nodes
- the text node children will be serialized as CDATA sections (this affects only
- serialization with the asXML method, no text node is altered in any
- way by this method). IF the method is called with an element name as
- first argument and a boolean with value true as second argument, every
- text node child of every element node in the document with the same
- @@ -309,11 +309,11 @@
- serialized as CDATA section nodes.</desc>
- </commanddef>
- <commanddef>
- <command><method>selectNodesNamespaces</method> <option>?prefixUriList?</option></command>
- - <desc>This method allows to control a document global prefix
- + <desc>This method allows one to control a document global prefix
- to namespace URI mapping, which will be used for selectNodes
- method calls (on document as well as on all nodes, which
- belongs to the document) if it is not overwritten by using
- the -namespaces option of the selectNodes method. Any
- namespace prefix within an xpath expression will be first
- @@ -370,11 +370,11 @@
- <commanddef>
- <command><method>toXSLTcmd</method> ?<m>objVar</m>?</command>
- <desc>If the DOM tree represents a valid XSLT stylesheet, this method
- transforms the DOM tree into an xslt command, otherwise it returns error. The
- -created xsltCmd is returnd and stored in the <m>objVar</m>, if a var name was
- +created xsltCmd is returned and stored in the <m>objVar</m>, if a var name was
- given. A successful transformation of the DOM tree to an xsltCmd removes the
- domDoc cmd and all nodeCmds of the document.
- <p>The syntax of the created xsltCmd is:</p>
- @@ -451,11 +451,11 @@
- </commanddef>
- <commanddef>
- <command><method>getElementById</method> <m>id</m></command>
- <desc>Returns the node having a id attribute with value
- -<m>id</m> or the emtpy string, if no node has an id attribute with that value.</desc>
- +<m>id</m> or the empty string, if no node has an id attribute with that value.</desc>
- </commanddef>
- <commanddef>
- <command><method>firstChild</method> <variable>?objVar?</variable></command>
- <desc>Returns the first top level node of the document.</desc>
- @@ -623,11 +623,11 @@
- <p>Otherwise, if an unknown method name is given, the command with the
- same name as the given method within the namespace <samp>::dom::domDoc</samp> is
- tried to be executed. This allows quick method additions on Tcl level.</p>
- <p>Newly created nodes are appended to a hidden fragment list. If they
- -are not moved into the tree they are automaticaly deleted as soon as the whole
- +are not moved into the tree they are automatically deleted as soon as the whole
- document gets deleted.</p>
- </section>
- <seealso>
- Index: doc/domNode.xml
- ==================================================================
- --- doc/domNode.xml
- +++ doc/domNode.xml
- @@ -129,11 +129,11 @@
- </commanddef>
- <commanddef>
- <command><method>getElementById</method> <m>id</m></command>
- <desc>Returns the node having an id attribute with value
- -<m>id</m> or the emtpy string if no node has an id attribute with that value.</desc>
- +<m>id</m> or the empty string if no node has an id attribute with that value.</desc>
- </commanddef>
- <commanddef>
- <command><method>hasAttribute</method> <m>attributeName</m></command>
- <desc>Returns 1 if the object node contains an attribute with name
- @@ -195,11 +195,11 @@
- method has the same effect as the method <b>setAttribute</b>.</p>
- <example>$node setAttributeNS "" attri "some Value"</example>
- <p>With the exceptions of the special prefixes "xmlns" and "xml" you
- -always must provide a non emtpy <m>uri</m>, if your <m>qualifiedName</m> has a
- +always must provide a non empty <m>uri</m>, if your <m>qualifiedName</m> has a
- prefix. It is not recommended to set xml namespace declarations. The effects are complicated and not always obvious up to resulting a not well-formed serializations after further processing.</p></desc>
- </commanddef>
- <commanddef>
- <command><method>removeAttributeNS</method> <m>uri</m> <m>localName</m></command>
- @@ -360,11 +360,11 @@
- <p>Similar to the way described above to inject literals in a secure
- way into the XPath expression using tcl variable references there is a
- syntax to inject element names from tcl variables. At every place
- where the XPath syntax allows a node test there could be a tcl
- variable reference (in any form), just the leading $ replaced with %.
- -This allows to select nodes with 'strange' (invalid, according to the
- +This allows one to select nodes with 'strange' (invalid, according to the
- appropriate XML production rule) node names which may be needed in
- case of working with JSON data.</p>
- <p>The option <m>-namespaces</m> expects a tcl list with prefix /
- namespace pairs as argument. If this option is not given, then any
- @@ -412,17 +412,17 @@
- </desc>
- </commanddef>
- <commanddef>
- <command><method>getLine</method></command>
- - <desc>Returns the line number of that node in the orignal parsed
- + <desc>Returns the line number of that node in the originally parsed
- XML.</desc>
- </commanddef>
- <commanddef>
- <command><method>getColumn</method></command>
- - <desc>Returns the column number of that node in the orignal parsed
- + <desc>Returns the column number of that node in the originally parsed
- XML.</desc>
- </commanddef>
- <commanddef>
- <command><method>asList</method></command>
- @@ -467,12 +467,12 @@
- <commanddef>
- <command><method>asHTML</method> <option>?-channel channelId?</option>
- <option>?-escapeNonASCII?</option> <option>?-htmlEntities?</option></command>
- <desc>Returns the DOM substree starting from the current node as the
- -root node of the result serialized acording to HTML rules (HTML elements are
- -recognized regardless of case, without end tags for emtpy HTML elements etc.),
- +root node of the result serialized according to HTML rules (HTML elements are
- +recognized regardless of case, without end tags for empty HTML elements etc.),
- as string or sends the output directly to the given channelId. If the option
- <m>-escapeNonASCII</m> is given, every non 7 bit ASCII character in attribute
- values or element PCDATA content will be escaped as character reference in
- decimal representation. If the option <m>-htmlEntities</m> is given, a
- character is written using its HTML 4.01 character entity reference, if one is
- @@ -526,11 +526,11 @@
- <commanddef>
- <command><method>toXPath</method> <m>?-legacy?</m></command>
- <desc>Returns an XPath, which exactly addresses the given
- node in its document. This XPath is only valid as there are no changes to DOM
- tree made later one. With the -legacy option, other XPath expressions
- -are returnd, which doesn't work in all cases.</desc>
- +are returned, which doesn't work in all cases.</desc>
- </commanddef>
- <commanddef>
- <command><method>getBaseURI</method></command>
- <desc>Returns the baseURI of the node. This method is deprecated in
- @@ -539,11 +539,11 @@
- <commanddef>
- <command><method>baseURI</method> <m>?URI?</m></command>
- <desc>Returns the present baseURI of the node. If the optional
- argument URI is given, it sets the base URI of the node and of all of its child
- -nodes out of the same enitity as node to the given URI.</desc>
- +nodes out of the same entity as node to the given URI.</desc>
- </commanddef>
- <commanddef>
- <command><method>disableOutputEscaping</method> <m>?boolean?</m></command>
- <desc>This method works only for text nodes; for every other node it
- @@ -550,11 +550,11 @@
- returns error. Without the optional argument it returns, if disabling output
- escaping is on. The return value 0 means, the characters of the text node will
- be escaped, to generate valid XML, if serialized. This is the default for
- every parsed or created text node (with the exception of that text nodes in a
- result tree of an XSLT transformation, for which disabling output escaping was
- -requested explicitely in the stylesheet). The return value 1 means, that output
- +requested explicitly in the stylesheet). The return value 1 means, that output
- escaping is disabled for this text node. If such a text node is serialized
- (with asXML or asHTML), it is literally written, without escaping of the
- special XML characters. If the optional boolean value <m>boolean</m> is given,
- the flag is set accordingly. You should not set this flag to 1 until you
- really know what you do.</desc>
- @@ -608,11 +608,11 @@
- <p>The <m>-xsltmessagecmd</m> option sets a callback for xslt:message elements
- in the stylesheet. The actual command consists of the script, given as argument
- to the option, appended with the XML Fragment from instantiating the
- xsl:message element content as string (as if the XPath string() function would
- -have been applied to the XML Fragment) and a flag, which indicates wether the
- +have been applied to the XML Fragment) and a flag, which indicates whether the
- xsl:message has an attribute "terminate" with the value "yes". If the
- called script returns anything else then TCL_OK then the xslt
- transformation will be aborted, returning error. If the called script
- returns -code break the error message is empty, otherwise the result
- code is reported. In case of terminated transformation the outputVar,
- Index: doc/expat.xml
- ==================================================================
- --- doc/expat.xml
- +++ doc/expat.xml
- @@ -555,11 +555,11 @@
- <desc>If <boolen> is true and the document does not have an
- external subset, the parser will call the -externalentitycommand script with
- empty values for the systemId and publicID arguments. This option must be set,
- before the first piece of data is parsed. Setting this option, after the
- parsing has started has no effect. The default is not to use a foreign DTD. The
- -default is restored, after reseting the parser. Pleace notice, that a
- +default is restored, after resetting the parser. Pleace notice, that a
- -paramentityparsing value of "never" (which is the default) suppresses any call
- to the -externalentitycommand script. Pleace notice, that, if the document also
- doesn't have an internal subset, the -startdoctypedeclcommand and
- enddoctypedeclcommand scripts, if set, are not called.</desc>
- </optdef>
- @@ -693,11 +693,11 @@
- <commanddef>
- <command><cmd>parser</cmd> <method>reset</method></command>
- <desc><p>Resets the parser in preparation for parsing another
- -document. A parser cannot be reseted from within one of its handler callbacks
- +document. A parser cannot be reset from within one of its handler callbacks
- (neither directly nor indirectly) and will raise a tcl error in this
- cases.</p></desc>
- </commanddef>
- </commandlist>
- </section>
- Index: doc/expatapi.xml
- ==================================================================
- --- doc/expatapi.xml
- +++ doc/expatapi.xml
- @@ -67,11 +67,11 @@
- </arglist>
- </section>
- <section>
- <title>DESCRIPTION</title>
- -<p>The functions described in this manual allows to add C level coded event
- +<p>The functions described in this manual allows one to add C level coded event
- handler to an tDOM Tcl expat parser objects. A tDOM Tcl expat parser object is
- able to have several Tcl scripts and C functions associated with an specific
- event. If the event occurs, first the Tcl scripts then the C functions
- associated with the event are called in turn.</p>
- @@ -86,11 +86,11 @@
- struct CHandlerSet *nextHandlerSet;
- char *name; /* refname of the handler set */
- int ignoreWhiteCDATAs; /* ignore 'white' CDATA sections */
- void *userData; /* Handler set specific Data Structure;
- - the C handler set extention has to
- + the C handler set extension has to
- malloc the needed structure in his
- init func and has to provide a
- cleanup func (to free it). */
- CHandlerSet_userDataReset resetProc;
- @@ -158,11 +158,11 @@
- <p><m>resetProc</m> and <m>freeProc</m> must have arguments that match the
- type</p>
- <syntax>void (Tcl_Interp *interp, void *userData)</syntax>
- - <p><m>resetProc</m> is called in case the parser is reseted with
- + <p><m>resetProc</m> is called in case the parser is reset with
- <samp><parserObj> reset</samp> and should do any necessary cleanup and
- reinitializing to prepare the C handler set for a new XML document. The
- <m>freeProc</m> is called, if the parser is deleted and should do memory
- cleanup etc. </p>
- Index: doc/tnc.xml
- ==================================================================
- --- doc/tnc.xml
- +++ doc/tnc.xml
- @@ -40,18 +40,18 @@
- </commanddef>
- <commanddef>
- <command><cmd>tnc</cmd> <m>parserObj</m> <method>getValidateCmd</method> <option>?validateCmdName?</option></command>
- - <desc><p>Returns a new created validation command, if one is avaliable
- + <desc><p>Returns a new created validation command, if one is available
- from the parser command, otherwise it signals error. The name of the validation
- command is the <m>validateCmdName</m>, if this optional argument was given, or
- -a random choosen name. A validation command is avaliable in a parser command,
- +a random chosen name. A validation command is available in a parser command,
- if the parser with tnc enabled was previously used, to parse an XML document
- with a valid doctype declaration, a valid external subset, if one was given by
- the doctype declaration, and a valid internal subset. The further document
- -doesn't need to be valid, to make the validation command avaliable. The
- +doesn't need to be valid, to make the validation command available. The
- validation command can only get received one time from the parser command. The
- created validation command has this syntax:</p>
- <syntax><cmd>validationCmd</cmd> <m>method</m> <m>?args?</m></syntax>
- @@ -69,12 +69,12 @@
- <commanddef>
- <command><method>validateTree</method> <m>elementNode</m> <m>?varName?</m></command>
- <desc>Checks, if the given subtree with <m>domNode</m> as root element
- -is a posible valid subtree of a document conforming to the DTD information
- -represented by teh validation command. IDREF could not checked, while
- +is a possible valid subtree of a document conforming to the DTD information
- +represented by the validation command. IDREF could not checked, while
- validating only a subtree, but it is checked, that every known ID attribute in
- the subtree is unique. Returns 1, if the subtree is OK, 0 otherwise. If the
- <m>varName</m> argument is given, then the variable it names is set to the
- detected reason for the validation error or to the empty string in case of
- a valid subtree.</desc>