Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Even a bit better wording, probably (at least the native speaker say so). |
---|---|
Downloads: | Tarball | ZIP archive | SQL archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
a3edd2a308f36833c140c16f73c86a50 |
User & Date: | rolf 2019-08-16 13:57:35 |
Context
2019-08-19
| ||
16:43 | Fixed typos. check-in: 8e8341da68 user: rolf tags: trunk | |
2019-08-16
| ||
15:20 | Merged from trunk. check-in: 5cf43bf74a user: rolf tags: schema | |
13:57 | Even a bit better wording, probably (at least the native speaker say so). check-in: a3edd2a308 user: rolf tags: trunk | |
13:04 | Corrected speeling and better wording. check-in: 7ec866b33f user: rolf tags: trunk | |
Changes
Changes to doc/domNode.xml.
188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 |
you must specify the attribute name with prefix, even if you want to set an already existing attribute to a new value. While searching, if the attribute already exists, only the given <m>uri</m> and the localname of the <m>qualifiedName</m> is used.</p> <example>$node setAttributeNS "http://some.uri.com/wow" prefix:attr1 attrValue</example> <p>If the uri is the empty string and the attribute name doesn't have a prefix, this 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 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> |
| | |
188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 |
you must specify the attribute name with prefix, even if you want to set an
already existing attribute to a new value. While searching, if the attribute
already exists, only the given <m>uri</m> and the localname of the
<m>qualifiedName</m> is used.</p>
<example>$node setAttributeNS "http://some.uri.com/wow" prefix:attr1 attrValue</example>
<p>If the uri is the empty string and the attribute name has no
prefix, this 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 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>
|