The third template suppresses all text nodes.
第三个模板删除了所有文本节点。
It returns all the concatenated element text nodes.
它会传回所有串连的项目文字节点。
Listing 29 shows the results with the text nodes ignored.
清单29展示了忽略文本节点后的结果。
So you have text nodes, element nodes, and attribute nodes.
所以可以有文本节点、元素节点和属性节点。
The example in Listing 5 does not add any of these TEXT nodes.
清单5中的示例没有添加任何这样的TEXT节点。
The element labels and element text nodes are stacked vertically.
元素标签与元素文本节点是垂直堆放的。
The XML document has only elements and element text nodes to parse.
XML文档只需要解析元素与元素文本节点。
The templates in Listing 18 isolate the elements from the text nodes.
清单18中的模板将元素从文本节点中分离出来。
This returns all the text contained in the logically-adjacent text nodes.
它返回在逻辑相邻的文本节点中所包含的所有文本。
Listing 4 shows you how to extract all the text nodes contained in a node.
清单4展示如何提取包含在节点中的所有文本节点？
This returns all the text contained in the logically - adjacent text nodes.
它返回在逻辑相邻的文本节点中所包含的所有文本。
node() matches all node types (elements, text nodes, comments, attributes, and so on)
node() 与所有的节点类型匹配（元素、文本节点、注释、属性，等等）
It needs to carefully avoid any comments or other non-text nodes that might appear.
必须小心避免任何注释或可能出现的其它非文本节点。
DOM provides this, in the form of a navigable tree of elements, attributes, and text nodes.
DOM提供了一个这样的模型，一个可导航的元素、属性和文本节点树。
Rules to match other nodes, such as text nodes, attributes, and comments, are comparatively rare.
匹配其它节点(如文本节点、属性和注释)的规则相对较少。
Optionally, normalize the text nodes of this new element, to make sure things are easier later on.
可能需要规范化这个新元素的文本节点以简化后续操作。
XML is stored in the database in a binary format, and the text nodes are stored as UTF-8 code points.
XML是以二进制格式存储在数据库中的，文本节点被存储为utf - 8代码点。
But it's still better to reference the element for which content should be returned to its text nodes.
但是，更好的方法仍然是引用内容将被返回给其文本节点的元素。
Each element is represented by an element node, and the actual data values are represented by text nodes.
每个元素由元素节点表示，实际的数据值由文本节点表示。
Other nodes, such as text nodes or XML comments, do not have a node name and therefore cannot be renamed.
文本节点或XML注释等其他节点没有节点名称，因此无法重命名。
The position function counts nodes-both elements and text nodes-even if the text is just white space.
position函数计数节点—元素和文本节点—即使文本只是空白。
In XPath 1.0 and XSLT 1.0, you would create 16 different text nodes and then group those nodes into a variable.
在XPath 1.0和XSLT 1.0中，您将创建16个不同的文本节点，然后将这些节点聚合到一个变量中。
This basically gets the text nodes out of the way and lets you deal with the text in your document more directly.
这基本上就完成了这个Text节点，并让您更直接地处理文档中的文本。
You'll find only the START_TAG and text event types, which correspond with element start tags and element text nodes.
您只会看到START _ TAG与TEXT事件类型，它们分别对应于元素开始标签与元素文本节点。
Listing 28 includes a template to ignore white space text nodes that affect the position of the elements in Listing 17.
清单28包含一个模板，它忽略会影响清单17中元素的位置的那些空白文本节点。
The code must select only ELEMENT type nodes, because TEXT nodes do not support this method and produce a non-recoverable error in Perl.
在代码中只能选择element类型的节点，因为该方法不支持TEXT节点，并且会在Perl中产生一个不可恢复的错误。
You no longer have to worry about the possibility that your text is being held by several adjacent text nodes that need to be concatenated.
不再需要担心文本包含在几个相邻的Text节点中，因而需要串接这些节点的情况。
For instance, text nodes, CDATA sections, comments, processing instructions, attributes, whitespace, document types, and XML declarations have values.
例如，文本节点、CDATA部件、注释、处理指令、属性、空格、文档类型和XML声明具有值。
Listing 1 (kill-content.xslt) is an XSLT script that eliminates all text nodes and attribute values, leaving essentially a skeleton of the node structure.
清单1 (kill - content .xslt)中的xslt脚本可以删除所有的文本节点和属性值，仅留下节点结构骨架。
The relevance between result fragments and user information need is the sum of the contributions of the element, attribution and text nodes in the fragments.
结果片段与用户信息需求的相关性是由其中的元素、属性和文本结点的总贡献决定的。
应用推荐