他们将一切内容都存储在“我的文档”文件夹或者桌面上。
They store everything in the My Documents folder or on the desktop.
我不想看到所有这些文档乱堆在我的桌子上。
我接受任何形式的帮助，如代码、文档、测试等。
I accept all kinds of help like code, documentation, tests,...
毫无例外的，我打开文档后总能找到明显的语法错误，比如没有反斜杠的空标签(应该是这样：)。
Invariably, I open the document and find an obvious syntax error such as an empty tag without the closing slash (it should look like this:).
一定要阅读它的文档——我保证您会头痛(也会有一些惊喜)，因为您会太多次拍击自己的前额，所以请先准备点阿斯匹林。
Be sure to look at the documentation — I guarantee you will get a headache (and some happy surprises) from slapping your forehead so many times, so grab some aspirin first.
最后，可以使用外部的验证解析器来验证文档，我将在本文的后面介绍。
Finally, you can validate documents with an external validating parser, which I discuss later in this article.
你需要将脚本复制到“我的文档”下的一个文件夹，虽然不够用户友好，但可以很好地工作。
Instead, you have to copy them into a directory in your My Documents folder, which is not exactly user-friendly, but works just fine.
遗憾的是，我发现可用的文档并非总是与极佳的工具相称。
Unfortunately, I have found that the documentation available is not always on par with the excellent tools.
我总是在它们自己的构件中编写商业规则文档，这样我可以在用例、参与者定义或从任何其它相应开发构件中引用它们。
I always document business rules in their own artifact, allowing me to refer to them in use cases, actor definitions, or from any other appropriate development artifact.
问：我正从事一个文档集成的项目。
然后我试着把文档输出成pdf文件，结果该文件不可读。
When I then tried exporting the document as a PDF file, it was unreadable.
我需要同文档团队合作保证他们明白如何编写高质量的教程和参考手册。
I met with the documentation team, making sure they understood how to write a good tutorial and reference for Excel Basic.
我将在在文档中定义实体小节中介绍如何声明命名实体。
I'll discuss how to declare named entities in the Defining entities in your documents section.
这是因为我在POD文档中使用了e语法，它指定对外部实体的引用。
This is because I used the LEE syntax in my POD documentation, which specifies a reference to an external entity.
请注意我已经选择要明确地控制我的JSON文档的样子。
Note that I've chosen to have explicit control over how my JSON document looks.
为了写出文档，我使用Crimson中内部定义的基本方法。
For writing out the document I use the basic method defined internally within Crimson.
在本例中，我希望预测新文档是否与Republicans或者Democrats相关。
In this case, I want to predict whether a new document is about Republicans or Democrats.
在本文中，我使用opensp来验证文档。
很快，我从json文档获取了一些数据—即纬度、经度和时间—创建一个Location实例，保存实例。
I promptly obtain a few pieces of data from the JSON document - namely the latitude, longitude, and time - create a Location instance, and save it.
现在，我的文档可以引用DanaBourgeois 保留的有关他的吉他的XML内容。 即便他更改了此信息，我也无需担心；我的文档始终是最新的，因为它只链接到他更新过的信息。
Now my document can reference the XML content that Dana Bourgeois keeps about his guitars.
如果某人在工作面试时对我说：“我对软件工程有很深入的理解，我的文档技巧非常棒。”我不知道我是否会雇用他。
If someone told me in a job interview that, "I'm really into software engineering — my documentation skills are excellent," I doubt if I would hire him.
我有没有用文档性的证据和例子来支持我的论据？
Have I supported my arguments with documented proof or examples?
但是，如果我的文档可以存储为使用FO的XML文档，那么不管我用的是什么应用程序，我可以保留格式信息。
If my document could be saved as an XML document using fo, however, I can expect to retain the formatting information regardless of the application I use.
当我开发XI时，我可能会发现我需要对这些文档做一些小的修正。
As I develop XI, I may find that I need to make small amendments to these documents.
在搜索字段内，我可以指定文档中必须包含的一个单词以及不能包含的另一个单词。
In the search field, I can specify a word that a document must contain, and another word the same document cannot contain.
他 们只是将所有的文件放到“我的文档”文件夹。
我学会了怎样让我的文档变得有秩序，怎样驾驭我的方案工作，怎样在家里和工作里变得有条理。
I learned how to keep my files in order, how to stay on top of my paperwork, to be organized at home and work.
我认为它也许代表查询，但是文档中没有说明。
我喜欢把RDDL文档称为资源集注，在定义RDDL的社区讨论中我就建议使用这个名称。
I like to call RDDL documents resource glosses, a name I recommended during the community discussions from which RDDL emerged.
我所说的不是早期设计文档，甚至也不是更为详细的设计文档；我说的是记录类上的各个方法和属性。
I am not talking about the early design documents, or even the more detailed design documents; I am talking about documenting individual methods and properties on classes.
应用推荐