可以向任意类型的活动中添加注释、问题，及响应。
Comments, questions, and responses can be added to any type of Activity.
还有一个更严重的问题：生成的注释可能会破坏某些样式表。
And there's a more serious problem: the generated annotations may break some stylesheets.
对于下个月的文章，我将回到在上一期文章中简要提到的一个问题，即注释与外部配置文件之间的权衡。
For next month's column, I'm going back to an issue I mentioned briefly in an earlier column: the trade-offs between annotations and external configuration files.
JPA允许通过注释来“懒散地”加载属性，但正如我们在后面看到的，当考虑到实体是一个POJO时，此方法自身也有问题。
JPA allows for "lazily" loading the properties through annotation, but as we will see in a later point, this approach creates its own problems when coupled with thinking that the entity is a POJO.
帕黛以单独一栏的注释解决了这个问题，她将这些段落置于诗篇正文旁方便一起阅读。
Ms Padel has overcome this problem by having paragraphs of notes run, in a single column, beside the texts of the poems so that they can be read side by side.
到目前为止，您已经看到如何在OptimQueryTuner各项功能的帮助下分析和调优问题查询，这些功能包括查询注释、访问计划图等等。
So far, you've seen how you can analyze and tune a problem query with the assistance of Optim query Tuner capabilities, such as query annotation, access plan graph, and so on.
首先考虑这样一种情况：假设您通过定制的InProgress注释标记一个类正在开发之中，这完全没有问题，对吧？
First, take a use case: Suppose that you mark a class as being in progress, through your own custom InProgress annotation. No problem, right?
非常确信，增加 “-fPIC” 可以解决这个问题，这正是错误消息建议的（也是Makefile 中有关其他两个常见的 64位体系架构的注释给我们的提示）。
Sure enough, adding "-fPIC," as the error message suggested (and as hinted at by the Makefile's comments about two other common 64-bit architectures), fixes the problem.
这种方法被这个领域内的资深科学家，多伦多大学的GeoffreyHinton称为“深度学习”(见注释5)，它不必仅限于处理计算机视觉问题。
This approach (which Geoffrey Hinton of the University of Toronto, a doyen of the field, has dubbed "deep learning") need not be confined to computer-vision.
与其他注释(如书签、断点和语法问题)类似，这些注释也是通过编辑器左侧空白上的符号来指示的。
Like other annotations such as bookmarks, breakpoints, and syntax problems, these are indicated by a symbol in the left margin of the editor.
在一些国家，比如印度和比利时，英语充其量不过是第三或第四种语言，多语言注释或者多语言代码的问题是比您想像的还要大的一个问题。
In countries, such as India and Belgium, where English is a third or fourth language at best, multilingual comments or multilingual code is a slightly bigger issue than you might imagine.
第二个问题就是在任何重要的样式表执行中都会产生许多注释—这样可能会由于注释太多而难以找到那些您真正感兴趣的注释。
A second worry is the generation of a lot of comments in any nontrivial stylesheet execution — perhaps so many that it would be hard to find the ones you're really interested in.
使用相关统计数据来注释有问题的查询，这样可以更好地理解DB 2使用哪些内容来进行评估。
Annotate the problem query with relevant statistics to better understand what the DB2 optimizer is using for its estimations.
编写定制的注释器是解决特定业务问题的有效方法。
Writing custom annotators can be a useful way to solve a specific business problem.
当我在后面的文章中研究注释和外部配置文件的权衡时，我会再回到这个问题上。
I'll return to this point in a later column when I look at the trade-offs between annotations and external configuration files.
一个问题就是生成的注释所提供的信息比期望的要少。
One concern is that the generated comments are less informative than they might be.
这将涵盖在注释器的UIMA代码中发生的问题，以及在定制注释器的注释器代码中发生的问题。
This covers all problems that occur in the UIMA code of your annotator and problems that occur in the annotator code of a custom annotator.
如果这能够解决该问题，那么注释器将返回一个比较长的返回值。
If this solves the problem, your annotator may return unexpectedly long return values.
在找出了实际错误后，我又在上面找到的问题后面加了注释。
After pointing out the actual errors, I made a point of adding comments about those things I just mentioned.
在某些情况下，有必要从更细的级别获取UIMA日志消息来调试注释器的问题。
On some occasions it may be necessary to debug the problems of your annotator by retrieving UIMA log messages of a finer level.
其他工作可能包括为图片添加注释，指出问题或疑问，让中心医院的医生解答。
Additional things could include annotating an image to point out a problem or a question to be answered by a doctor at a central hospital.
如果UIMA 注释器的结果大于它们映射到的结果列，那么可能出现难以识别的问题。
Possible problems that are not easy to identify can occur if the results of the UIMA annotator are larger than the result column they are mapped to.
问题是，加入的所有空格、分行符、注释都增加了脚本文件大小和应用程序的加载时间。
The problem is, all of the whitespace, line breaks, and comments that you add to your code increase the file size of the script and the load time of your application.
模型提供了一个深刻老到的观点，以了解怎样通过注释性的UML表达业务问题。
Models provide vivid insight into how business problems can be expressed through notational UML. A typical requirements gathering includes these components.
通常，最简单的解决办法是在configure中注释掉相应的测试，并直接设置出问题的环境变量。
Often, the easiest thing to do is simply to comment out the relevant test in configure, and set the variable in question directly.
如果您有任何问题的话，请提出来在注释的表格。
If you have any questions, feel free to ask in the comment form below.
需要注意的主要问题是v1注释。
The main thing I want to call attention to is the v1 comment.
当然，我可以使用JPA的EntityListeners注释来处理这个问题，这意味着我可以监控删除事件，在事件发生时删除Runner实例。
I, of course, can handle this by using a JPA's EntityListeners annotation, which means I can hook into a removal event and use it to remove Runner instances.
当然，我可以使用JPA的EntityListeners注释来处理这个问题，这意味着我可以监控删除事件，在事件发生时删除Runner实例。
I, of course, can handle this by using a JPA's EntityListeners annotation, which means I can hook into a removal event and use it to remove Runner instances.
应用推荐