你可以用下面的文档开始。
因此，查询将返回下面的文档作为结果，但这并不是预期的结果。
Thus, the query would return the following document as a result, which was not intended.
例如，下面的文档（输入）将变成其后的文档（输出）。
For example, the document below (Input) will become the following document (Output). Notice that the line breaks occur after 65 characters as specified by the lineWidth attribute
usr/share/doc下面的文档大概有 118MB。
The documents under /usr/share/doc take about 118 MB of space.
自定义：可以在下面的文档之间创建关系：它们包含的信息超出了使用预定义的关系自动采集的信息的范围。
Custom: You can create relationships between documents that go beyond the information that can be automatically captured using the set of predefined relationships.
例如，如果有些“customerinfo”文档还包含“assistant”信息，就像下面的文档一样。
For example, if some of the "customerinfo" documents also contain "assistant" information, like the one below.
这是在进行文档标准化(documentnormalization)操作时可能造成的部分结果，我们将在下面的文档标准化一节中对此加以描述。
This is one of the results you can obtain as part of an operation called document normalization that we describe in the section document normalization.
下面的清单15显示一个经过大量简化的返回文档。
Listing 15 below shows a greatly simplified version of the returned document.
考虑下面的XML文档。
正如我们在下面的样本涉众目标文档中所看到的那样，目标满足因素并没有如建议的那样为用户场景清晰地进行了标注。
As can be seen in the sample stakeholder goals document below, goal satisfiers do not map as neatly to user stories as this suggests.
下面的例子返回 第 1部分中所用的订单文档。
The following example returns to the purchase order document used in Part 1.
也可以为所有的XML文档或只为特定的某个文件指定缺省编码(请参阅下面的验证XML代码并对其字符进行编码)。
You can also specify a default encoding for all XML documents or for only a specific file (see Validating and character encoding XML code below).
对于库根下面的每个文件夹和文档，这个feed包含一个AtomEntry。
The feed contains an Atom Entry for each folder and document under the library root.
如果成功地执行了步骤3，则使用下面的命令分解XML文档。
If step 3 goes through successfully, then decompose the XML document using the following command.
现在，假设您要将其转换成下面的XHTML文档
Now suppose you want to transform it to the following XHTML document
MetadataWorkbench管理员可以通过执行下面的步骤导入扩展映射文档。
A Metadata Workbench administrator can import extension mapping documents by doing the following.
现在，假设您已有下面的XML文档。
下面的例子只选择了customer表中用customer模式验证之后的文档。
The below example selects only those documents from the customer table which are validated using customer schema.
不同的TMap需求规格技术非常适合于建立基于RUP系统文档的测试用例(也可以参见下面的“技术”一节)。
Various TMap specification techniques are very well suited for constructing test cases based on RUP system documentation (see also the "techniques" section below).
例如，在下面的部门表中，我们为每个部门使用一个XML文档（中等粒度）。
For example, in our department table below, we use one XML document per department (medium granularity).
不过你得明白，并不是所有这些软件我们都试用和测试过，所以下面的信息大部分是取自产品文档。
Note that not all products have been tried and tested. Most of the analysis below is based on information gathered from the documentation of the products.
或者——这也是下面的示例中采用的方法——附件也可以包含指向现有策略文档的链接，而不是包含策略定义本身。
Alternatively — and this is the approach used in the example below — the attachment can also contain a link to an existing policy document, instead of the policy definition itself.
下面的图表显示了对每个文档进行50次处理所需的平均时间。
The charts below show the average time required for 50 passes on each document.
下面的例子显示如何在RPX中访问文档，打印这些文档中包含的需求的名字和标签。
This example shows how to access documents in the RPX, and print the name and tag of the requirements contained within those documents.
下面的例子消除了组合两个文档时对某一公共元素产生歧义。
This is an example of disambiguating a common element when two documents are combined.
在下面的例子中，我要介绍的过滤器能够忽略XML文档的整个分支。
In the next example, I'll show a filter that skips a whole branch of an XML document.
所有文档转换完成后，可以继续下面的工作，根据需要发布所有的内容，不会遗漏任何内容。
After all documents are converted, moving forward, you can publish as needed with all your content, without missing a beat.
注意：我们将建立示例文档，在下面的清单2到清单7 中有详细描述。
Note: We'll build the sample document detailed in Listings 2 through 7 below.
例如，假设需要使用以下格式的XML文档作为客户机请求的响应发送，如下面的清单2所示。
For example, assume an XML document, using the following format, is to be sent as a response to a request by a client, as shown Listing 2 below.
请注意，清单1中定义的数据类型是在下面的清单2中所示的WSDL文档的开头导入的。
Note that the data types defined in Listing 1 are imported at the beginning of the WSDL document shown in Listing 2, below.
应用推荐