24.08.2015 Views

Oxygen XML Author plugin 13.2.0

Oxygen XML Author plugin 13.2.0

Oxygen XML Author plugin 13.2.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Author</strong> for DITA | 127• you have URI content references in your DITA topic files and you want to map them to local files when the map istransformedIn such situations you have to add the catalog to <strong>Oxygen</strong> <strong>XML</strong> <strong>Author</strong> <strong>plugin</strong> . The DITA Maps Manager view willsolve the displayed topic refs through the added <strong>XML</strong> catalog and also the DITA map transformations (for PDF output,for XHTML output, etc) will solve the URI references through the added <strong>XML</strong> catalog.DITA Specialization SupportThis section explains how you can integrate and edit a DITA specialization in <strong>Oxygen</strong> <strong>XML</strong> <strong>Author</strong> <strong>plugin</strong> .Integration of a DITA SpecializationA DITA specialization includes:• DTD definitions for new elements as extensions of existing DITA elements• optionally specialized processing, that is new XSLT template rules that match the extension part of the classattribute values of the new elements and thus extend the default processing available in DITA Open ToolkitA specialization can be integrated in <strong>Oxygen</strong> <strong>XML</strong> <strong>Author</strong> <strong>plugin</strong> <strong>XML</strong> <strong>Author</strong> with minimum effort.If the DTD's that define the extension elements are located in a folder outside the DITA Open Toolkit folder you shouldadd new rules to the DITA OT catalog file for resolving the DTD references from the DITA files that use the specializedelements to that folder. This allows correct resolution of DTD references to your local DTD files and is needed for bothvalidation and transformation of the DITA maps or topics. The DITA OT catalog file is called catalog-dita.xmland is located in the root folder of the DITA Open Toolkit.If there is specialized processing provided by XSLT stylesheets that override the default stylesheets from DITA OTthese new stylesheets must be called from the Ant build scripts of DITA OT.Important: If you are using DITA specialization elements in your DITA files it is recommended that youactivate the Enable DTD processing in document type detection checkbox in the Document Type Associationpage.Editing DITA Map SpecializationsIn addition to recognizing the default DITA map formats: map and bookmap the DITA Maps Manager view can alsobe used to open and edit specializations of DITA Maps.All advanced edit actions available for the map like insertion of topic refs, heads, properties editing, allow the user tospecify the element in an editable combo box. Moreover the elements which appear initially in the combo are all theelements which are allowed to appear at the insert position for the given specialization.The topic titles rendered in the DITA Maps Manager view are collected from the target files by matching the classattribute and not a specific element name.When editing DITA specializations of maps in the main editor the insertions of topic reference, topic heading, topicgroup and conref actions should work without modification. For the table actions you have to modify each action byhand to insert the correct element name at caret position. You can go to the DITA Map document type from the DocumentType Association page and edit the table actions to insert the element names as specified in your specialization. See thissection for more details.Editing DITA Topic SpecializationsIn addition to recognizing the default DITA topic formats: topic, task, concept, reference and composite,topic specializations can also be edited in the <strong>Author</strong> page.The content completion should work without additional modifications and you can choose the tags which are allowedat the caret position.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!