课程稽核资料的建议格式为何？
What is the recommended format for a program's audit material?
请将下面遵从了建议格式的SQL示例与另一个进行了其他格式化的示例进行比较。
Compare below an SQL example conforming to the suggested format, and another that has been formatted without this concern.
我建议以此格式绘制你的分支图，而且可以将其挂到团队所在房间的墙上。
I suggest drawing a picture of your branches in this format and putting up on the wall in the team room!
我建议只使用SOAP绑定，因为它受到最广泛地支持，并且在大多数情况下没有理由不用SOAP作为消息格式。
I suggest using the SOAP binding simply because it is the most commonly supported and there is no reason not to use SOAP as a message format in most cases.
本文包含了一些可以让格式变得统一的建议，这样您就可以平稳和可预测地进行数据迁移，同时维护一个一致的层级结构。
This article includes tips to make the formats to uniform so that you get a smooth, predictable movement of data while maintaining a consistent hierarchy.
建议您抽查一些报告，验证不存在软件更新创建的格式问题。
It is suggested that you spot check some reports to validate that there are no formatting issues being created by the software update.
关于应该使用哪种XML，我无法提供太多建议；但是，如果某种标准格式(比如XHTML、SVG或X3D)能够很好地适应您的数据，就可以选用它。
I can't provide too much guidance on which XML you should use, except that you want to choose a standard format (such as XHTML, SVG, or X3D.) that provides a good enough fit for your data.
我们建议微软停止把自己不稳定无证明的垃圾格式命名成这样，发音和我们差不多，谢了。
We call it Stop Naming Your Unstable Undocumented Shitty Format to Sound Like Ours Thanks.
如果比较的状态显示为“NoDifferences”，那么会建议进行抽查，以确保没有发生格式更改。
If there are "no Differences" shown for the status of the compare, then spot checking is suggested to make sure that formatting changes have not occurred.
对终极web黑客的建议：在XHTML5文档的顶部始终包含默认的命名空间，并为其他嵌入的xml格式使用相应的命名空间。
Recommendation for the desperate web hacker: Always include the default namespace at the top of XHTML5 documents and use the appropriate namespaces for other, embedded XML formats.
如果您还不熟悉这种格式，建议您先参阅关于这个主题的Wikipedia文章(参见参考资料中的链接)。
If you are not already familiar with it, I suggest you start with the Wikipedia article on the subject (see Resources for a link).
阅读本文时，建议手头上准备一份Atom 1.0格式规范的副本，以便作为所讨论的各种元素的交叉参考。
As you read through this overview, I recommend that you keep a copy of the Atom 1.0 format specification handy as a cross-reference for the various elements discussed.
我建议您在更熟悉synth格式并且能够设置XML中的继承模型之前，使用每个组件一种式样(one - style - per - component)的设置。
I recommend using the one-style-per-component setup until you are more familiar with the Synth format and can set up inheritance models in the XML.
虽然“格式分数”在SAT中被用来抵制猜答案，但像这样的建议却是通过积极鼓励猜答案来打倒“格式分数”的意义。
Even though formula scoring is used in SAT to discourage guessing, an advice like this defeats the purpose of formula scoring by actively encouraging guessing.
本文中的示例将遵循该建议书的格式。
The examples in this article will follow the format of that recommendation.
因此，我们建议将文字“选填”以淡灰色的格式显示在输入框的内部，就像图6所示的那样。
Therefore, we recommend placing the word 'optional' inside the text boxes in grayed fonts, as shown in Figure 6.
如果您需要找出某些名称或编号，以便设置特定的屏蔽，建议您观察格式化输出的一个示例。
If you need to find some names or Numbers to set up a particular mask, it is recommended that you look in a sample of formatted trace output.
如果图像是GIF格式的，建议先把它转换成PNG格式，他们是类似的，但是PNG格式文件比较小。
IF the image is in GIF format, I recommend converting it to PNG because they're similar, but PNGs will usually be smaller in file size.
本尼建议老板格式化生产工序等等。
Benny suggested that the boss format the production process, and so forth.
同样的，每当你一觉察到有令你不安的念头，都可以运用今天的观念。下面所建议的格式就是为此目的而设的。
As usual, use today's idea whenever you are aware of a particular thought that arouses uneasiness. The following form is suggested for this purpose.
使用建议的方法，我们可以利用多种格式的现有资产：uml模型、逻辑或物理数据模型(ddl格式)、XSD模式和代码模块。
With the proposed approach, we can leverage existing assets of many formats: UML models, logical or physical data models (in DDL), XSD schemas, and code modules.
建议的用户接口格式。每一个配置文件描述用户应该如何访问配置文件，从而维持一个统一的用户体验。
Suggested user interface formats. Each profile describes how a user should view the profile so that a consistent user experience is maintained.
如果可随意选择格式，我们建议您优先考虑可读性和完整性，其次才是维持小规模和低开销。
If the choice of format is open, we recommend prioritizing human readability and integrity over smallness and overhead. Your format choices (summarized in Table 1) are.
McFerran建议采用简单、清晰易读的格式。
Report选项卡显示EVTK对该数据的报告、每个所选字段的摘要、整个日志的表格式摘要以及一系列调整建议。
The report TAB shows the GC and Memory Visualizer's report on the data, with a summary of each selected field, a tabular summary of the whole log, and a series of tuning recommendations.
我曾经建议使用验证器，如XMLSchema，这会实现一个严格格式的结构。
I've even gone so far as to recommend using a validator, like XML Schema, that will enforce a rigid structure.
他建议：“一定要找人对你的简历进行校对，对格式和内容提出意见。”
"Be sure to have someone proofread your resume and critique it for format and content," he suggests.
用于格式化和分发的建议CPU数量取决于格式化算法和分发日志记录设置的复杂性。
The recommended number of CPUs for formatting and distribution depends on the complexity of the formatting algorithm and of the distribution logging settings.
用于格式化和分发的建议CPU数量取决于格式化算法和分发日志记录设置的复杂性。
The recommended number of CPUs for formatting and distribution depends on the complexity of the formatting algorithm and of the distribution logging settings.
应用推荐