AH XSL Formatter Standard V6.5 R1
Released: Sep 21, 2017
Updates in V6.5 R1
Features
-
Enhancements:
- PDF/A-2 and PDF/A-3 are now available to output.
- Multimedia can now be embedded as rich media
- The axf:layer-settings parameter that defines the layer has been extended.
- Custom properties can now be specified to PDF.
- Specify the font size of the character string displayed in the Form Fields.
- Specify the alignment of a text field.
- The stroke of a character can now be specified.
- The feature of GSUB/GPOS in the OpenType font can now be controlled.
- Line numbers that are always outputted can now be specified.
- The upper limit height of the “keep-together” condition can now be specified.
- Specify the display method at the end of the contents when overflowing in the inline progression direction.
- The odd-or-even property has been extended.
- The processing of converting transparency output to PDF into opaque has been extended.
- Support for fonts in OpenType Collection format.
- Exception dictionaries are now available in Khmer, Lao and Burmese (Myanmar).
- XCF can now be directly specified as a child element of <fo:external-graphic>.
- It is now available to specify whether the external reference is permitted or not in <!ENTITY> of XML to be formatted.
- Word(docx) output is now available.
Fixes
- When space-before was specified for a parent fo: block, the placement of fo:float was sometimes incorrect.
- The keep property on the list item led to the incorrect position of text that followed it.
- Footnote references positioned incorrectly after the float.
- The processing of axf:column-rule-display=”all” was incorrect in vertical document.
- The processing of the length axf:column-rule-length) specified by % was incorrect in vertical document.
- axf:punctuation-spacing sometimes affected on trimming other than the space between full-width punctuation and full-width character.
- The line break position of Myanmar characters was incorrect.
- A data with security settings created a corrupt pdf.
- Fallback errors for glyphs that were in the applied font.
- Crash with data that used an incorrect font.
- Crash with a cgm file.
- The script settings to font-entry in MathML were not effective.
- Another company's product opened Formatter GUI with Japanese interface in the English environment.