四月份，随groovy- 1.0 -jsr -01发行版本提供的解决方案是一个更新过的语法以及一个用来对语法进行标准化的新语法内容解析器。
The solution, presented in April with the release of groovy-1.0-jsr-01, was an updated syntax and a new-syntax-savvy parser to standardize it.
然后，在对这个方法调用的响应中，解析器将构建该元素的子内容。
The element then builds the child content from the parser in response to the method call.
即使CDATA区域的内容完好无损地通过您的解析器，它们仍需是有效的XML数据字符，正如文档的字符编码所规定的一样。
Even though the contents of the CDATA section pass through your parser untouched, they still need to be valid XML data characters, as specified by the document's character encoding.
可以用一个内容处理程序来处理这两种情况，但每次解析器调用处理程序时，都需要进行一次检查，以查看到底是哪一种情况需要被处理。
You can have one content handler that handles both cases, but this requires a check to see which case needs to be handled each time the parser invokes the handler.
您将告诉解析器何时获取下一个文档片段，而不是在解析器看到文档后告诉您所看到的内容。
Rather than being told what the parser sees when the parser sees it, you tell the parser when to go fetch the next piece of the document.
在这个虚构的示例中，解析器并不关心声明的实际内容，因为它与句子没什么关系。
The parser in this made-up example does not care about the exact contents of the declaration, because it's tangential to the sentence.
第1个问题—为使解析器精确读取XML，存储在XML文件中的内容必须对实体进行相应地格式化。
Issue 1 — for a parser to read the XML accurately, the content stored within the XML file had to format entities accordingly.
实体是对数据的引用；根据实体种类的不同，xml解析器将使用实体的替代文本或者外部文档的内容来替代实体引用。
Entities are references to data; depending on the kind of entity, the XML parser will either replace the entity reference with the entity's replacement text or the contents of an external document.
如果您要使用一个解析器来解释某些语言中的代码，那么您应该向解析器返回一些内容来告知它您得到了什么记号。
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格式视图内容上，使用PHP的xml解析器查找文档和字段。
On the received XML-formatted view content, use PHP's XML parser to find documents and fields.
使用这种方法，应用程序沿着XML标记流移动指针，在每一步中检查解析器的状态来了解解析内容的更多信息。
Using this approach, the application advances a cursor over a stream of XML tokens, examining the parser state at every step to get more information about what was parsed.
DSL的使用可能会对读取使用 DSL编写的内容的工具造成明显的影响 —在这种场景中，通常都需要编写一个自定义解析器。
The use of a DSL may have a significant impact on the tools that read the content written in the DSL — there is always a requirement to write a custom parser in this type of scenario.
解析器不会在内存中长期保持内容，所以可以用于非常巨大的文件。
The parser doesn't keep anything in memory for very long, so it can be used for extremely large files.
图1显示了测试序列中前两个步骤所需的平均时间的总和，即使用解析器构建文档，并遍历文档表示以检查其中的内容。
Figure 1 shows the sums of the average times required for the first two steps in the test sequence, building a document from the parser, and walking the document representation to check the content.
这些标记之间的任何内容都将原封不动地通过xml解析器。
Anything between those bits of markup will pass through the XML parser untouched.
惟一的补救方法是，在执行查询时调用XML解析器来“搜索” XML文档，以便找到符合搜索条件的内容。
The only remedy is to invoke the XML parser at query execution time to "look into" the XML documents such that search conditions can be evaluated.
之后，脚本读取文件并把文件的大块内容发送到解析器。
After that, the script reads in the file and sends off chunks of the file to the parser.
换句话说，该构造管理由解析器构造的解析树的形状和内容。
In other words, this governs the shape and content of the parse tree that's constructed by the parser.
每块XML数据可以附加到文件后；或提供给SAX解析器，该解析器作用于元素和内容并在处理完毕后废弃XML数据块。
Each block of XML could be appended to a file; or it could be fed to a SAX parser that ACTS on the elements and contents and discards it once processed.
xml解析器可以利用这种父子结构来遍历文档，甚至修改文档的结构或内容。
XML parsers can use this parent-child structure to navigate to a document, and even to modify the structure or content of the document.
当以XML形式构建消息时，可以使用xml解析器来抽取消息字段的内容，而不考虑内容的大小。
When the message is built as XML, an XML parser can be used to extract the content of message fields without regard to the size of the content.
为这些测试开发的基准实用程序使用HTML解析器来处理Web内容，更新有关链接、表单和表等元素的信息。
The benchmarking utility developed for these tests USES an HTML parser to process Web content, updating information about links, forms, tables, and so on.
lexer实际上完成了指出它位于消息中的哪个地方的一些任务，但是解析器仍将所有内容放在一起。
The lexer actually does some of the work of figuring out where in a message it is, but the parser still ties everything together.
Pascal和VHDL等大小写敏感语言中的lexer要复杂一些，因为它们必须解析begin和begin等内容并为解析器生成相同的标记。
The lexers for case-insensitive languages like Pascal and VHDL are slightly more complicated because they must parse, for example, begin and begin and generate the same token for the parser.
为了检测哪些资源已被关闭，解析器应该在DB 2跟踪文件中查找包含以下内容的行。
In order to detect which resources have been closed, the parser should look into the DB2 trace file to find the lines containing.
为了让解析器了解您要开始谈论一个内容项，请使用itemscope属性。
To let the parser know you're starting to talk about an item, use the itemscope attribute.
对于不具备良好格式的html内容，lxml提供了两个有用的包：lxml . html模块和BeautifulSoup解析器。
For content in HTML that might not be well formed, LXML provides two useful packages: the lxml.html module and the BeautifulSoup parser.
为了更加可重用，这个解析器添加了以下内容
The resolver, in order to be more re-usable, adds the following
您还可以使用itemtype属性，让解析器知道您正在谈论的内容的类型。
You can also use the itemtype attribute to let the parser know what type of thing you're talking about.
从态度上看，gnosis. xml . validity将它继承的内容归功于Spark解析器。
In attitude, gnosis.xml.validity owes its heritage to the Spark parser.
应用推荐