XMLmind logoCompany | Contact | Site Map
 
 

Change History

1.2 (March 6, 2010)

Enhancements:

Bug fixes:

  • XSL-FO output format: a footnote inherited its font style and its font weight from its container.
  • XSL-FO output format: converting a map which ends with a reltable pulling topics (that is, these topics are not referenced directly or indirectly anywhere in the topicref hierarchy) and instructing ditac to generate an index at the end of the document caused the conversion to fail with error message: "fatal error reported by the XSLT engine: A sequence of more than one item is not allowed as the first operand of 'eq'".
  • A notices element having no href attribute caused the conversion to fail with error message: "An empty sequence is not allowed as the result of function u:nextSequenceName()".
  • Made all the IDs automatically generated by ditac as short as possible. The reason of this change is that some output formats (e.g. .docx) do not support cross-references having long IDs.

    The following sed script may be used to convert old automatically generated IDs to new automatically generated IDs:

    s/__XSL_RESOURCE_\([0-9]*\)__/__RES\1/g
s/__TOC__/__TOC/g
s/__TOC_ENTRY_\([0-9]*\)__/__TOCE\1/g
s/__TITLE__/__TT/g
s/__TITLE_PAGE__/__TP/g
s/__TABLE_LIST__/__LOT/g
s/__MAP__\.ditamap/__MAP.ditamap/g
s/__INDEX_LIST__/__IDX/g
s/__IMAGE_\([0-9]*\)__/__IMG\1/g
s/__IDENTIFIER__/__ID/g
s/__ID\([0-9A-Za-z]*\)__/I_\1_/g
s/__FIGURE_LIST__/__LOF/g
s/__EXAMPLE_LIST__/__LOE/g
s/__END_OF_TOPIC__/__EOT/g
s/__END_OF_FRONTMATTER__/__EOFM/g
s/__END_OF_BODYMATTER__/__EOBO/g
s/__END_OF_BACKMATTER__/__EOBM/g
s/__-__/__/g

Incompatibilities:

  • Though not mandated by the DITA standard, XMLmind DITA Converter now checks that all the topics which compose the document to be converted have distinct IDs. If this is not the case, a fatal error is reported.
  • The qualified ID of a descendant element of a topic is now transformed as follows: topicID/descendantID becomes topicID__descendantID in the generated content. (The separator string being used comprises two underscore characters.) Previously, it was topicID__-__descendantID, which was longer and less readable.

1.1.0_02 (December 4, 2009)

Enhancements:

  • XMLmind DITA Converter now detects the following suspicious case and reports a warning: a topic is referenced in the map but does not appear in the output document. This is generally caused by a missing or erroneous chunk specification.

1.1.0_01 (November 10, 2009)

This is just a patch release. Its distribution differs from the 1.1 distribution only by the ditac.jar it contains.

Bug fixes:

  • Using a topicref to include a map containing only reltables into another map (see example below) didn't work.
    <topicref href="TS_EX_reltable.ditamap" format="ditamap"/>

1.1.0 (November 9, 2009)

Enhancements:

  • XMLmind DITA Converter now allows to convert DITA documents to Eclipse Help.
  • Replaced parameters page-header and page-footer by the following parameters: header-left, header-center, header-right, header-separator, header-left-image, header-center-image, header-right-image, footer-left, footer-center, footer-right, footer-separator, footer-left-image, footer-center-image, footer-right-image. The new parameters allow to better control the contents of page headers and footers. For example, such parameters may now be used to display a logo in a page header or footer:
    -p header-left-image in/icon_small.svg 
-p footer-center "Page %page-number% of %page-count%"

    Notice the mix of text and variables in footer-center.

  • Added a title-page parameter to all the XSLT stylesheets. The possible values of this parameter are:
    auto
    Default value. Automatically generate a ``title page'' based on the title and metadata of the map.
    none
    Do not generate a title page.
    URI_of_custom_title_page
    Specifies the URI of a custom title page. This custom title page is an XHTML file for XHTML-based formats (XHTML, HTML Help, etc). This custom title page is an XSL-FO file for FO-based formats (PDF, RTF, etc). Such custom title pages are generally hand-written.
  • The automatically generated title page now includes the last created or revised child element of the critdates element found in the metadata of a map. The value of the golive attribute (publication date) has priority over the value of created/@date and revised/@modified (modification date).

    If the value of a date is formatted as YYYY-MM-DD, then the generated title page contains a localized form corresponding to the language of the map. Otherwise, the value of the date (e.g. "October 12, 2007") is copied as is to the generated title page.

  • The searchtitle of a topic, if any, is now used to specify the title of the generated HTML page. The searchtitle element may be specified in topic/titlealts or in topicref/topicmeta.
  • Added the -options (short name -o) option. This option allows to specify a text file containing command-line arguments. Example:
    $ ditac -v -o html.options foo.htm foo.ditamap

    If html.options contains:

    -format html
-p css http://www.acme.com/css/acme.css

    then this is equivalent to running:

    $ ditac -v -format html -p css http://www.acme.com/css/acme.css \
    foo.htm foo.ditamap
  • The -toc option will not add a toc element to a map when this map contains a single topicref having no nested topicref descendants.
  • Slightly changed the default chunking policy of ditac. When a map does not specify chunk="to-content" at all and when this map is to be converted to a screen media (XHTML, HTML Help, etc), ditac adds chunk="to-content" to all topicrefs which are direct children of the map. However, if a map contains a single topicref, ditac will also add chunk="to-content" to all topicrefs which are direct children of this root topicref.
  • Added a minimal workaround for the following RenderX XEP limitation: space-after.conditionality="discard" is not implemented, fallback value is "retain". As a consequence of this limitation, there was much too space between list items.
  • The generated messages (Table of Contents, Chapter, etc) have been translated to Russian by Nikolay Rastegaev.

Bug fixes:

  • No content was generated for the itemgroup element.

Incompatibilities

  • Replaced parameters page-header and page-footer by parameters: header-left, header-center, header-right, header-separator, header-left-image, header-center-image, header-right-image, footer-left, footer-center, footer-right, footer-separator, footer-left-image, footer-center-image, footer-right-image.
  • Java Help/HTML Help parameter show-title-page has been replaced by a combination of new common parameter title-page and of new Java Help/HTML Help parameter add-toc-root:
    show-title-pageEquivalent title-page and add-toc-root
    show-title-page=yestitle-page=auto and add-toc-root=no
    show-title-page=notitle-page=no and add-toc-root=no
    show-title-page=toc-roottitle-page=auto and add-toc-root=yes
  • The value of Java Help/HTML Help parameter number-toc-entries is now no by default. This is consistent with the default value of common parameter number which is an empty string. That is, by default, nothing is numbered.

1.0.0_01 (October 22, 2009)

This is just a patch release. Its distribution differs from the 1.0 distribution only by the ditac.jar it contains.

Enhancements:

  • Any attribute (that is, not only audience, platform, product, rev, otherprops and props) can be used to filter or flag an element. Previously, it was not possible to use attributes belonging to a namespace (e.g. xml:lang).

Bug fixes:

  • When a .ditaval file contained the following specification
    <prop att="audience" action="exclude" /> 
<prop att="audience" val="external" action="include" />

    elements having a audience="external" attribute were excluded too. This was caused by the fact that action="include" and action="passthrough" were parsed but after that, such actions were completely ignored.

1.0 (September 23, 2009)

Initial release.