这个方法存在的问题是，它需要处理程序代码始终知道解析器位于文档的哪个位置，并需要它正确地解释组件。
The problem with this approach is that it requires your handler code to always know where the parser is in the document, and to interpret the components appropriately.
解析器的行为更像解释器，而不是编译器。
The parsers behave more like interpreters and are not compilers.
为解释这个以及其他有趣的特性，我需要描述一下索引器使用解析器的AST将如何工作以及它如何同PDOM进行交互。
To explain this and other interesting features, I need to describe what the indexer does with the parser's AST and how it interacts with the PDOM.
将这个样例标记包含在一个CDATA 区域中允许您原样编写标记，无需XML解析器试图将其解释为一个包含 元素的 元素。
Wrapping the sample markup in a CDATA section lets you write it as-is, without having the XML parser attempt to interpret it as a element containing an element.
如果您要使用一个解析器来解释某些语言中的代码，那么您应该向解析器返回一些内容来告知它您得到了什么记号。
If you're using a parser to interpret code in a new language, you will need to return something to the parser to tell it what tokens you've found.
解析器读取XML文档，解释语法并向应用程序传递有意义的对象。
The parser reads the XML document, decodes the syntax and passes meaningful objects to the application.
一旦您拥有了DTD或模式以及与其相配的XML文档，就需要一个解析器来读取并解释该XML文档。
Once you have a DTD or schema and the XML document to go with it, you'll need a parser to read and interpret the XML document.
可以通过两种方式实现：使用' '；或者使用blank _ p预定义解析器，这更好，它同时解释了空格和制表符。
You can do so two ways: use ' '; or, better, use the blank_p predefined parser, which accounts for both Spaces and tabs.
msgflow不在FileInput节点中执行记录检测，而是由TDS解析器解释输入数据中的每一行之间的CRLF。
WholeFile.msgflow does not perform record detection in its FileInput node, instead the CRLF between each line in the input data is interpreted by the TDS parser.
XMLNSC解析器解释XML标记以确定一个Invoice 记录在何处结束以及下一个 Invoice 记录在何处开始。
The XMLNSC parser interprets the XML tags to determine where one Invoice ends and the next one begins.
XMLNSC解析器解释XML标记以确定一个Invoice 记录在何处结束以及下一个 Invoice 记录在何处开始。
The XMLNSC parser interprets the XML tags to determine where one Invoice ends and the next one begins.
应用推荐