In DITA 1.1, there are some attributes that you can use to set the actual display size of the pictures in the <image> tag, such as "width", "height", and so on.
OASIS DITA 1.1 provides the DITA architects with an enhanced feature, extensible metadata attributes. If the architects want to achieve multiple purposes in one attribute, especially in a selective attribute, they can use the extensible metadata attributes.
The following example illustrates how people of different roles use the extensible metadata attributes in DITA 1.1.
After you perform these actions, another user can reuse the content.
You can now use a new element <abstract> in DITA topics. The <abstract> element can include complex markups besides the <shortdesc> element. You can put the <shortdesc> element inside the <abstract> element, together with many other elements. The following examples illustrate how you can use the <abstract> element..
Example 1
In DITA 1.0, you can only use the <shortdesc> element that cannot contain the <p> element.<shortdesc>This is a short description in DITA 1.0. It <b>cannot</b> contain paragraphs.</shortdesc>
Example 2
This example illustrates how you can use different elements besides <shortdesc> inside the <abstract> element, and apply different styles to the text inside the <abstract> element.<abstract> <shortdesc>This is the short description</shortdesc> <ol> <li>This is a <i>list</i>.</li> </ol> <p>This is a <b>paragraph</b>.</p> <codeblock>Here are some codes.</codeblock> <filepath>This is the file path.</filepath> </abstract>
Example 3
This example illustrates how you can use both the <shortdesc> element and plain text inside the <abstract> element.<abstract><shortdesc>This topic is about short description.</shortdesc>. Short description is very important, so read more.</abstract>
As an author, when you create DITA files, you can add the <data> element, and put content inside it. When you transform the DITA files to the output that you want, the transformation ignores the <data> element and any content inside.
As a specializer, when you specialize the <data> element, and put information inside the specialized element, you can create a transform override to use the information.
In DITA 1.0, you cannot specify the <see> and <see also> index entries by using the current <indexterm> element. The DITA1.1 standard introduces the following new child elements for <indexterm> that support this functionality:
<indexterm>computer <index-see>monitor</index-see> <index-see-also>Illustration</index-see-also> </indexterm>Then, if you generate a PDF output with the indexing function enabled, you can see the following index entries in the PDF output:
computer 43 See monitor See also IllustrationThe "monitor" and "Illustration" entries after "see" and "see also" will not be links to the "monitor" and "Illustration" index entries in a PDF output.
<indexterm>computer <index-see>monitor</index-see> </indexterm>the output is as follows:
computer See monitor
With the DITA 1.1 standard, you can specify a sort phrase and sort index entries under the sort phrase. This feature provides you with the flexibility to sort an index entry in a different way. Typically you can disregard insignificant leading text, such as punctuation or words like "the" or "a". If you want to sort <data> under the letter D rather than the character "<", you can include such an entry under both the punctuation heading and the letter D. Thus, there can be two index entry directives differentiated only by the sort order.
<indexterm>data<index-sort-as>key</index-sort-as></indexterm> <indexterm>indextest<index-sort-as>abc</index-sort-as></indexterm>the output should be:
indextest data
If you have written an XML book with many punctuation-laden entries in its index, you can use the <index-sort-as> element to specify how the sorting method of the entries if the punctuation marks are eliminated. For example, <data> is always displayed as an entry <data> in the index term under the letter D; otherwise, all the entries with punctuations will be sorted under "<".
Here is another example. In a translation project, a document needs to be translated into Japanese. Many of the index entries contain kanji, which need to be sorted in phonetic order. The translators, who can understand the language and see the entry in its context, can insert the <index-sort-as> elements into the <indexterm> elements as part of their localization work.
In DITA OT 1.3, you can indicate page ranges instead of individual references over consecutive pages. Page ranges indicate where the index entry links to an extended discussion that goes over a number of pages. This is typically manifested as a page range like 34-36. This is distinguished from individual references over consecutive pages (34, 35, 36). The page-range indexing function is enabled when you use the FO plugin.
<indexterm>DITA<index-range-start/></indexterm>. Later in the same topic, you can add a range terminating marker: <indexterm>DITA<index-range-end/></indexterm>. This spans 4 pages on the paper, as illustrated in the following example.
DITA, 46-49
With enabled ICU interface, DITA Open Toolkit 1.3 helps you get correctly sorted index output for different languages.
During normal transformation, the toolkit tries to find if there are ICU classes inside the classpath element. If ICU exists, the toolkit uses ICU's Collator class to do the comparing and sorting work. If no ICU is found, the toolkit will use JDK's Collator class to do the comparing and sorting work. ICU is packed in the big package in DITA OT 1.3
As an author, when you create DITA files, you can add the <unknown> element, and put content inside it. The <unknown> element and any content inside it is ignored when you transform the DITA files to your desired output.
As a specializer, when you specialize the <unknown> element, and then put information inside the specialized element, you can create a transform override that allows the information to appear correctly in the output.