How to do this
Make sure the its:translate attribute is available for the root element of your documents, and for any element that has text content.
For details on how to add an attribute such as its:translate to a DTD, an XSD schema, or a RELAX-NG schema, see: Section 4.2: Adding an Attribute to an Existing DTD or Schema.
Make also sureUse the its:rules element is available somewhere in your documents, for exampleexpression in the headerselector part if there is one. The its:rules element provides accessattribute to the its:translateRule element which can beassign used to change the translatability property of attributes.information.
In the following document, the content of the par elements are normally translatable, but in this instance, the last one should remain in English. Declaring its:translatebe as an optional attribute of the par element allows the author to set the given paragraph as not translatable.translated:
<myDoc
xmlns:its="http://www.w3.org/2005/11/its"
its:version="1.0">
<par>To apply these terms to you library, attach the following notice.
It is safest to attach it to the start of each source file to most
effectively convey the exclusion of warranty; and each file should
have at least the "copyright" line and a pointer to where the full
notice is found.</par>
<par>The notice should read (preferably in English):</par>
<par
its:translate="no">This library is free software; you can
redistribute it and/or modify it under the terms of the GNU Lesser
General Public License as published by the Free Software Foundation;
either version 2.1 of the License, or (at your option) any later
version. This software is distributed as open source under LGPL.</par>
</myDoc>
[Ed. note: TODO: Maybe this is more an example for the author. Maybe we should have and example showing ITS inclusion in a DTD or schema.][Example's source code]
For existing DTD and schema:
If you are working with DTD or a schema where there is a way to override translatability information that is not its:translate, you should provide anof ITS rules document where you use the its:translateRule element to associate this mechanism to the ITS Translate data category.used.
For example, [DITA 1.0] offers its own translate attribute, and [Glade] provide its own translatable attribute. Both have the same function as its:translate.
The following rules indicate howIn to associate the DITA translatedocument attribute with the ITS Translate data category. The order in which the rules aretext listed is important: You must first defined the general rules, then two rules for the case of the elements with translate="no" (one for the elements, one for the attributes of children elements), and lastly, the rule for translate="yes"emphasized.
<its:rules
xmlns:its="http://www.w3.org/2005/11/its" version="1.0">
<!-- Rules for the translate attributes -->
<translateRule selector="//*[@translate='no']" translate="no"/>
<translateRule selector="//*[@translate='no']/descendant-or-self::*/@*" translate="no"/>
<translateRule selector="//*[@translate='yes']" translate="yes"/>
</its:rules>
[Example's source code]
You can find a more complete example of how DITA markup is associated with ITS in Section 5.4.2: Relating ITS to Existing Markup in DITA.
Why doing this
In some cases,define the author of a document mayparts need to change the translatability property onuse parts of the content, overriding defaults or moregeneral rules.element:
