Note that some old versions of
OpenOffice/LibreOffice do not support SVG graphics in ODT documents
(though this is explicitly recommended even in
“ancient” OpenDocument
1.0 specification). If you want to also support these old
versions of OpenOffice/LibreOffice, you must pass parameter
alwaysSaveAsPNG=svg to the XMLmind XSL-FO Converter engine.
More information about conversion parameter alwaysSaveAsPNG
in the Incompatibilities section below.

Note that this new
feature applies only to XMLmind XSL-FO Converter for Java™ and not
to XMLmind XSL-FO Converter for .NET which does not support SVG graphics
at all.

Bug fixes:

Conversion parameter set.SVG.resolution had an effect
on the resolution of the output PNG image but not on its size in pixels.
For example, set.SVG.resolution=96 created a PNG image
having a resolution of 96dpi and a size of 400x200px (which is correct),
but set.SVG.resolution=192 created a PNG image having a
resolution of 192dpi and a size of 400x200px, (which is incorrect; the
expected size being 800x400px).

Incompatibilities:

Conversion parameter alwaysSaveAsPNG now accepts two
new values in addition to true and false:
jpeg and svg.

Value

Definition

false

Do not convert input JPEG and SVG graphics to PNG in the
output file. Default value for the ODT output format.

Version 5.4.2 (September 12,
2016)

XMLmind XSL Server: upgraded the bundled Jetty 7 to version
7.6.20.v20160902. Note that this version of Jetty requires a Java™
runtime 1.7+. It does not work using a Java™ runtime 1.6.

Bug fixes:

XMLmind XSL Utility and XMLmind XSL Server: by default, navigation
headers and footers are suppressed when converting DocBook to Web Help
or EPUB. The bug was that there was no way to restore them. These
navigation headers and footers can now be restored using XSLT stylesheet
parameter suppress.navigation=0.

XMLmind XSL Utility: added a workaround for an Apple Java bug which
possibly caused any scrolled window to become garbled when scrolling
quickly. This bug seems to be specific to Apple Java and to
non-Retina Macs running El Capitan.

A regression caused XMLmind XSL Server to fail on a headless server.
(X)HTML conversions raised the following exception:
java.awt.HeadlessException: No X11 DISPLAY variable was set, but this
program performed an operation which requires it.

The old
implementation which depends on the Microsoft Visual J# runtime and which
works using a .NET 2.0+ framework is still available, but should be
discontinued in the future.

Other enhancements:

XMLmind XSL Utility and XMLmind XSL Server:

XMLmind XSL Utility and controlapp(desktop
application allowing to easily configure and control XMLmind XSL
server) now works fine on computers having very high
resolution (HiDPI) screens. For example, it now works fine on a
Mac having a Retina® screen and a Windows computer having an UHD
(“4K”) screen. On Windows, all DPI scale factors
—100%, 125%, 150%, 200%, etc— are supported.

On a
Linux computer having a HiDPI screen, HiDPI is not automatically
detected. You'll have to to specify the display scaling factor you
prefer using a command-line option. Examples:

Version 5.3 (July 31,
2015)

Enhancements:

It's now possible to add a watermark to the pages generated by
XMLmind XSL-FO Converter. This is done the way which is supported by all
the other XSL-FO processors, that is, by setting the background-image
property of fo:region-body.

WML format only: identical images are no longer duplicated in the
generated file. This was already the case for the ODT and DOCX formats.
This is not yet the case for the RTF format.

the
empty fo:block used to specify a page break was ignored.
That is, the block having named style "Heading 3" was not
preceded by a page break.

Java™ Edition only: failing to read the resolution from an
image file (i.e. because the image metadata is inconsistent or in
a form which is not supported by the Java runtime) caused the
image not to be rendered at all. Now XFC fallbacks to the
default image resolution (96DPI), then XFC proceeds to
render such images.

HTTP header "Content-Type: image/jpg" was not
considered to be equivalent to "Content-Type: image/jpeg".
Such HTTP headers are used by XFC when a
fo:external-graphic element references a remote graphic
file having no file extension and when attribute
content-type is not specified.

Version 5.1 (September 18,
2014)

Enhancements:

DOCX and OTD formats only: duplicate images referenced in the source
XSL-FO are now stored once in the DOCX or ODT output file. Not
only this reduces the size of the output file, but this also reduces
XMLmind XSL-FO Converter (XFC for short) processing time.
This feature is especially useful when converting DITA or DocBook
documents to DOCX or ODT. Such documents generally make use of a large
number of admonition icons (e.g. note.svg,
tip.svg, warning.svg).

Java version only: by default, SVG graphics are now rasterized at
192DPI. In previous versions of XFC, the resolution used
for that was 96DPI. By default, MathML equations are now rasterized at
288DPI. In previous versions of XFC, the resolution used
for that was 144DPI.

These defaults can be changed by using new
properties allowing to parameterize the graphic factories handling SVG
graphics and MathML equations. For example, the following properties may
be used to restore the defaults used by previous versions of
XFC: set.svg.resolution=96,
set.mathml.resolution=144.

When a fo:external-graphic element references a graphic
file having no file extension and when attribute
content-type is not specified, XFC now uses
the Content-Type header returned by the HTTP server to
determine the format of the graphic file. Example of such
fo:external-graphic:

Property genericFontFamilies may be used to map the generic
font families (e.g. sans-serif) to actual font families (e.g.
Calibri). Font family "Arial Unicode MS" gets now a
special treatment:

Font family "Arial Unicode MS"
is often used to render east asian (CJK) text. However, this typeface
has no bold, italic and bold+italic fonts. That's why specifying
"sans-serif=Arial Unicode MS" is equivalent to specifying
"sans-serif=Arial", except that some special instructions are
inserted in the output file to specify that typeface Arial is
to be used to render western text and "Arial Unicode MS" is to
used to render east asian text.

This specificity is supported by
the ODT, WML and DOCX output formats, but not by the RTF output
format.

Java version: added -Djava.awt.headless=true to all the
command-line executables, fo2docx, fo2odt,
etc, found in XFC_install_dir/bin/.

As of v5.1, by default, images are not prescaled. In
previous versions of XFC, by default, images were prescaled
to minimize output document size.

.NET version only: the /p (do not prescale images)
command-line option is ignored as it now specifies the default behavior
of XFC. If, on the contrary, you need to prescale images,
please use new command-line /pi (prescale images).

Version 5.0 (February 17, 2014)

XMLmind
XSL-FO Converter now allows to generate RTF, WordprocessingML, Office Open
XML (.docx) and OpenOffice (.odt) files where most of the
text formatting is achieved using named paragraph styles
("Normal", "Heading 1", "Heading 2", etc) and
named character styles ("Strong", "Emphasis",
etc).

Moreover, a named paragraph style may reference a named
numbering scheme (also known as a “list style”). This allows
to implement numbered headings and advanced —multilevel— lists
purely by using named paragraph styles.

The main benefits of
generating named styles are for the end-user of the word processor
files:

Thanks to the names of the styles, the document, when opened in
MS-Word or OpenOffice/LibreOffice, looks familiar and its organization
is easier to understand.

After a change, the numbering of headings and list items is
automatically updated by the word processor.

The formatting of the document is a snap to modify using the various
style editors included in the word processor.

This
change was needed because on Windows, for permissions reasons, there is
no way to pick a font file from the "C:\Windows\Fonts\" folder
using the standard file chooser (whether the native or the
Java™ one). Therefore the only way to register with Apache
FOP or RenderX XEP a font found in "C:\Windows\Fonts\" is to
drag its file from the Windows file manager and to drop it onto the
list.

This change was
needed because on Windows, for permissions reasons, there is no way to
pick a font file from the "C:\Windows\Fonts\" folder using the
standard file chooser (whether the native or the Java™
one). Therefore the only way to register with Apache FOP or
RenderX XEP a font found in "C:\Windows\Fonts\" is to drag its
file from the Windows file manager and to drop it onto the
list.

Version 4.8.2 (August 2,
2013)

Remember that Window/Orphan
control is turned on by default, as the initial value of the
orphans and widows properties is 2.

Also note that for MS-Word, Window/Orphan control is an all or
nothing option. Therefore if you set attribute orphansor attribute widows to 1, Window and
Orphan control will be turned off. If, on the contrary, you set
attribute orphansor attribute widows
to any value greater or equal than 2, Window and Orphan control
will be turned on.

Upgraded XMLmind DITA
Converter(ditac for short) to
version 2.4.2_01. This version allows to control the numbering of
ordered lists by the means of the outputclass attribute
of the ol element. More information here.
This version also allows to generate self-contained Web Help. More
information here.

keep-together.within-column was ignored while
keep-together.within-page was honored. Now these properties
are treated exactly the same (which is the fine because
XFC targets word processors). Same bug with
keep-with-next and keep-with-previous.

The new output formats all support rich media content. A new
chapter of the XMLmind DITA Converter Manual, Rich media content, explains how to add
SVG, MathML, audio, video, Flash animations and actions (e.g. click some
text to play a sound) to your DITA topics. This chapter also explains how
this rich media content is processed depending on whether it is supported by
the output format.

Attributes fo:language and fo:country (or
equivalently, xml:lang) are now used to add language
information to the files created by XMLmind XSL-FO Converter. This
information was absent from the files created by the previous
releases. This caused the word processor to believe that the
document was entirely written in the default language of the
application. More information in "Adding
language information to the files created by XFC".

XMLmind XSL Utility: removed the Preview tab from the
Conversion editor and instead, added a handy Preview checkbox to
the main window.

XMLmind XSL Utility: the Conversion editor/Transform
tab/Revert button now works as expected, even when the
user-specified custom XSLT file is not found anymore (e.g. the user
deleted it).

Version 4.7 (July 20, 2012)

Personal
Edition does not exist anymore. If you want to evaluate XMLmind XSL-FO
Converter, you now need to download and install Evaluation
Edition.

Note that Evaluation Edition is useless for any purpose
other than evaluating XMLmind XSL-FO Converter. This edition generates
output containing random duplicate letters. (Of course, this does
not happen with Professional Edition!)

Enhancements:

XMLmind XSL Utility:

Conversion editor/Transform tab: new Customize
button allows to automatically create a customization of the XSLT
stylesheet currently selected. New Edit button (next to the
Customize button) invokes a specialized editor called XMLmind
XSL Customizer. This editor allows to add parameters and
attribute sets to the newly created XSLT customization and this,
without prior knowledge of XSL.

Conversion editor/DITA tab: the Edit button now
invokes the helper application associated to the .ditaval
extension (typically an XML editor or a text editor).

XMLmind XSL Utility and XMLmind XSL Server:

The conversions from DocBook 4 and 5 now use the
profiling stylesheets (that is, supporting conditional
processing) rather than the plain stylesheets.

XMLmind XSL-FO Converter engine: fo:external-graphic and
fo:instream-foreign-object: when both content-width
and content-height attributes were specified, XFC behaved as if
scaling="non-uniform" was also specified (which means:
scaling need not preserve the aspect ratio). This is incorrect
in all cases because the default value of attribute scaling is
"uniform" (which means: scaling should preserve the
aspect ratio).

XMLmind XSL Utility and XMLmind XSL Server:

The XHTML stylesheets were passed parameter
foProcessor=XEP when FOP was used to convert an XHTML page
to PDF.

Version 4.6.1 (March 23,
2012)

Enhancements:

XMLmind XSL-FO Converter engine: made XSL-FO parsing less strict:

A length other than 0 having no unit (e.g.
font-size="12") is now assumed to have an implicit
px unit.

Unit ex is now supported. For XFC, 2ex = 1em, which is
an approximation.

These XSLT 2
stylesheets support a large number of parameters. They make an
extensive use of xsl:attribute-sets. Last but not least, by
default, CSS styles specified in XHTML style attributes,
style and link elements also apply to the XSL-FO
file generated by these XSLT 2 stylesheets.

Note that the
XSLT 2 stylesheets for XHTML 1.0, 1.1 and 5.0 developed by XMLmind
are open source software licensed under the terms of the MIT
license. This means that you may freely use these resources outside
XMLmind products. More information in XHTML 5
Resources.

Version 4.6 (December 15,
2011)

Enhancements:

XMLmind XSL-FO Converter engine:

New extension attribute xfc:outline-level may be used
to mark a fo:block as a heading having the outline level
specified by the value of the attribute. The value of this attribute
is an integer between 1 and 9 inclusive. Any other value will cause
attribute xfc:outline-level to be ignored.

Specifying
outline levels allows to:

Use the Document Map and the Outline View in MS-Word. Use
the Navigator Window in OpenOffice/LibreOffice.

Insert a Table of Contents in a document edited in MS-Word
or OpenOffice/LibreOffice.

A JPEG image file referenced by the source XSL-FO is
now kept in JPEG format in the output file. In the previous
releases, such images were systematically transcoded to
PNG, which lead to large .rtf, .wml,
.docx or .odt files in certain cases.

If, for
any reason, you prefer to keep transcoding JPEG image files
to PNG, then specify command-line option
-alwaysSaveAsPNG=true (Java) or /png
(.NET).

Added jai_imageio.jar to ext/lib/. In
consequence, when xfc_ext.jar is in the CLASSPATH
of the host application, this allows XFC to support the following
additional image file formats: TIFF, JPEG 2000 and
PNM.

Added a "Browse Files" button to the dialog box allowing
to add or edit an XSLT stylesheet parameter.

XMLmind XSL Server:

Added the following server parameters: maxRequestSize
(default value: 20Mb), maxFileSize (default value: 10Mb),
fileSizeThreshold (default value: 16384b). These parameters
allows to configure the support of "multipart/form-data"
requests. In the previous releases, the corresponding values were
hardwired in the code and also way too small (2Mb, 1Mb,
16384b).

RTF output only: a table cell containing just an empty block
inherited the wrong font size and thus, often caused the overall
height of its container row to be too large.

Specifying attribute
content-type="content-type:image/jpg" on a
fo:external-graphic element caused XFC to ignore the JPEG
image and to report a "'image/jpg', unsupported graphic
format" warning. Now "image/jpg" is considered to be
an alias for "image/jpeg".

XMLmind XSL-FO Converter for .NET now works with .NET 4+. It
does so by automatically invoking XmlMind.FoConverter.FixDotNET4.DoIt.
Therefore, in principle, there is nothing special to do in the
client code.

In the unlikely case where automatically invoking
FixDotNET4.DoIt poses some problems, please do not hesitate
to ask for an xfc.dll which does not contain this
workaround (based on P/Invoke).

Version 4.5.0_01 (July 22,
2011)

XMLmind XSL Utility and XMLmind XSL Server have been patched in
order to integrate XMLmind DITA Converter (ditac) v2.0.4. This release of
ditac contains a number of bug fixes.

Version 4.5 (June 3, 2011)

Enhancements:

OOXML (.docx): images are now represented by
DrawingML elements. Previously, images were represented by VML
—deprecated— elements. This makes the images nicer to edit
in Word 2007+ and this also fixes a bug on the Mac (see below).

XFC
compatiblity mode

Generating VML is still possible by setting the
docx.useVML property of
com.xmlmind.fo.converter.Driver or Converter to
"true". The corresponding command-line option of
fo2docx.bat is -docx.useVML=true.

When using the
.NET edition of XMLmind XSL-FO Converter, set the UseVML
property of UseXmlMind.FoConverter.Converter to true.
The corresponding command-line option of fo2docx.exe is
/vml.

Added support for the following XSL-FO 1.1 property
values: scale-down-to-fit, scale-up-to-fit. These
are values of properties content-width and
content-height. Such properties apply to
fo:external-graphic and
fo:instream-foreign-object.

XFC automatically tries to infer the numbering style from the label
of the first list item. When the heuristics used by XFC are insufficient
to infer the type of a list, it's now possible to explicitly specify
this type by adding an xfc:label-format proprietary attribute
to the fo:list-block.

Conversion to WordprocessingML and to Office Open XML (.docx):
adding an id attribute to the callout part of a fo:footnote
(e.g. <fo:footnote><fo:inline baseline-shift="super"
id="fn1">(1)</fo:inline>...) caused MS-Word not to
show this footnote.

Conversion to Office Open XML (.docx): added a
<w:nsid val="XXXXXXXX"/> child element to
<w:abstractNum>. Though not required by the standard,
some third-party tools seem to expect this child element to be
present.

Version 4.4.1 (September 23,
2010)

XMLmind XSL-FO Converter is now available integrated in XMLmind XSL
Server, a powerful, production-quality, Servlet which leverages
the XSL technology to allow
converting XML documents to a variety of formats.

This new software
distribution targets the Web developer (JavaScript, Ajax, PHP,
etc) and the system integrator. No prior knowledge of the
JavaTM language or the Servlet technology is required to be able
to deploy, use, program and customize XMLmind XSL Server.

then run xslutil -p /etc/xslutil to
configure the conversions of XMLmind XSL Server.

Bug fixes:

XMLmind XSL Utility: a change made by XMLmind to the DocBook XSL
stylesheets prevented an element such as

<imagedata fileref="/images?id=ef31" format="GIF"/>

from
being converted to PDF, RTF, etc.

Version 4.4 (April 14,
2010)

Enhancements:

Out of the box, XMLmind XSL-FO Converter now supports WMF, EMF, BMP
(only .NET version and JavaTM 1.5+), TIFF
(only .NET version and JavaTM on the Mac)
graphics in addition to GIF, JPEG and PNG graphics.

Implementing the public, documented, Graphic and
GraphicFactory interfaces (IGraphic and
IGraphicFactory for the .NET version) allows third-party
programmers to add support for even more graphic formats.

The XML content of a fo:instream-foreign-object element is
now passed to the proper GraphicFactory. For this to work, the
fo:instream-foreign-object element must have a
content-type attribute containing a media type
supported by a registered GraphicFactory.

Note that
content-type ``sniffing'' is implemented only for SVG and
MathML and that content-type attributes starting with
"namespace-prefix:" are completely ignored.

The two aforementioned GraphicFactories are
available in both source (XFC_install_dir/ext/src/) and
compiled (XFC_install_dir/ext/lib/xfc_ext.jar)
forms.

The script files fo2rtf, fo2rtf.bat,
fo2wml, fo2wml.bat, fo2docx,
fo2docx.bat, fo2odt, fo2odt.bat have all been
modified to detect the case where xfc_ext.jar is
available.

In practice, if a Java 1.5+ runtime is being used and
if xfc_ext.jar and also a number of other .jar files
(batik-all.jar, jeuclid-core.jar, etc) are found in
the CLASSPATH then XMLmind XSL-FO Converter supports SVG and
MathML graphics referenced as external files
(fo:external-graphic) or embedded in the XSL-FO file
(fo:instream-foreign-object).

The "data:"
URI scheme is now supported in the src attribute of the
fo:external-graphic element.

The size or resolution information stored in a graphic file (e.g.
the pHYs chunk in a PNG file) is now taken into account.

The
-imageResolution (/r for the .NET version)
command-line parameter is now used only when such size or resolution
information is not found in the graphic file (e.g. a GIF file).

For completeness, added two new parameters related to image and
screen resolutions: -imageRendererResolution (/rr for
the .NET version) and -screenResolution (/sr for the
.NET version). Changing the default value, 96DPI, of these parameters is
almost never needed.

By
default, the generic font families serif, sans-serif,
monospace are mapped to "Times New Roman",
Arial, "Courier New" for RTF, WML and DOCX and to
"DejaVu Serif", "DejaVu Sans", "DejaVu Sans
Mono" for ODT. Note that by default, fantasy and
cursive are not mapped.

XMLmind XSL-FO Converter now copes with the 40-character limit of
RTF, WML and DOCX bookmarks. Previously very long IDs specified on
XSL-FO elements caused XMLmind XSL-FO Converter to generate MS-Word
files where cross-references were broken.

An empty fo:list-block caused fo2odt to raise a
NullPointerException.

Removed endlocal at the end of fo2rtf.bat,
fo2wml.bat, fo2docx.bat and fo2odt.bat to
allow cmd.exe /c "fo2XXX.bat in.fo out.xxx" to
return the exit code of fo2XXX.bat instead of always
returning 0.

Incompatibilities:

The built-in URI resolver is now much stricter than before. It now
only accepts absolute or relative URIs. Something like
url(C:\temp\log.gif) now longer works.

The -imageResolution (/r for the .NET version)
command-line parameter is now used only when the size or resolution
information is not found in the graphic file. Previously, this parameter
was systematically used to compute the intrinsic size of a graphic.

Converting px lengths to other units (in,
mm, cm, pt, etc) is now based on the value of
the new -screenResolution (/sr for the .NET version)
command-line parameter. Previously, this conversion used the value of
-imageResolution (/r for the .NET version) for
fo:external-graphic elements and 96DPI otherwise.

By default, the generic font families serif,
sans-serif, monospace are now mapped to "Times New
Roman", Arial, "Courier New" for RTF, WML and
DOCX and to "DejaVu Serif", "DejaVu Sans", "DejaVu
Sans Mono" for ODT. Previously these font families were
``hardwired'' to be Times, Helvetica, Courier
for RTF, WML and DOCX and to be "Bitstream Vera Serif",
"Bitstream Vera Sans", "Bitstream Vera Sans Mono" for
ODT.

Version 4.3.2_01 (March 8, 2010)

All
changes are found in XMLmind XSL Utility, that is, nothing has changed in
xfc.jar (JavaTM version) and in xfc.dll (.NET
version).

Enhancements:

Upgraded XMLmind DITA
Converter (ditac) to version 1.2. Ditac v1.2 allows to convert DITA
documents to EPUB (standard e-book
format). It also contain fixes for a few minor bugs.

Though not mandated by the DITA standard, XMLmind XSL Utility 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 DITA 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.

Version 4.3.2 (December 4, 2009)

All
changes are found in XMLmind XSL Utility, that is, nothing has changed in
xfc.jar (JavaTM version) and in xfc.dll (.NET
version).

Using
XMLmind XSL Utility, you can now convert DITA 1.1 topics and maps to
production-quality XHTML 1.0, XHTML 1.1, HTML 4.1, JavaTM
Help, HTML Help, Eclipse Help, PDF, PostScript®, RTF (can be opened in
Word 2000+), WordprocessingML (can be opened in Word 2003+), Office Open
XML (.docx, can be opened in Word 2007+), OpenOffice
(.odt, can be opened in OpenOffice.org 2+).

The Conversion specification combobox has been replaced by a
better organized, less cluttered, popup menu.

Added a "Restore stock conversion specifications" button in
Preferences, General section, which allows to restore all
the stock conversion specifications.

Added a "Helper Applications" section to the dialog box
displayed by clicking Preferences.

This allows to specify the
locations of respectively, jhindex and hhc.exe, two
external tools, which are needed to convert DITA documents to
respectively, JavaTM Help and HTML Help.

The conversion specifications modified or created by the user are
now saved using a safer, more perennial, scheme, which has been designed
to better cope with XMLmind XSL Utility upgrades.

On Windows, XMLmind XSL Utility now detects the case where the file
generated by clicking the Convert button (e.g.
MyBook.pdf) is already opened in another application (e.g.
Adobe® Reader®).

This case caused the conversion process to fail
during its last step. This case is now detected at the very beginning of
the conversion process. The user is then informed that she/he might need
to close the file in the other application before proceeding with the
conversion.

Unlike XMLmind XSL-FO Converter and Apache FOP, RenderX XEP is just
pre-installed in XMLmind XSL Utility. The first time you'll try to use
this commercial XSL-FO processor, you'll be prompted to finish its
installation inside XMLmind XSL Utility.

On Windows, XMLmind XSL
Utility now detects the case where you may not finish this installation
due to insufficient privileges. This typically happens on Vista when you
install XMLmind XSL Utility in C:\Program Files\. In such case,
a dialog box is displayed informing you how to run
xep_finish_install.bat as an administrator.

All the modifications you have made to the stock conversion
specifications of XMLmind XSL Utility v4.3.1 will be lost. Of course,
all the original conversion specifications you have personally created
will be preserved.

All the stock conversion specifications which did not produce
self-contained deliverables are no longer available.

For example, the
conversion specification called dbToHTML is no longer
available. This conversion specification required the user to copy by
hand all the image files referenced by the HTML pages.

The stock conversion specifications operating on Slides documents
are no longer available.

Both distributions are only
available as .zip archives, which should work fine on any
JavaTM 1.5+ platform. This means that installing the product
simply means unzipping the distribution somewhere, and that uninstalling
the product simply means deleting the directory created by unzipping the
distribution.

The user preferences of the XMLmind XSL-FO Converter command-line
tools are now stored in
user_preferences_dir/xfc.properties.

The user
preferences of XMLmind XSL Utility are now stored in various files found
in user_preferences_dir/.

Version 4.2p1 (02/22/2008)

Unsupported XSL-FO extensions were not handled properly, possibly
resulting in a NullPointerException. (This
bug was introduced in version 4.2.)

Bug fixes (RTF)

Right border on table cells spanning multiple columns was not
handled properly, possibly resulting in a missing border.

Implicit empty cells in a nested table would result in invalid
RTF output.

Bug fixes (WML)

Right border on table cells spanning multiple columns was not
handled properly, possibly resulting in a missing border.

Characters '-' and '.' in id
property values would possibly result in invalid hyperlink targets.
(These characters cannot be used in bookmark names as MS-Word replaces
them with character '_' while leaving hyperlink targets
unchanged.)

Footnote body was lost if the id
property was set on the inline child of the
footnote object.

Bug fixes (OOXML)

Characters '-' and '.' in id
property values would possibly result in invalid hyperlink targets.
(These characters cannot be used in bookmark names as MS-Word replaces
them with character '_' while leaving hyperlink targets
unchanged.)

Version 3.0p1 (10/18/2006)

Images did not show up in MS-Word 2007. (Not a bug actually, but
rather a flaw in the RTF loader of Office 2007.)

Bug fixes (RTF/WML)

All bookmarks supposed to be set on a list item were lost along
the way, which would possibly result in broken links in the output
document.

Version 3.0 (09/29/2006)

New
features

Support of OpenDocument as alternate output format.

Version 2.3p1 (03/28/2006)

Bug
fixes

A table in a list item inside a table cell would not be handled
properly, resulting in incorrect RTF/WML output.

Some particular page sequence definitions would result in missing
header/footer on even pages. (This happened for instance when converting
a DocBook document with recent versions of DocBook-XSL, unless the double.sided parameter was set to '1'.)

XSL Utility

Fixed a bug in xslutil: conversion
to RTF/WML would possibly fail when the input file was specified as a
relative path name.

The body of a footnote was ignored if the footnote element was a child of another
inline-level element.

Bad shorthand property values (e.g. border="1") would possibly
result in a ClassCastException.

Version 2.2
(05/25/2005)

Enhancements

Use of expressions for property values specification is now
supported.

The header and footer offsets (RTF \headery and \footery control words) are now set according to
the page master margin-top and margin-bottom property values.

Bug fixes (RTF)

Failure to access the URL (src
property value) of an external-graphic
object would possibly result in a NullPointerException. (This bug affects version
2.1 only.)

Setting the space-before property on
a nested table would result in invalid RTF output.

XSL Utility

Upgrade of DocBook-XSL to version 1.68.1.

Version 2.1
(03/18/2005)

Enhancements

Support of nested tables.

Automatic switch to the fixed table layout when all column widths
are specified.

Bug fixes (RTF)

The charset encoder used to determine if a given character can be
represented in the output encoding was a class variable, which could
possibly cause an IllegalStateException in
a multi-threaded environment.

Bug fixes (WML)

XML special characters (e.g. '&') were not escaped in the
w:dest attribute values.

Version 2.0 (10/20/2004)

New
features

Support of WML as alternate output format.

Bug fixes

When a block contained character data followed by a table, the
character data before the table would end up inside the first cell of
the table.

Values of some compound properties (e.g. border-separation) were not properly
evaluated.

Version 1.3 (05/28/2004)

New
features

Support of multiple page layouts (e.g. different headers and/or
footers on left and right pages).

Enhancements

Support of justified text in the body of list items.

Bug fixes

XFC would occasionally hang while processing an external-graphic object in some particular
environments (e.g. on Windows platforms with JRE 1.3).

The margin-left and margin-right properties were not considered in
the computation of text indents.

XSL Utility

Upgrade of DocBook-XSL to version 1.65.1.

The Jimi image library is now included in the
distribution.

Version 1.2
(12/03/2003)

Enhancements

Support of the proportional-column-width function.

Support of the text-align property
on the table-and-caption element.

Support of the keep-with-next
property on table rows (MS-Word compatible implementation).

Handling of vertical space before a table. (Implemented by means
of an empty paragraph.)

Use of the RTF Unicode control word (\u) for characters that cannot be represented in
the output encoding. (Requires JRE 1.4+.)

Bug fixes

A bookmark (id property) attached to
the last block of a document was lost if the block contained no
character data.

Particular values of the border,
border-top, border-bottom, border-left and border-right property (e.g. border-top="solid") would cause a NullPointerException. (Was supposed to be fixed
since version 1.0p1.)

A list-item-body element with a
list-block as its first child was not
handled properly, resulting in weird paragraph layout.

XSL Utility

Upgrade of DocBook-XSL to version 1.62.0.

Drag & Drop support enhancement.

Command-line utility for batch processing.

Version 1.1 (03/19/2003)

New
features

Support of page references (page-number-citation element).

Partial support of leaders (leader
element).

Support of hypertext links (external-destination and internal-destination properties).

New image converter based on the Java Image I/O library.

New Java property rtf.target.

Bug fixes

Paragraph attributes were not reset inside an empty table cell,
resulting in bad rendering by MS-Word whenever the very first cell of a
table was empty.

XSL Utility

Upgrade to FOP 0.20.4 and DocBook-XSL 1.60.1.

Version 1.0p1
(10/31/2002)

Enhancements

Revised and extended API (Professional Edition).

Bug fixes

Particular values of some shorthand properties would cause a
NullPointerException. This bug would show
up for instance when the value of the border, border-top,
border-bottom, border-left or border-right property did not specify the border
color, e.g. border-top="solid".

A bad property value would possibly result in additional
properties of the current object not being evaluated.

The background color of an outer block would not propagate to
inner blocks.

SAX exceptions were not handled properly, causing a NullPointerException when trying to convert an
ill-formed document.

Version 1.0 (07/26/2002)

First
commercial version.

Enhancements

Support of keeps and breaks properties in tables.

Support of the scale-to-fit value of
the content-width/content-height properties.

Bug fixes

The space-after and break-after properties were not handled
properly.

Image scaling was inaccurate when the content-width or content-height property was specified as a
<length> value.

Version 1.0b1
(06/05/2002)

New features

Automatic table layout.

Collapsing border model.

Support of the static-content (before and after
regions), footnote and page-number elements.

Enhancements

Support of lists in table cells.

Full implementation of the separated border model.

Partial support of keeps and breaks properties.

Support of the baseline-shift
property.

Support of the background color and border attributes of
inline-level elements.

Better selection of a page master among alternatives.

Use of the bullet character (\u2022)
as default label in bulleted lists.

Bug fixes

The font attributes of basic-link
elements were ignored.

The monospace generic family was not
bound to an actual monospaced font.

The list numbering type specification was not compatible with
Word 97.

White space between two inline-level elements was entirely
discarded.

The initial value of the column-number property did not consider row
spans, possibly causing an incorrect table layout in some
situations.

The initial value of the border-*-color properties was not properly set,
possibly causing a NullPointerException in
some situations.