1.Many current DTDs incorporate ways to deal with some of these issues, but the breadth of the issues leads to more than just a DTD.
许多当前DTD合并了处理这些问题的方法，但这些问题所涉及的范围往往超出了DTD。
2.These helpers make your work a whole lot easier in trying to conform to a DTD (or in developing one).
这些帮助程序让您在尝试遵循DTD（或开发DTD）时更容易。
3.With a good framework of base classes in place, you can basically copy a DTD directly into a set of class definitions or initializations.
有了一个优秀的基类框架，基本上，您就可以将DTD直接复制到一组类定义或初始化中了。
4.When parsing XML, UAs do not always read the DTD, and thus may not know what the ID of an element is.
当解析XML时，浏览器不会总去读取DTD，因此可能会不知道一个元素的ID是什么。
5.The biggest problem with this was that a naive processor is likely to load that DTD URL, which might be an unwanted network operation.
这样做的最大问题是新型的处理器很可能加载此DTDURL，而这可能是一种不必要的网络操作。
6.With your DTD in a format that's more easily understood by Quick, you're almost ready to move to the next step.
现在，DTD的格式更容易被Quick理解了，您就要准备继续下一步了。
7.In an XML-based DTD, a new set of elements simply needs to be internally consistent and well-formed to be added to an existing DTD.
在基于XML的DTD中，新的元素组只需要内部一致并且格式良好，就可以添加到现有的DTD中。
8.When an XHTML document is created, the DTD to which it conforms is declared at the top of the document.
在创建XHTML文档时，在该文档的顶部声明了它应符合的DTD。
9.Each information type is defined in its own DTD module, which defines only the new elements for that type.
每种信息类型都在自己的DTD模块中定义，其中仅定义该类型的新元素。
10.Use parameter entities to pull external declarations into your DTD, or to create in-DTD macros to improve readability.
参数实体用于将外部声明拖到DTD中，或者用于创建DTD内部宏来改善可读性。