| | Home|News|Products|Store|Contact |
| XMLmind DITA Converter | ||
Enhancements:
Downloadzh (Chinese), thanks to a
contribution made by Ray Technologies.Enhancements:
<topicref href="topic-for-group-A.dita" audience="group(A)"/> <topicref href="topic-for-group-B.dita" audience="group(B)"/> <topicref href="topic-for-group-C.dita" audience="group(C)"/>
one could use the following DITAVAL, as documented in "Darwin Information Typing Architecture (DITA) Version 1.3 Part 2: Technical Content Edition, 2.4.3.2 Filtering":
<val> <prop action="exclude" att="audience" val="group"/> <prop action="include" att="group" val="A"/> </val>
but not this alternative DITAVAL (which had no effect):
<val> <prop action="exclude" att="group"/> <prop action="include" att="group" val="A"/> </val>
Ditac now supports both the above specifications.
nn (Norwegian Nynorsk)
and nb (Norwegian Bokmål), thanks to a contribution made by
Leif Halvard Silli.ditac-N_N_N-plus-fop.zip now
contains Apache FOP 2.10 (including hyphenation and MathML
support). This XSL-FO processor is automatically declared and thus,
ready to be used to generate PDF or PostScript.Bug fixes:
css
was not declared in the EPUB manifest causing all EPUB
files created using XMLmind XML Editor (which uses this
css parameter) to be rendered without any style by Apple
Books®.Enhancements:
Bug fixes:
Enhancements:
Bug fixes:
ditac-N_N_N-plus-fop.zip containing a bundled Apache
FOP, a -foconverter option invoking possibly another
version of FOP, possibly with different FOP options, was ignored. It was
the built-in command invoking bundled FOP which was always used to
convert a DITA document to PDF.Enhancements:
-fopconf configuration_file
command-line option lets you specify the location of an Apache FOP configuration file. Ignored unless option
-fop is also specified.-ahfconf configuration_file
command-line option lets you specify the location of an Antenna House Formatter configuration file. Ignored
unless option -ahf is also specified.Enhancements:
mathjax-url XSLT stylesheet parameter now
points to latest 3.x version of the MathJax mml-chtml
component.ditac-N_N_N-plus-fop.zip now
contains Apache FOP
2.9 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Enhancements:
add-copiable-links
parameter which makes it easy copying links to chapters, sections,
tables, figures, etc, in order to share them with others. For example,
send by email a link to a chapter found in the generated Web Help.corporate layout in addition to the classic
and simple layouts.Enhancements:
Enhancements:
topicrefs do not point to any topic and
essentially consist in a title (navtitle attribute or
topicmeta/navtitle element). For example
(part and chapter are
topicrefs):<part>
<topicmeta>
<navtitle>User guide</navtitle>
<shortdesc>Everything you need to know about Gizmo.</shortdesc>
</topicmeta>
<chapter href="intro.dita"/>
...
</part>When converting a map containing such
topicrefs to other formats, previous versions of
ditac used to just consider the title of the
topicref and to ignore any other topicmeta.
Now the topicmeta/shortdesc content, if any,
also appears in the output.
Bug fixes:
data:" URLs
(e.g. <image
href="data:image/svg+xml;base64,PD94b...ZnPgo="/>)
somewhat worked but:ditac reported a false "invalid value for
attribute href" error when the -validate
command-line option was used.image/@scale
attribute caused ditac to report a "Cannot
determine the size of image 'data:image/...+Cg==': unknown protocol:
data" error and such images were not scaled.Enhancements:
lib/resolver.jar) by the XMLResolver
(lib/xmlresolver.jar).ditac-N_N_N-plus-fop.zip now
contains Apache FOP
2.8 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Enhancements:
Bug fixes:
topicrefs pointing to URLs having a query component.figgroup element was silently ignored
by the XSL stylesheets. This element is now processed in a similar way
to the div element.Upgraded XMLmind Web Help Compiler (whc for
short) to version 3.3.2 which adds ARIA roles to
some of the HTML elements generated by the classic and the
simple layouts.
Bug fixes: many thanks to Jirka Kosek for reporting the following issues:
step child elements of a
steps was incorrect when stepsections were
found between some of the steps. This bug affected all
output formats but the PDF output format.bookmaps like the following one:<bookmap>
<title>Test</title>
<frontmatter>
<topicref href="topics/notices.dita"/>
<booklists>
<toc/>
</booklists>
</frontmatter>
<!-- Invalid. Should be either a chapter or
a topicref found inside frontmatter. -->
<topicref href="topics/chapterA.dita"/>
<chapter href="topics/chapterB.dita"/>
<chapter href="topics/chapterC.dita"/>
</bookmap>It failed with XSLT error "A sequence of more
than one item is not allowed as the first operand of 'ge'" when
attempting to convert the above bookmap to any of the
XSL-FO based output formats (e.g. PDF).
Enhancements:
ditac-N_N_N-plus-fop.zip now
contains Apache FOP
2.7 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Bug fixes:
topicref[locktitle=yes]/@navtitle and
topicref[locktitle=yes]/topicmeta/navtitle were ignored
when the topicref pointed to a DITA file containing several
topics, whether multiple topics (dita root element) or a single topic
containing nested topics.Possible incompatibilities:
Enhancements:
Regressions:
onclick processing-instruction is no longer
supported. Rationale: this processing-instruction was mainly used to
generate the EPUB epub:trigger element, a feature not
supported by any major EPUB viewer and deprecated as of EPUB 3.2.Enhancements:
ditac-N_N_N-plus-fop.zip now
contains Apache FOP
2.6 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Enhancements:
Enhancements:
chain-pages is different from
'none' have been improved. The "First Page" and
"Last Page" icons have been removed. New "Table of
Contents" and "Index" icons have been added.ditac-N_N_N-plus-fop.zip now
contains Apache FOP
2.5 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Bug fixes:
audio and video elements. Note that this kind
of conversion is still not possible if you pass the
-validate parameter to ditac. (The
“plain DITA” schema does not support the new
audio and video elements yet.)Possible incompatibilities:
mathjax-url XSLT
stylesheet parameter from (obsolete) https://cdn.mathjax.org/mathjax/latest/MathJax.js
to https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.7/MathJax.js.Enhancements:
orient=land
(landscape table) is now supported when generating any
XSL-FO based output format (PDF, RTF, WML, DOCX, ODT). However, except
when the XSL-FO processor being invoked by ditac is XMLmind
XSL-FO Converter v6.2+ , the landscape
table must have few enough rows to fit onto one page. When this is not
the case, the last rows of the landscape table will simply not appear in
the output.ditac-N_N_N-plus-fop.zip now
contains Apache FOP
2.4 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Fixed a
bug which occurred when parsing a certain combination of ditac
command-line arguments.
Enhancements:
wh-responsive-ui.-p wh---navigation-background-color "#F6F8FA") may be
used to override most fonts and colors used in the generated Web
Help.wh-ui-language may be used to specify the language
used by the messages of the generated Web Help (tab labels,
button tool tips, etc). The default is to use the language
of the Web browser.custom-css.Incompatibilities:
wh-jquery-css,
wh-jquery-custom-theme, wh-jquery-theme,
wh-jquery-ui.css-name is not supported anymore. The stock CSS stylesheet
is now stored in a file called "base.css" and this,
whatever the XHTML-based output format.Upgraded XMLmind Web Help Compiler
(whc for short) to version 2.3.2 because the the Web Help
having the classic layout generated using whc
v2.3.1 did not work in Google Chrome version 77+.
Enhancements:
Bug fixes:
href, conref, conrefend
attributes making an invalid use of the "#." abbreviated
fragment-identifier syntax introduced in DITA 1.3. For example, it
silently replaced href="intro.dita#./disclaimer" by
href="intro.dita#the_introduction/disclaimer", because
"the_introduction" is the ID of the first topic found in
file "intro.dita".In a nutshell, direct URI references
like "foo.dita#./bar" now cause fatal errors. Only
“local” direct URI references like "#./bar" are
now accepted.
<ol outputclass="continue"> element preceded
by an ol sibling itself having ol descendants,
continued its numbering from last ol descendant and not
from the preceding ol sibling.Incompatibilities:
Enhancements:
inheritnum in the
outputclass attribute of an ordered list now causes the
list item numbering to inherit from outer-level ordered lists. For
example, using this feature (e.g. <ol outputclass="upper-alpha
inheritnum">), the items of a list nested at level 2 are
labelled "1.A.", "1.B.", "1.C.", etc.Incompatibilities:
Enhancements:
Example: if the subject scheme map specifies
that the values of attribute audience are limited to
"beginner", "intermediate" and
"advanced", then an error will be reported for an
element having attribute audience="expert".
Example: if the DITAVAL filter specifies that all
elements having attribute platform="linux" are to be
excluded and if the subject scheme map specifies that value
"redhat" of attribute platform is a kind
of "linux", then all elements having attribute
platform="redhat" will excluded too.
More information in "Appendix C. Limitations and implementation specificities, Subject scheme maps".
window-1252 on a Western PC). In
previous version of ditac, this default encoding was UTF-8
whatever the platform. If you want to explicitly specify the encoding of
an MDITA file, please save your file with a UTF-8 or
UTF-16 BOM or add an
encoding directive inside a comment anywhere at the beginning
of your file. Example:<!-- -*- coding: iso-8859-1 -*- --> Heading ======= ## Sub-heading Paragraphs are separated by a blank line.
The above example should work fine because ditac now
understands the GNU Emacs file variable called
"coding".
Incompatibilities:
Enhancements:
Bug fixes:
reltables and when a DITAVAL file was used to flag
some list items contained in the topics.pagebreak processing-instruction
and the header-separator XSLT stylesheet parameter.Enhancements:
keydef is used to create an hyperlink and
contains a topicmeta/shortdesc, this
shortdesc is now used to specify the tooltip of
the hyperlink. Example:<ph keyref="XDR"/>
where key "XDR" is defined as follows:
<keydef keys="XDR"
href="http://www.xmlmind.com/docrep/"
format="html" scope="external">
<topicmeta>
<linktext>XMLmind Document Repository</linktext>
<shortdesc>XMLmind Document Repository is a <i>web-based</i> document
store featuring <i>automatic</i>, <i>transparent</i>,
<i>versioning</i>.</shortdesc>
</topicmeta>
</keydef>is translated in XHTML to:
<a href="http://www.xmlmind.com/docrep/"
title="XMLmind Document Repository is a web-based document store featuring
automatic, transparent, versioning.">XMLmind Document Repository</a>note elements are converted to
RTF, WML, DOCX and ODT. When a DITA note element has
attribute type=other, this enhancement makes use of XMLmind XSL-FO Converter v6 new extension
attribute xfc:render-as-table. If you want to restore the
previous behavior, pass new XSLT stylesheet parameter -p xfc-render-as-table ""
(its default value being "note") to
ditac.
Incompatibilities:
ditac using the -xfc
option, option -rtf.target=MSWord is automatically
passed to fo2rtf. This option is needed to circumvent an
obscure bug in the RTF loader of MS-Word, which does not handle table
cell padding tags correctly.Enhancements:
audio and video elements), HDITA (topics and maps written in HTML5) or
MDITA Extended Profile (topics and maps
written in Markdown).XMLmind DITA Converter can of course process DITA documents comprising a mix of XDITA, HDITA, MDITA and (full) DITA topics and maps.
However for this to work, you must be using a Java 1.8+ runtime. More information in "Lightweight DITA support".
line-numbers to the
outputclass attribute of any element specializing
pre numbers the lines of this element.Adding class
tab-width-N to the outputclass
attribute of any element specializing pre
“expands” the tab characters found in this element and also
performs other whitespace normalizations.
Note that when the
outputclass attribute of any element specializing
pre contains class line-numbers and/or class
language-L (which triggers syntax highlighting),
then class tab-width-8 is implicitly specified too, that
is, whitespace normalization is automatically performed. If this is not
what you want, please explicitly add class tab-width-0 to
outputclass.
More information in "Fancy code blocks".
ditac-N_N_N-plus-fop.zip now
contains Apache FOP
2.3 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Bug fixes:
draft-comment and
required-cleanup were not filtered out prior to generating
text for TOC entries, figure list entries, index entries,
etc.Incompatibilities:
text-file-encoding is no
longer supported. By default, the character encoding of the text file
included using a coderef element is automatically
determined by ditac (e.g. by examining the BOM or
<?xml encoding="XXX"?>). You may specify this
character encoding explicitly by adding a
format="text; charset=XXX" attribute to the
coderef element. Example:
<coderef format="text; charset=US-ASCII" href="../src/sieve.cpp"/>.Regressions:
use-multimedia-extensions is
no longer supported. When set to 'yes' and when RenderX
XEP was used to generate PDF, a proprietary extension called
rx:media-object was used to embed audio and video objects in
the output file.Enhancements:
Bug fixes:
<revised modified="2018-04-14"/> was formatted as
"2018 April 14" instead of expected "April 14,
2018".Important bug fix; please upgrade. Upgrading XMLmind Web Help Compiler (whc for short) to version 2.1.1 introduced a bug in the layout of the generated Web Help. This bug was visible on most Web browsers but not on Firefox.
This bug is fixed in whc v2.1.2 which is included in ditac v3.2.4.
window.sessionStorage rather than cookies to store the
internal state of the Web Helps it generates.Please do not use newest Java 9 to run
ditac. XMLmind DITA Converter has not yet been tested against this version of Java.
Enhancements:
<?pagebreak?>
processing-instruction may be used to force a page break. This
processing-instruction must be placed between elements that generate
blocks of text (e.g. after a paragraph, section or table, not
inside a table).nn (Norwegian Nynorsk)
and nb (Norwegian Bokmål), thanks to a contribution made by
Leif Halvard Silli.Bug fixes:
width and
height attributes of img to be specified. As a
consequence of this specificity, DITA images like
<image href="X" width="W"/>,
<image href="X" height="H"/> or
<image href="X" scale="S"/> were not
converted to an img really usable by JavaHelp.Enhancements:
add-index-toc=no.font-size: 1em;" to all rules
targeting table classes. This is a workaround for a well-known
quirks mode behavior.ditac option -p wh-layout simple to give it a
try.Enhancements:
language-bourne).Bug fixes:
fn inserted into a pre was very
poorly formatted.chain-pages was set did not get their
“tooltip texts” localized. That is, their tooltip texts
always contained English messages.Enhancements:
ditac-N_N_N-plus-fop.zip
contains Apache FOP
2.2 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.nn (Norwegian Nynorsk)
and nb (Norwegian Bokmål), thanks to a
contribution made by Leif Halvard Silli.ja (Japanese), thanks to
a contribution made by Kazuko Ohashi of NEC Corporation.Bug fixes:
epubcheck complained about the system
ID found in the DOCTYPE of the generated
toc.ncx.colspec/@colnum.Other changes:
Enhancements:
%{N} in the localized text. This variable
is replaced by the number of the element.Japanese example: excerpts
of a possible
ditac_install_dir/xsl/common/messages/ja.xml:
<message name="chapter">第%{N}章</message>For the first chapter of the document, this gives "第1章", which means "The 1 Chapter".
For example, this Web Help has been
generating by passing ditac
-p wh-jquery-custom-theme jquery-ui-1.12.1.custom.zip,
where jquery-ui-1.12.1.custom.zip was entirely created
using JQueryUI ThemeRoller.
Enhancements:
Enhancements:
title attribute to
the XHTML area elements generated out of a DITA
imagemap element. This title attribute is used
by Web browser to display a tooltip.scale attribute in
something like <image href="drawing.svg scale="75"/>
caused ditac to fail scaling the SVG graphics. The following error
message was printed on the console: "'svg', unsupported image
extension". This is no longer the case provided that the
svg root element of the referenced SVG file has both
width and height attributes containing an
absolute length, for example:
<svg width="640px" height="320px">.Bug fixes:
Enhancements:
imagemap is now converted
to a div containing img and map
child elements.imagemap is now converted
to an image followed by a numbered list, with one list item per area
element. A list item contains the link specified by the
area element. No list items are generated for “dead
areas” (area element specifying no link at
all). This numbered list may be suppressed by setting XSLT
stylesheet parameter show-imagemap-links to
'no'.format-to-type which
allows to map DITA xref/@format to XHTML
a/@type.Parameter format-to-type contains
zero or more DITA format/MIME type pairs. Example: "txt text/plain
xml application/xml html text/html". The default value of this
parameter is the empty string, which means that DITA
xref/@format is not converted to XHTML
a/@type.
Using this default value, <xref
scope="external" format="txt" href="http://acme.com/info.xyz">
is converted to <a href="http://acme.com/info.xyz"
target="_blank">. The fact that file extension
".xyz" is unknown may cause problems when attempting to
navigate or download file "info.xyz" using a Web
browser.
If -p format-to-type "txt text/plain" is
passed to ditac then <xref scope="external" format="txt"
href="http://acme.com/info.xyz"> is converted to <a
type="text/plain" href="http://acme.com/info.xyz"
target="_blank">, which is better.
Bug fixes:
Enhancements:
This major jQuery upgrade required making a number of changes in the JavaScript™ code of XMLmind Web Help Compiler, so this may have added minor bugs. If, in the generated Web Help, you find anything which does not work as expected, please be kind enough to file a bug report (mailto:ditac-support@xmlmind.com).
Bug fixes:
type attribute was not correctly processed for
object elements having a datakeyref attributes
and for param elements having a keyref
attribute.Incompatibilities:
object element. Alternate audio and
video files used to be specified as follows:<object data="media/audio.mp3" type="audio/mpeg"> <param name="source.src" value="media/audio.m4a"/> <param name="source.type" value="audio/mp4"/> <param name="source.src" value="media/audio.wav"/> <param name="source.type" value="audio/wav"/> <param name="controls" value="true"/> </object>
Alternate audio and video files must now be specified as follows:
<object data="media/audio.mp3" type="audio/mpeg">
<param name="source" value="media/audio.m4a"
valuetype="ref" type="audio/mp4"/>
<param name="source" value="media/audio.wav"
valuetype="ref" type="audio/wav"/>
<param name="controls" value="true"/>
</object>More information in Rich media content, Audio and Video.
Other:
XMLmind DITA Convert now fully supports DITA 1.3 Technical Content. However, there are still limitations, deemed minor, and implementation specificities which are documented in the manual.
Bug fixes:
reltable elements, metadata attributes (e.g.
scope) did not cascade correctly from the
relcolspec elements of the reltable to the
topicref elements contained in the relcell
elements of the reltable.Enhancements:
fo_indent.xsl may
be used to generate any XSL-FO based output format: PDF, DOCX, ODT, etc.
This stylesheet:body-start-indent. By default
body-start-indent is 2pc.This stylesheet is invoked by passing option
-t ditac-xsl:fo/fo_indent.xsl to ditac.
Example of its output: manual-fop.pdf.
epub2-compatible to
no.epub:switch elements..ditaval file. Elements like li,
dlentry, step, stentry, etc, can
now be flagged to
a certain extent.ditac no longer supports Internet
Explorer 8 and older versions.Enhancements:
Bug fixes:
properties tables having just 2 columns
(that is, not containing proptype and
propvalue and propdesc) and not
having a prophead header row was poorly implemented.
Moreover converting such properties tables to PDF caused
Apache FOP to fail.topicmeta of a
topicref to the prolog of a topic
(reference: "Reconciling
topic and map metadata") It was copied only in the case of
topicrefs having an href attribute.
Example:<map>
<topicref href="t1.dita">
<topicmeta><data name="key1" value="value1"/><topicmeta>
</topicref>
<topichead navtitle="My Title">
<topicref href="t2.dita">
<topicmeta><data name="key2" value="value2"/><topicmeta>
</topicref>
</topichead>
</map>File t1.ditac (that is, preprocessed
t1.dita) ended up with a prolog containing <data
name="key1" value="value1"/>, which was correct.
File
t2.ditac (that is, preprocessed t2.dita),
being referenced in the map using a topicref contained in a
topichead not having an href attribute, did
not end up with a prolog containing <data
name="key2" value="value2"/>, which was incorrect.
Partial DITA 1.3 support:
line-through, steptroubleshooting,
troubleshooting topic, XML domain, MathML domain, SVG
domain, equation domain, etc), but not any of the DITA 1.3 new features
(abbreviated syntax "#./elementId", key scopes,
branch filtering, etc). Full DITA 1.3 support is planned for year
2016.<!DOCTYPE> means "use latest
version of the DITA DTD":<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd"> <topic id="MyTopic"> ... </topic>
This should not be a problem as DITA 1.3 is a superset of DITA 1.2.
<?xml version="1.0" encoding="UTF-8"?> <?xml-model href="urn:oasis:names:tc:dita:rng:topic.rng"?> <topic id="MyTopic"> ... </topic>
java -cp ditac_install_dir/lib/ditac.jar com.xmlmind.ditac.tool.DTDToSchema -rng MyTopic.dita
Other enhancements:
mathjax XSLT parameter to
"auto" allows to add a script element loading
MathJax to the html/head elements of the XHTML
files containing MathML generated by ditac.This is needed because very few web browsers (Firefox) can natively render MathML. Fortunately, there is MathJax. MathJax is a JavaScript display engine for mathematics that works in all browsers.
Enhancements:
ditac-N_N_N-plus-fop.zip
contains Apache FOP
2.1 (including hyphenation and MathML support). This XSL-FO
processor is automatically declared and thus, ready to be used to
generate PDF or PostScript.Bug fixes:
<chapter href="sub.bookmap"/> included the
topicrefs and reltables contained in
sub.bookmap, which is fine, but also the
frontmatter and backmatter of
sub.bookmap, which is incorrect.Enhancements:
-Djava.awt.headless=true to the command-line
executables found in ditac_install_dir/bin/.Bug fixes:
The flow-name "XXX" on fo:static-content could not be mapped to a region-name in the layout-master-set.
bookmap/booktitle were not
correctly processed.META-INF/MANIFEST.MF file was missing.eclipsehelp.css CSS file
to adapt it to the Eclipse Help Viewer when displayed on very
high-resolution (HiDPI) screens.Bug fixes:
abbreviated-form is now processed as described
in the DITA 1.2 spec, that is, it is substituted with the
glossSurfaceForm (first occurrence of an
abbreviated-form) or the glossAcronym
(subsequent occurrences of an abbreviated-form) of the
glossentry pointed to. In previous versions,
abbreviated-form was systematically substituted with the
glossterm of the glossentry pointed to.glossref.Enhancements:
watermark-image (all output
formats) and watermark (XSL-FO based output formats
only).If you need this feature when generating RTF, WordprocessingML, Office Open XML (.docx), OpenDocument (.odt), please make sure to use XMLmind XSL-FO Converter v5.3+.
border-width to the tgroup and
entry attribute-sets. This allows to easily
give tables a border width which is thicker than 0.5pt (which is the
“stock” value).Bug fixes:
Enhancements:
Other:
Enhancements:
-validate option allows to validate all the XML
files loaded by ditac. Any validation error will cause ditac to
immediately stop running. Therefore the combination of the
-validate and -dryrun (checks
cross-references) options gives you a simple way to thoroughly
check your DITA document.Note that for the -validate
option to work, all the XML files (maps, topics, even
.ditaval filter files) loaded by ditac must start with the
proper <!DOCTYPE> declaration.
image element has an
empty or invalid href attribute or if this
href attribute points to a non-existent file.Enhancements:
bgcolor(color) directive (where
color is any CSS color value) to the
outputclass attribute of most table elements. More
information in this chapter of the manual.Bug fixes:
frame, colsep and rowsep
attributes of table elements to be effective.Enhancements:
wh-index-numbers which allows
to index words looking like numbers. Note that, by default,
number-like words are not indexed.wh-user-resources now accepts the
absolute "file:" URI of a directory, as well as an absolute
or relative filename.Bug fixes:
<task id="myTask">
<title>Parent Task</title>
<taskbody>
...
</taskbody>
<task id="conrefTask" conref="conrefTask.dita">
<title/>
</task>
</task>the nested topic was empty (instead of having the same
contents as conrefTask.dita) in the files generated by
ditac.
Date:format was not
thread-safe.Enhancements:
Bug fixes:
<prop action="exclude"/> in a
.ditaval file caused ditac to raise a
NullPointerException.Incompatibilities:
Enhancements:
Upgraded XMLmind Web Help Compiler (whc for short) to version 1.3.0_02. This version leverages jQuery v1.11.0 and jQuery UI v1.10.4.
Bug fixes:
id attribute of the resourceid element was
modified by ditac.two-sided was set to no,
page-inner-margin and page-outer-margin were
swapped for even and odd pages.simpletables, but not for tables.Starting from Java™ 1.6.0_23, converting XML documents to PDF using RenderX XEP randomly fails with false XSL-FO errors (e.g. attribute "space-before" may not be empty). This problem seems specific to the 64-bit runtime.
Enhancements:
Example: let's suppose the Web Help contains word "Servlets", but not word "Servlet". In previous versions of the Web Help, which did not implement stemming, searching for "Servlet" failed to find the page containing "Servlets". With stemming now implemented and turned on by default, searching for "Servlet" finds the page containing "Servlets".
Enhancements:
outputclass attribute of the ol element. For
example: <ol outputclass="upper-roman start(10)">
specifies an ordered list which starts with an "X.". More
information in this chapter of the
manual.wh-local-jquery which allows to copy all jQuery
files to the directory containing the other Web Help files. By default,
the jQuery files are accessed from the Web (typically from a
CDN).Enhancements:
This feature requires generating PDF version 1.5+. By default, XEP generates PDF version 1.4. It seems that there is no way to change this by passing a command-line option to xep.bat or to the xep shell script. However, this can be changed once for all, for example by inserting
<option name="PDF_VERSION" value="1.5"/>into the<generator-options format="PDF">element found in theXEP_install_dir/xep.xmlconfiguration file.
bookmap now adds elements after any existing
booklists elements. Using the -backmatter
command-line option when converting a bookmap now adds
elements before any existing booklists
elements.Bug fixes:
Bug fixes:
Enhancements:
Note that (X)HTML 5 really requires using a very recent Web browser. For example, Internet Explorer 8 does not support (X)HTML 5.
The EPUB 3 generated by XMLmind DITA Converter has been successfully tested against epubcheck 3.0 and iBooks 3.0.2. Note that iBooks still has font problems with MathML and also, video control by the means of epub:trigger does not always work as expected.
external-resource-base
may be used to specify how to resolve xref or
link elements having an external
scope attribute and a relative href
attribute. Example of such xref elements: <xref
scope="external" format="java"
href="src/Test.java">Test.java</xref>.Incompatibilities:
com.xmlmind.ditac.preprocess.ImageHandler has been replaced
by com.xmlmind.ditac.preprocess.ResourceHandler.Bug fixes:
xml:lang to element fo:root.
Previously, this stylesheet added a language attribute to
element fo:page-sequence but this language
attribute possibly contained a combination of a language code and a
country code (e.g. "en-US"), which is incorrect.Fixed a minor bug in the open source software component called "XSLT syntax highlighting" (found in ditac_install_dir/lib/xslthl.jar). Without this bug fix, XMLHighlighter.highlight raised a StringIndexOutOfBoundsException when the XML text to be highlighted contained nested elements like for example in:
<pre><db:xref <i>linkend='foo'</i>/></pre>
In the above example, the text to be highlighted is basically "<db:xref linkend='foo'/>". However, this text also contains a <i> nested element, which triggered the bug.
Bug fixes:
<glossarylist> <topicref href="term1.dita"/> <topicref href="term2.dita"/> <topicref href="term3.dita"/> </glossarylist>
was processed as if it was:
<topicgroup> <topicref href="term1.dita"/> <topicref href="term2.dita"/> <topicref href="term3.dita"/> </topicgroup>
In some cases, when generating a XSL-FO based format (PDF, RTF, etc), this caused "A sequence of more than one item is not allowed as the first operand of 'eq'" errors.
Now, the above glossarylist is processed as if it was:
<glossarylist navtitle="Glossary"> <topicref href="term1.dita"/> <topicref href="term2.dita"/> <topicref href="term3.dita"/> </glossarylist>
Note that all the following bookmap elements: abbrevlist, amendments, appendices, appendix, bibliolist, bookabstract, booklist, chapter, colophon, dedication, draftintro, figurelist, glossarylist, indexlist, notices, part, preface, tablelist, toc, trademarklist, are considered to have an implicit title when
<topicref href="multi.dita"/> <!-- Now, pull a copy of multi.dita. --> <topicref href="multi.dita"/>
where multi.dita contains multiple topics, each topic possibly containing nested topics. As expected, the first topicref pulled all the topics, including nested ones, contained in multi.dita. The second topicref only pulled the first topic contained in multi.dita.
However, please note that there are still limitations and inconsistencies when working with files containing multiple topics and/or nested topics. We have documented some of these limitations here.
Enhancements:
.hl-keyword {
font-weight: bold;
color: #602060;
}<xsl:attribute-set name="hl-keyword" use-attribute-sets="hl-style"> <xsl:attribute name="font-weight">bold</xsl:attribute> <xsl:attribute name="color">#602060</xsl:attribute> </xsl:attribute-set>
Bug fixes:
Incompatibilities:
Now supports simple plug-ins.
A plug-in is simply a subdirectory of ditac_install_dir/plugin/. For example, ditac_install_dir/plugin/MyPlugin/.
This subdirectory may contain an XML catalog file. This XML catalog file must be named catalog.xml. In the case of a DITA specialization, catalog.xml points to local copies of customized DTDs. Example: ditac_install_dir/plugin/MyPlugin/catalog.xml:
<catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"
prefer="public">
<public publicId="-//OASIS//DTD DITA Concept//EN"
uri="dtd/concept.dtd"/>
...
</catalog>This subdirectory may contain an xsl/ subdirectory organized exactly like ditac_install_dir/xsl/. That is, this xsl/ subdirectory may contain one or more of the following XSLT stylesheets:
| XSLT stylesheet | Description |
|---|---|
| xsl/fo/fo.xsl | Used to generate an intermediate XSL-FO file. After that, the XSL-FO file is converted to PDF, PostScript, RTF, WordprocessingML, Office Open XML (.docx) or OpenOffice (.odt) by the means of an XSL-FO processor. |
| xsl/xhtml/xhtml.xsl | Used to generate XHTML 1.0 pages. |
| xsl/xhtml/xhtml1_1.xsl | Used to generate XHTML 1.1 pages. |
| xsl/xhtml/html.xsl | Used to generate HTML 4.1 pages. |
| xsl/webhelp/webhelp.xsl | Used to generate Web Help files, which are then compiled using XMLmind Web Help Compiler. |
| xsl/htmlhelp/htmlhelp.xsl | Used to generate HTML Help files, which are then compiled using hhc.exe. |
| xsl/eclipsehelp/eclipsehelp.xsl | Used to generate Eclipse Help files. |
| xsl/javahelp/javahelp.xsl | Used to generate Java Help files, which are then archived in a .jar file. |
| xsl/epub/epub.xsl | Used to generate EPUB files, which are then archived in a .epub file (Zip archive having a .epub extension). |
When ditac is passed command-line option -plugin plugin_name, it will use the DTDs/schemas and the XSLT stylesheets found in the plug-in subdirectory having specified name preferably to those found in ditac_install_dir/schema/ and in ditac_install_dir/xsl/.
Incompatibilities:
com.xmlmind.ditac.convert.Converter methods:
registerCustomStyleSheet,
setStyleSheetDirectory (instead, now set system property
DITAC_XSL_DIR), getStyleSheetDirectory.Enhancements:
Bug fixes:
Enhancements:
For these navigation links to be generated, XSLT stylesheet parameter ignore-navigation-links must be either specified as 'no' or 'auto'. And, if ignore-navigation-links is specified as 'auto', then XSLT stylesheet parameter chain-topics must not be specified as 'yes' (in other words, 'auto' means: same value as chain-topics).
The default value of ignore-navigation-links is: 'auto' for XHTML and its variants; 'yes' for Web Help, Java Help, HTML Help, Eclipse Help and EPUB.
Bug fixes:
<concept id="intro">
<title id="title">Introduction</title>
<prolog>
<data audience="newbie"><title conaction="pushreplace"
conref="#intro/title">Introduction for newbies</title></data>
<data audience="expert"><title conaction="pushreplace"
conref="#intro/title">Introduction for experts</title></data>
</prolog>
...
</concept>Enhancements:
New XSLT stylesheet parameters:
New attribute-sets:
Bug fixes:
Incompatibilities:
<meta name="generator"
content="XMLmind DITA Converter VERSION" />The name of the software which has been used to create the HTML pages is specified by new XSLT stylesheet parameter generator-info.
If you have XMLmind XSL-FO Converter v4.6+, XMLmind DITA Converter will now automatically generate outline levels for the RTF, WordprocessingML, Office Open XML (.docx), OpenOffice (.odt) output formats. In practice, this allows to use the Document Map and the Outline View in MS-Word and to use the Navigator Window in OpenOffice/LibreOffice.
XMLmind DITA Converter (ditac for short) now allows to generate Web Help.
This feature leverages a new, free, open source, component: XMLmind Web Help Compiler.
XMLmind Web Help Compiler (whc for short) is a generic —that is, not depending on ditac in any way— tool which can be used to convert a set of static XHTML pages to a standalone, interactive, Web Help application running in a Web browser. More information in Features.
whc has been embedded in ditac, so there is no need for a ditac user to download and install whc. We mention this tool merely because its documentation describes quite precisely the kind of Web Help application which can now be generated by ditac.
We plan to integrate ditac v2.1 in the following products: XMLmind XSL Utility, XMLmind XSL Server, XMLmind XML Editor Professional Edition, very shortly. Note whc will also be used by XMLmind XML Editor to generate Web Help out of DocBook documents.
Bug fixes:
<keydef print="no" keys="screenshot" href="screenshot.png" /> <keydef print="printlonly" keys="screenshot" href="screenshot.svg" />
Before the bug fix, key screenshot points to screenshot.png. After the bug fix, key screenshot points to screenshot.svg.
Other changes:
Bug fixes:
Enhancements:
Note that ditac is not a DITA validator. It checks the value of the id attribute only in a few cases and it requires such value to be a mere NMTOKEN.
Enhancements:
This feature has been tested with: Adobe Digital Editions (ADE), Calibre, iBooks on the iPad and Bookworm.
Bug fixes:
Incompatible changes:
Enhancements:
Bug fixes:
Enhancements:
XMLmind DITA Converter (ditac) has now extensive support for the DITA 1.2 standard. Ditac 2.0 has less limitations and less specificities than ditac 1.x. It is also more conforming to the DITA 1.2 standard than ditac 1.x was to the DITA 1.1 standard. All in all, even if you do not intend to use any of the DITA 1.2 features in your documents, upgrading to ditac 2.0 is strongly recommended. And if you gave up the idea of using ditac 1.x because of its limitations and specificities, then may be you should give ditac 2.0 a try.
We plan to integrate XMLmind DITA Converter v2.0 in the following products: XMLmind XSL Utility, XMLmind XSL Server, and XMLmind XML Editor Professional Edition within a couple of weeks.
Other enhancements:
Removed limitations and specificities (compared to ditac 1.x):
For example, a map author is no longer required to manually specify chunk="to-content" on almost all topicref elements.
Incompatible changes other than regressions (compared to ditac 1.x):
Regressions (compared to ditac 1.x):