What's new in this version:
- XHTML, DITA topic, DocBook configurations: the "Add image" toolbar button now allows to add an image map to your document.
- Once the image map element has been added, right-clicking anywhere in this element and selecting "Edit Image Map" from the contextual popup menu displays a specialized image map editor. This image map editor allows to add “hot areas” to your image. More information in the "Edit Image Map" dialog box.
- New image map editor also has a facility allowing to make the “hot areas” visible and/or to give them numbers so they can be referred to by number. This facility automatically generates an SVG file embedding the original image file and adding the chosen visual marks above the embedded image.
- Command "DocBook|Link callouts" has better support for graphicco, imageobjectco, programlistingco, screenco elements, that is, for elements using area and/or areaset elements rather than co elements to mark areas of interest in an image or a program listing.
- XHTML iframe element is now rendered by embedding a Web browser in the styled view
- The XSLT stylesheets used to convert XHTML to XSL-FO now generate a numbered list for a XHTML map element, 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 elements specifying no link at all). This numbered list may be suppressed by setting XSLT stylesheet parameter show-map-links to 'no'.
- When possible, the caret now remains at the same location —between the two joined fragments— after joining adjacent elements by pressing DEL or BACKSPACE
- Upgraded XMLmind Assembly Processor to version v1.0.1
- Upgraded the "Word To XML" add-on to XMLmind Word To XML v1.2.1_01
- Upgraded XMLmind DITA Converter (ditac for short) to version 3.1.2
- Upgraded Saxon to version 18.104.22.168
- When converting a DocBook document to Web Help with the following XSLT stylesheet parameters: suppress.navigation=0, navig.graphics=1, the navigation icons (Home, Previous, Next, Up) were missing in the generated HTML pages.
- "DocBook|Paste As|Paste From Word" did not work in a DocBook 5.1 topic, nor in any DocBook document conforming to a customized schema (e.g. ).
- DocBook CSS stylesheets: refsection, refsect1, refsect2 and refsect3 were not styled as collapsible blocks.
- XHTML 5: data-XXX attributes were not copied when using Edit|Convert. For example: < strong id="i1" data-foo="bar" > was converted to < strong id="i1" > and not to < strong id="i1" data-foo="bar" > as expected.
- XHTML: an iframe element was saved as an empty element, that is, as follows: < iframe src="http://www.xmlmind.com" >. This is interpreted by Web browsers as an iframe start tag with no corresponding close tag. To fix this issue, an iframe element is now saved as follows: < iframe src="http://www.xmlmind.com" >< /iframe >.
- Opening a document styled using a CSS stylesheet making a very heavy use of label(xpath,XPath_expression) was very slow.
- On Windows, dragging and dropping the URL of a media file (e.g. "http://techslides.com/demos/sample-videos/small.mp4") from a Web browser onto the media player used to render audio and video elements added an internet shortcut (.URL file) to the media player dialog box.
- Fixed a bug in the "Use integrated input method support" feature. This bug caused for example the following incorrect behavior using the Japanese Hiragana input method: typing n, e, k, o, SPACE (to insert the Kanji for neko) three times in row, without pressing each time ENTER to commit the Kanji for "neko", inserted the Kanji for "neko" three times but with an "n" between each Kanji.
- When a node range was selected, in some cases, using "Edit|Copy as Text" caused XXE to fail with a NullPointerException.
- Command-line utility xxetool did not pick up the customizations done using "Options|Customize Configuration|Customize Document Conversion Stylesheets".
- When XXE is deployed using Java™ Web Start, bundling TTF font files and a FOP configuration file (e.g. fop.conf) pointing to these local TTF font files in a customization of the "Apache FOP 1.x XSL-FO processor plug-in" add-on caused the conversion to PDF to fail with the following error message: "FOP XSL-FO processor error: java.lang.IllegalArgumentException: URI is not absolute".
- "Apache Batik image toolkit plug-in" add-on: fixed the following Batik 1.8 bug: BATIK-1090; Embedded SVG reports "Content is not allowed in prolog"; https://issues.apache.org/jira/browse/BATIK-1090.
- All DocBook configurations: "Convert Document|Convert to Web Help" now generates Web Help containing XHTML 5.0 pages. This change was needed to support DocBook audio and video elements.
- All DITA configurations: "Convert Document|Convert to Web Help" now generates Web Help containing by default XHTML 5.0 pages. "Options|Customize Configuration|Customize Document Conversion Stylesheets" allows to select an alternate stylesheet generating Web Help containing XHTML 1.0 pages.
- When converting a DITA document to single-page or multi-page XHTML or to Web Help, SVG graphics are no longer automatically converted to PNG.
- Adobe Flash being now obsolete, replaced item "object(flash)" by "object(youtube)" in the menu displayed by the "Insert media object" button of the DITA Topic toolbar.