Graphic scaling improvement is an enhanced feature that DITA Open
Toolkit 1.3 provides. DITA OT 1.3 supports this feature
in the transformation for different outputs, such
as HTML, XHTML, PDF, and FO. This feature is not applicable
in RTF output.
To implement this feature, you must first meet the following prerequisites:
In DITA 1.1, there are some attributes that you can use to set
the actual display size of the pictures in the
You can set the actual display size of the image in the output by taking the following steps:
You can also use the scaling function in setting the actual display size of the image in the output by taking the following steps:
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.
A specialization-unaware trademarking tool requires generalization of the contributed content. If the user runs all the content through the tool, the content is processed and filtered against the new attributes after the generalization. The new attributes are now collapsed into the "props" attribute.
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..
If you use several <shortdesc> elements inside the <abstract>
element, they will be concatenated when pulled for
hover help. After you format the source files, the
content inside the <abstract> element will be transformed
into normal text.
In DITA 1.1, you can use new element, <data>. This element and
the content inside it is ignored in the transformation
process of DITA files.
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.
DITA 1.1 supports the following new indexing elements:
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:
For example, you can add an index entry, as illustrated in
the following text in the DITA source file:
If you generate HTML output using the same source file, you can get the following index entries; however, instead of displaying page numbers, the HTML file display the terms after "see" and "see also" as hyperlinks. The "Illustration" hyperlink points to the index entry for "Illustration" under "I".
Index
entries will only be processed when you generate
HTMLHelp and JavaHelp. For HTMLHelp and JavaHelp, the index
contains an entry that uses the text "See xxx" or
"See also xxx". The "See xxx" or "See also
xxx" index entries
For example, if you put the following content in
the source file,
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.
For example, if
you put the following content in the source file,
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,
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
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.
For example, you can add
a page spanning index entry:
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
In DITA 1.1, you can use the <unknown> element to incorporate
existing standard vocabularies for special content,
like MathML and SVG, as inline objects.
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.