| | Home|News|Products|Store|Contact |
| XMLmind XSL-FO Converter | ||
Enhancements:
Enhancements:
Enhancements:
Download
Buyunderline, overline,
line-through, etc), it's now possible to specify the color,
style (solid, double, dotted,
dashed, wavy) and thickness of the text
decoration. The syntax used for extended simple properties is identical
to the syntax of CSS3 property
text-decoration.Actual support of the “simple
properties” comprising text-decoration by the RTF,
WML, DOCX, ODT output formats varies, but this was already the case for
the decoration type (e.g. overline not supported by RTF,
WML, DOCX). More information in "Non-standard
extension of XSL-FO property
text-decoration".
bin/resolver.jar) by the XMLResolver
(bin/xmlresolver.jar).Bug fixes:
Enhancements:
Enhancements:
<navtitle>.Limitations when using XMLmind XSL Utility on a Mac having an Apple® M1 (ARM®) processor:
- JavaFX WebView crashes Java™ (bug
JDK-8276991), hence it has been disabled on this platform. As a consequence, this desktop application features a rudimentary online help system.
Regressions:
Enhancements:
idXSLTParameterName" for security reasons. This new
servlet parameter contains a regular expression matching XSLT parameter
names specifying which XSLT parameters are to be checked by XMLmind XSL
Server as having values containing syntactically correct XML or HTML
IDs.The sample web.xml file contained in shipped
xslsrv.war specifies "root\-?id" because XSLT
parameter "rootid" is implemented by the DocBook XSL
Stylesheets and XSLT parameter "root-id" is implemented by
the XHTML XSL Stylesheets.
Bug fixes:
In previous versions of MS-Word, these adjacent paragraphs used to look like a single block having specified background color. Is this a change in the behavior of MS-Word starting from version 2019 or is it a bug? We don't know. Anyway, this change had unwanted consequences.
This bug was caused
by the fact that XSL-FO property line-height was always
translated to RTF, WML and DOCX as some space between lines having at
least a value specified in points. Now, when property
line-height is specified as a relative value
(e.g."1.2", "120%", "1.2em",
"3ex"), it is translated to a multiple of the "Single" line
spacing, which seems to fix the bug. Of course, when property
line-height is specified as an absolute value
(e.g."14pt", "16px"), the bug is still
there.
Possible incompatibilities:
line-height is
translated to RTF, WML and DOCX differently than in previous versions of
the XMLmind XSL-FO Converter engine. Therefore documents created using
this version may look slightly different in terms of text line spacing
when opened in MS-Word.Enhancements:
If, for any reason, you prefer to use the
“system” Look & Feel, please start xslutil
by running
xslutil -putpref lookAndFeelClassName fallback
This setting is done once for all. If after doing that, you finally prefer to revert to FlatLaf, simply run
xslutil -delpref lookAndFeelClassName
Enhancements:
fo:block-container with a
reference-orientation attribute equal to 90,
270, -90 or -270 may be used to
temporarily switch the page orientation from portrait to landscape. This
feature is typically used to help MS-Word or OpenOffice/LibreOffice
display a wide table or a wide figure. More information here.<table orient="land">.wh-responsive-ui.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.Bug fixes:
vertical-align="center" instead of
vertical-align="middle", vertical-align being
a CSS shorthand mapping to XSL properties
alignment-baseline, alignment-adjust,
baseline-shift, dominant-baseline)
could cause the XMLmind XSL-FO Converter engine to raise a
NullPointerException.BIZ-UDMinchoM.ttc: Name does not exist in the TrueType collection: BIZ UD明朝 Medium) when converting an XML document to PDF.
Incompatibilities:
admon.graphics=1, admon.textlabel=0. In
previous versions, the default values of these parameters were:
admon.graphics=0, admon.textlabel=1.Enhancements:
border and
padding attributes were not supported for a
fo:inline element. They are now, but only if you use LibreOffice v5+ (does not
work with OpenOffice)
to open the file created by XMLmind XSL-FO Converter.font-family property contains a list of several font
families (e.g. font-family= "'FF Trixie',
'Andale Mono',monospace"). See "About
the font-family property".print" and FO_processor_name (that
is, "FOP", "XEP" or
"XFC").This version gives even more control over the numbering
of ordered lists. Specifying 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.
Bug fixes:
xslutil displayed a blank
window when the computer running xslutil was not connected
to the Internet.Incompatibilities:
ext/lib/jai_imageio.jar, which added support for
the TIFF and PNM image file formats, is not bundled with the XMLmind
XSL-FO Converter engine anymore. If you need XFC to support
the TIFF image file format, simple use a Java™ 11+ runtime.Enhancements:
xfc:label-format has now an
"inherit" parameter. Example:
xfc:label-format="%{lower-alpha;inherit})". Setting the
"inherit" parameter specifies that a numbered
fo:list-block “inherits” the numbering of its
ancestor numbered fo:list-blocks. In other words, this
parameter may be used to implement what is often called multi-level
numbering (e.g. 1.A.a.)More information in "The
xfc:label-format extension attribute".
xfc:render-as-table may be used as
a quick and easy workaround for one of the most annoying limitations of
XMLmind XSL-FO Converter: a fo:block having a border and/or
background color and containing several other blocks, lists or tables is
very poorly rendered in RTF, WML, DOCX and ODT. (Such container
fo:blocks are quite commonly used, for example, to
represent complex notes, admonitions or sidebars.)The reason of this limitation is due to the fact that the RTF, WML, DOCX and ODT output formats can —to make it simple— only contain a “flat” sequence of styled paragraphs and tables.
Example:
<fo:block margin="0.5em 2em" padding="1em 4em" border="1px solid #800000" background="#FFF0F0" xfc:render-as-table="true"> <fo:block space-before="0.5em" space-after="0.5em">First paragraph.</fo:block> <fo:block space-before="0.5em" space-after="0.5em">Second paragraph.</fo:block> <fo:block space-before="0.5em" space-after="0.5em">Third paragraph.</fo:block> </fo:block>
A fo:block having attribute
xfc:render-as-table="true" is automatically converted to an
equivalent fo:table by XMLmind XSL-FO Converter.
More information in "The
xfc:render-as-table extension
attribute".
xfc:label-format is used to create
proper RTF, WML, DOCX and ODT ordered lists, including nested
ordered lists which inherit their numberings from their ordered
list ancestors (that is, support for DocBook
orderedlist/@inheritnum="inherit").xfc:render-as-table is used to render
notes and sidebars. This attribute enables a workaround for a
limitation of XMLmind XSL-FO Converter: a fo:block
having a border and/or background color and containing several
other blocks, lists or tables is very poorly rendered in RTF,
WML, DOCX and ODT.pre;audio and video
elements), HDITA (topics and maps written in
HTML5) or MDITA Extended Profile (topics
and maps written in Markdown).More information in "Fancy code blocks" and in "Lightweight DITA support".
Please note that Markdown support of any kind in any XMLmind tool requires using a Java™ 1.8+ runtime.
Java 10 and 11 regression
[JDK-8211422]For some PNG images,
- Apache FOP reports error "I/O error while extracting image metadata: Error reading PNG metadata" and fails to render the PNG image.
- XMLmind XSL-FO Converter reports warning "cannot get the resolution of image 'file:/tmp/XXX.png': Error reading PNG metadata" and renders the image using default image resolution (96dpi; may be changed using option
-imageResolution=DPIor option/r DPI).For now, the only workaround for this bug is to open the faulty PNG image in an image editor (e.g. GIMP) and to re-export it as PNG under the same filename.
Bug fixes:
<fo:external-graphic src=" https://www.acme.com/logo.png "/>
were not trimmed before being parsed. (The recommended way to
specify an URL being:
<fo:external-graphic src="url(https://www.acme.com/logo.png)"/>.)xfc:restart-numbering extension attribute, which is
very useful when using named paragraph styles to create numbered
lists.Regressions:
controlapp which allowed to stop,
configure or reconfigure and start or restart both the bundled Jetty Servlet
Container and the XMLmind XSL Server WebApp has been discontinued.
XMLmind XSL Server is now available only as standard, ready to deploy,
xslsrv.war.Enhancements:
-docx.variant=MS-Word_major_version [ strict ]?.
Examples: -docx.variant=14,
-docx.variant=15strict. (Corresponding option for the .NET
version is: /variant.)This option may be used to mark generated DOCX files as being compatible with MS-Word having specified major version. Any major version other than 14 (MS-Word 2010), 15 (MS-Word 2013), 16 (MS-Word 2016) is currently ignored.
Moreover
suffix "strict" (supported only when
MS-Word_major_version >= 15) may be used to generate DOCX
files marked as being "Strict Open XML".
Unless this option is used, the generated DOCX files are not marked as being compatible with a specific version of MS-Word.
Specifying
-docx.variant=15suppresses the "[Compatibility Mode]" text appearing in the title bar of MS-Word 2013 and 2016.Note that specifying
-docx.variant=15does not prevent the generated DOCX file from being opened in MS-Word 2007 and 2010. However specifying-docx.variant=15strictgenerates "Strict Open XML" files which are not supported by MS-Word 2007 and 2010.
if the Java™ runtime used to run
xslutil is older than version 1.8.0_40, the system
Web browser rather than the dedicated, embedded Web browser is used to
display the Web Help, which is much less convenient for the
user.
Bug fixes:
http://docbook.sourceforge.net/release/images/draft.png.
Now XMLmind XSL Utility and XMLmind XSL Server use a local copy of this
graphics file.#foo) caused
the conversion to fail with the following error: Error: net.sf.saxon.trans.XPathException: Base URI {...} contains a fragment identifier.
Regressions:
ext/lib/jai_imageio.jar no longer supports the JPEG 2000
image file format.Please do not use newest Java 9 to run the programs which are part of XMLmind XSL-FO Converter. XMLmind XSL-FO Converter has not yet been tested against this version of Java.
Enhancements:
This version of ditac itself includes
XMLmind Web Help
Compiler (whc for short) version
2.0, which supports 2 layouts for the generated Web Help:
classic, the default layout and simple, a new
layout. If you want to give it a try, set XSLT stylesheet parameter
"wh-layout" to "simple".
Bug fixes:
Enhancements:
Other changes:
Enhancements:
-detectLists=false (.NET equivalent /nolist)
may be used to stop XFC from creating proper lists by inferring the
numbering style of the list from the label of its first item.Note
that even when this option is used, it's still possible to instruct XFC
to create proper lists by specifying extension attribute xfc:label-format
in the XSL-FO input file.
Bug fixes:
xml:lang="ja-JP") was converted as if it was a
western language specification.Note that for East Asian language detection by MS-Word to work on a Windows computer having a Western locale,
MS Gothic") for the text runs containing East Asian
characters.JP" in xml:lang="ja-JP")
was not correctly converted.Enhancements:
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:
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:
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. |
true | Convert input JPEG and SVG graphics to PNG in the output file. |
jpeg | Convert input JPEG graphics (not SVG graphics) to PNG in the output file. |
svg | Convert input SVG graphics (not JPEG graphics) to PNG in the output file. Default value for the RTF, WML and DOCX output formats, which anyway cannot contain SVG graphics. |
Parameter alwaysSaveAsPNG=false in previous
versions of XMLmind XSL-FO Converter is equivalent now to
alwaysSaveAsPNG=svg.
Enhancements:
Bug fixes:
suppress.navigation=0.Enhancements:
Partial DITA 1.3 support
XMLmind DITA Converter v2.6 supports all DITA 1.3 new elements (
line-through,steptroubleshooting,troubleshootingtopic, 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.
More information in "About DITA support in XMLmind DITA Converter".
Bug fixes:
java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it.
New implementation of XMLmind XSL-FO Converter for .NET
The new implementation no longer requires installing Microsoft Visual J#® 2.0 Redistributable Package on the computer used to run XMLmind XSL-FO Converter for .NET. This new implementation just requires a .NET 4.0+ framework on Windows or Mono 3.8+ on Linux.
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:
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:
xslutil -putpref displayScaling 200 controlapp -displayScaling 200
.dmg distribution including a private Java™ 1.8.0_66
runtime.Bug fixes:
Enhancements:
background-image
property of fo:region-body.As a consequence, SVG and MathML support in XMLmind XSL-FO Converter engine now requires using Java 1.6+.
Bug fixes:
Enhancements:
Bug fixes:
<fo:block break-before="page"/> <fo:block xfc:user-style="Heading 3">Heading 3</fo:block>
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.
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.Enhancements:
note.svg,
tip.svg, warning.svg).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.
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:<fo:external-graphic src="url(http://acme.com/logo-generator?w=100&h=200)"/>
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.
-Djava.awt.headless=true to all the
command-line executables, fo2docx, fo2odt,
etc, found in XFC_install_dir/bin/.Bug fixes:
fo:list-item-label caused the list
item to have an incorrect first line indent in the DOCX output file.
Example of empty fo:list-item-label:<fo:list-item>
<fo:list-item-label end-indent="label-end()">
<fo:block/>
</fo:list-item-label>
<fo:list-item-body start-indent="body-start()">
<fo:block>List item here.</fo:block>
</fo:list-item-body>
</fo:list-item>Incompatibilities:
/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).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:
More information in "XSL-FO extension for generating named styles".
Other enhancements:
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.
Bug fixes:
<fo:block> <fo:inline>A</fo:inline> <fo:inline>B</fo:inline> <fo:inline>C</fo:inline> </fo:block>
caused XFC .NET Edition to generate a paragraph containing "ABC", the expected value being a paragraph containing "A B C".
Enhancements:
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.
Enhancements:
orphans and
widows XSL-FO properties.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 orphans
or attribute widows to 1, Window and
Orphan control will be turned off. If, on the contrary, you set
attribute orphans or attribute widows
to any value greater or equal than 2, Window and Orphan control
will be turned on.
Unlike MS-Word, OpenOffice/LibreOffice fully
supports the orphans and widows XSL-FO
properties.
outputclass attribute of the
ol element. More information here. This
version also allows to generate self-contained Web Help. More
information here.Bug fixes:
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.Incompatibilities:
XMLmind XSL Utility and XMLmind XSL Server now allow to convert DITA documents to XHTML5 pages, Web Help containing XHTML5 pages and EPUB3.
In order to add support for the new output formats, the following components were upgraded in both XMLmind XSL Utility and XMLmind XSL Server:
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.
Enhancements:
Bug fixes:
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:
Bug fixes:
Enhancements:
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.
Bug fixes:
Enhancements:
Specifying outline levels allows to:
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).
Bug fixes:
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).
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.
Enhancements:
This feature has been tested using the Word application contained in the following Microsoft Office releases: Office 2003 + Compatibility Pack for Word, Excel, and PowerPoint 2007 file formats, Office 2007, Office 2010, Office 2011 Mac.
Microsoft Office Word 2007 minor bug
Microsoft Office Word 2007 has a minor bug in its handling of DrawingML. You are unlikely to encounter this minor bug. However, in order to fix it, you may have to install:
- The 2007 Microsoft Office Suite Service Pack 2 (SP2). Service Pack 2 provides the latest updates to the 2007 Microsoft Office Suite. This update also applies to Microsoft Office Project, Microsoft Office SharePoint Designer, Microsoft Expression Web, Microsoft Office Visio, and Visual Web Developer.
- Update for Microsoft Office Word 2007 (KB974561). Microsoft has released an update for Microsoft Office Word 2007. This update provides the latest fixes to Microsoft Office Word 2007. Additionally, this update contains stability and performance improvements.
Doing this brings Word 2007 to SP2 MSO 12.0.6554.5001.
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.
The syntax of this attribute is:
label-format -> [ bullet | number ]?
bullet -> String
number -> [String]? '%{' format '}' [String]
format -> 'decimal'|'lower-alpha'|'upper-alpha'|
'lower-roman'|'upper-roman' [start]?
start -> ';start=' Positive_IntegerExamples: xfc:label-format="", xfc:label-format="→", xfc:label-format="%{lower-alpha;start=3}.", xfc:label-format="-%{decimal}-".
Bug fixes:
XMLmind XSL Utility and XMLmind XSL Server now allow to convert the most complex DITA 1.2 documents to a variety of formats.
Other enhancements:
Bug fixes:
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.
Other enhancements:
<init-param> <param-name>customizeDir</param-name><param-value>/etc/xslutil</param-value> </init-param>then run xslutil -p /etc/xslutil to configure the conversions of XMLmind XSL Server.
Bug fixes:
<imagedata fileref="/images?id=ef31" format="GIF"/>
from being converted to PDF, RTF, etc.
Enhancements:
Note that content-type ``sniffing'' is implemented only for SVG and MathML and that content-type attributes starting with "namespace-prefix:" are completely ignored.
SVG support is based on the Batik Open Source Java 1.5+ component.
MathML support is based on JEuclid Open Source Java 1.5+ component.
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 -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).
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.
This attribute is used by the DocBook XSL stylesheets included in XMLmind XML Editor and in XMLmind XSL Utility and also by XMLmind DITA Converter (ditac) to generate nicer Tables of Contents (TOC).
Bug fixes:
Incompatibilities:
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:
Incompatibilities:
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:
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+).
Unlike ditac, a command-line utility, XMLmind XSL Utility is a graphical tool which makes it easy parameterizing the DITA conversion process.
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.
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.
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.
Bug fixes:
Incompatibilities:
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.
Bug fixes:
License and price changes:
Enhancements:
In practice, this means that XMLmind XSL Utility now:
Bug fixes:
Moreover this limitation was not documented.
Incompatibilities:
This allows to evaluate the integration of the XMLmind XSL-FO Converter engine in your application simply by using the xfc.jar or xfc.dll library found in the distribution of Personal Edition.
Note that XMLmind XSL Utility now requires a JavaTM runtime version 1.5 and above to run.
Both distributions are self-contained.
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 XMLmind XSL Utility are now stored in various files found in user_preferences_dir/.
Directory user_preferences_dir/ is:
Example: C:\Documents and Settings\john\Application Data\XMLmind\FOConverter\ on Windows 2000 and XP. C:\Users\john\AppData\Roaming\XMLmind\FOConverter\ on Windows Vista.
Bug fixes
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.)
New features
XSL-FO extension to generate structured document tags (SDTs) in an Office Open XML document.
Bug fixes (WML)
Character '>' was not escaped in string "]]>", resulting in invalid XML content.
Bug fixes (OOXML)
Character '>' was not escaped in string "]]>", resulting in invalid XML content.
Page number format was not properly specified in section properties.
Bug fixes (OpenDocument)
Character '>' was not escaped in string "]]>", resulting in invalid XML content.
Images in headers/footers did not show in OpenOffice, due to
missing namespace declarations in file styles.xml.
XSL Utility
Use of XML catalogs for resolution of URIs in XSLT stylesheets.
Enhancements
Support of image viewport.
New property imageResolution to
specify source image resolution.
New property prescaleImages to
specify image scaling policy.
New license terms (Personal Edition).
New features
Support of Open XML as alternate output format.
Enhancements
New property singleSidedLayout to
force single-sided page layout.
XSL Utility
Upgraded FOP to version 0.93.
Upgraded DocBook-XSL to version 1.71.1.
Added DTD for DocBook v4.5.
New licensing scheme (Professional Edition).
Enhancements
Improved automatic table layout provides better handling of very long words in table cells.
Bug fixes (RTF)
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.
New licensing scheme (Professional Edition).
Enhancements
Improved automatic table layout provides better handling of very long words in table cells.
Bug fixes (RTF)
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.
New features
Support of OpenDocument as alternate output format.
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.
Added DTD for DocBook v4.4.
Upgraded DocBook-XSL to version 1.69.1.
First .NET version.
Enhancements
Revised and extended API (Professional Edition).
Bug fixes
Characters U+00AD (soft hyphen) and
U+2011 (non-breaking hyphen) were not
handled properly.
Bug fixes (RTF)
The font table writing did not strictly conform to the RTF specification. This syntax error would make RTF documents unreadable by TextEdit and possibly other Mac OS X applications.
XSL Utility
Upgrade of Saxon to version 6.5.4.
New transformation XHTML to RTF (XSLT stylesheet by Antenna House).
Enhancements
Better handling of white space at the beginning/end of a paragraph.
Fixed issue with characters '-' and '.' in id property values. (The RTF loader of MS-Word
replaces these characters with '_' (underscore) in bookmark
names.)
Bug fixes
List item labels containing non-textual objects (e.g. images) were not handled properly. (This bug was introduced with version 2.1.)
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
XSL-FO extensions - e.g. fox - were
not handled properly, resulting in an ArrayIndexOutOfBoundsException.
Initial release.