I've added the authentication properties for clarity.
为清楚起见，我增加了认证特性。
In my example, I added this attribute just for clarity.
在我的例子里，添加这个属性只是为了表述更清晰。
The preceding examples are exaggerated for clarity.
为了便于说明问题，前面的示例有点儿夸大了。
Declare your views and actions in the same package for clarity.
出于明确性的考虑，在同一个包中声明视图和操作。
For clarity, the entity name is composed of the domain identifier and -att.
为清晰起见，实体名称由域标识符和- att组成。
Many people like appending a .pl extension to all Perl programs for clarity.
为清晰起见，许多人喜欢将 .pl扩展名附加到所有Perl程序。
The code is shown in Listing 2 (log messages have been removed for clarity).
代码如清单2(为清楚起见，已删除了日志消息)所示。
The code samples use the JSP scripting language where appropriate for clarity.
代码示例使用jsp脚本语言是为了表示清楚。
The ServiceClass class' if...else logic branch remains the same (for clarity).
ServiceClass类的if...else逻辑分支保持不变（为了清晰起见）。
Note that namespaces have been left out, leaving only the prefixes for clarity.
请注意，为了清楚起见，已省去命名空间，仅保留了前缀。
Note that this code is optimized for clarity, not efficiency: it buffers too much.
请注意，这段代码是为了清楚起见，而没有考虑效率：它缓冲的内容太多。
The VMOPT.0 definition is on one long line, but here I've split it out for clarity.
定义实际上是一长条，但这里我为了清楚显示，把它分成了几段。
(For clarity, I haven't included exception-processing logic in the sample listings.)
(为清楚起见，本文没有在示例清单中加入异常处理逻辑。)
Persist in asking "why?" Look for sincerity, for logic, and for clarity of thought.
不停地问“为什么”，找寻思维之中的真实性、逻辑性以及清晰性。
For clarity, the entity name is composed of the domain identifier and the base element name.
为清晰起见，实体名称由域标识符和基本元素名称组成。
I look for clarity in their presentation and well-thought-out arguments and conclusions.
我在他们的介绍及慎重考虑后得出的论点和结论中找寻思路。
The last example left a lot of blank Spaces for clarity, so it's easy to line up the XML tags.
为了清晰，前一个示例保留了许多空白，使XML标记处于单独的行上。
That’s the root directory. Let’s list it now (for clarity, we’ll omit a lot of the entries)
那个目录就是根目录。
Listing 2 shows you how to handle the validation phase (with some code omitted for clarity).
清单2显示了如何处理验证阶段(为了保持简洁，省略了一些代码)。
There are some limitations in the EAz implementation example, mainly for clarity and simplicity.
EAz实现示例中存在某些限制，主要是清晰性和简单性。
NOTE: you should name your portlet something similar to the name of your Eclipse view for clarity.
注意：为简洁起见，应将portlet命名为与Eclipse视图名类似的名称。
Not all code changes have to be related to a user story, I just did that in all my examples for clarity.
不是所有的代码变更都必须与某个用户故事相关的，在例子中，我只是为了描述的清晰才这样做。
The code you receive has a lot of language translations of the title, which I have removed for clarity.
您收到的代码包含了使用许多语言翻译的标题。为了保持简洁，我把它们删除了。
These sections include examples derived from real-life artifacts that have been simplified for clarity purposes.
这些部分包含了来源于现实的工件，为了目的清楚而简化了的实例。
For clarity, the listing includes a graphical representation of the instances rather than the schema specification.
为了清晰，清单中包括实例的图形化表示而不是模式规范。
You will get back a response that looks like Listing 3 (again, I omitted the less important parts for clarity).
您将获得一个类似于 清单3 的响应（同样，我省略了次要部分以便更简明）。
We'll discuss them together for clarity and to illustrate their relationship with the other patterns previously applied.
为了清晰起见，我们将一起讨论它们，揭示它们与先前应用的其他模式的关系。
Note: The necessary exception handling logic has been excluded for clarity in most of the code examples in this article.
注释：必要的异常处理逻辑已经排除在这篇文章中的大多数样例代码，这主要是为了代码更清晰。
It is also not necessary to run the application on a dedicated server but I've used a dedicated server here for clarity.
同样也没有必要在专门的服务器上运行应用程序，不过为了清晰起见，这里我使用了一台专门的服务器。
Table 7 provides benchmark results for this approach, with the previous results (from Table 6) included for clarity.
表7提供了这种方法的测评结果，并包含了以前的结果(表6)以便进行对照。
应用推荐