start-column, end-column, inside-column, and outside-column are added to axf:footnote-position.
The following issues have been corrected:
Columns in a table were not well balanced.
When the name of the external link of fo:basic-link was figures, the relevant page did not open.
A list arranged beside the float occasionally became incorrect when a page break occurred.
The rounding specification of table was not reflected in the background of table-row.
space-before specified to fo:block was not correctly secured when there was no border specification in fo:block, which was a parent of fo:float.
When the table was rotated, the width of the cell and the output position were not correct.
When axf:footnote-number-reset="page" was specified, footnote numbers were not outputted correctly.
Footnotes might be outputted to the wrong page.
When multiple fo:table-row were specified, table-marker were overlapped.
When multiple fo:table-row were specified, table-marker were overlapped.
A page broke with a big white space when the height was specified in table, table-row, and table-cell.
when axf:line-number-reset="page" was specified, numbers were not reset when the table broke or cells overflowed.
The position of the side note was not correctly outputted when the anchor was in FO which generated the reference area.
The border of table-marker might not be correct.
When the table extended over the next page, the position of the footnote in table-header was outputted incorrectly.
When there were table and block in block-container and it was not possible to break between table and block according to the keep condition, the block-container occasionally wholly moved to the next page without being broken in the table.
Punctuations occasionally overflowed from the cell.
An exception error occasionally occurred when a child of fo:table-row had fo:retrieve-table-marker.
The specification of left or right using the clear property did not match with the actually targeted float.
axf:footnote-keep="always" did not function correctly.
When setting the security with PDF embedding, the file that could not open was generated.
When embedding a specific PDF, an error occurred when opening the generated PDF.
When data with the Form field was outputted to PDF, the text in the field was not occasionally displayed.
When missing-glyph="0" was specified in the option settings, missing-glyph was not detected.
If the unit of px or em were specified for the size property, it occasionally became an error.
When the specified value of the size property is only length, the specification might be disregarded.
The character in fo:inline-container occasionally swerved to the vertical direction when script was specified in fo:block.
When PDF was embedded in the input data, an unnecessary text was occasionally displayed in GUI.
A part of the link might not become effective when formatting with two pass option.
The page only of several lines might be made by data with a lot of footnotes.
runtime error R6025 might be generated.
The link of bookmark might become invalid.
A table border might disappear.
The result might be different in the PDF output from GUI and the PDF output from the command line.
When PDF with the file name including the white space is specified as the background, it is not correctly outputted.
It is likely to become an error when a tagged PDF made by data with the acroform is checked with the accessibility checker tools in Adobe Acrobat (Full Check).
A memory leak might occur when formatting data that uses the image.
When a ligature is composed, stretch might not be reflected in the width calculation.
When the column block starts from the position where there is not enough space in the page and column balancing is performed, the column might not break.
When the PDF outputted by data with forms is opened with Acrobat Reader, it is likely to become an error.
The system error might occur if the font with a specific PFA format is used.
Font-stretch might work more than the necessity when the page overflows.
When data with the TIFF image is outputted in PDF, the image might be distorted.
When data with the image is outputted to PDF/A, PDF/A file might not exist though the formatting ends normally.
The column might overflow without breaking in an appropriate point when there is block-container in the column block and table or block-container is in it and the block with span="all" comes after the block.
The height of the table row with row-span might not become correct.
WMF might not be drawn correctly.
ChartML is not outputted to GUI, and the error might occur when the PDF is outputted.
The system error might occur when PDF is outputted by using data with the font of Khmer via Distiller.
The content of the cell might overflow to the right when the content needs to be split.
A missing glyph error might occur even if the glyph exists in the specified font.
When axf:overflow-condense="font-size" is specified and full width punctuation is specified to trim, the character might become small too much.
A period might be outputted to the start of line.
When the file is referred by specifying the relative path in data, it might not be interpreted correctly.
When outputting to INX, the box is out of alignment and the radio button occasionally overlaps.
When outputting to INX, a table might not be outputted.
The color fill in CGM data might not be correctly outputted.
When fo:index-key-reference page-number-treatment="link" is used and linked, it might not be linked correctly.
The column break processing in the nested table might not be correct.
The width of the rotated table cell might not become correct.
If FO contains too many SVG graphics, "PDF output failed" error occurs.
If FO contains particular SVG graphics, printer sometimes returns error.
Specifying axf:border-radius extended property to fo:table does not work correctly.
The error EPS file name is not displayed when outputting PDF from FO
Sometimes if text contains U+200B (ZERO WIDTH SPACE), text-align="justify"
does not work correctly.
Text portion of some type of EMF is not outputted to PDF or displayed.
Occasiobally clipping operation does not processed correctly for some type of EMF.
Some FO causes core-dump at INX output in Solaris version.
Some type of FO causes Java VM to crash when formatting using Java interface in Solaris version.
Occasionally FO that contains MathML causes Java VM to crash when formatting using Java interface.
Occasionally FO that contains MathML causes
"Unknown or unsupported graphic file" error.
Occasionally redundant space is inserted between PDF and text when formatting FO into PostScript.
Occasionally table in the first column overflows beyond page in the two column layout.
Some kind of FO can be formatted into PDF using Windows GUI but Code: 32778 error occurs when using command-line.
Some type of multi column FO causes table to overflow into footnote area.
Some Type1 font causes "Font read error: Extent Table read error".
Some OpenType font that has extension ".ttf" causes "Font file error: Bad sfntVersion type XXXXXXXX".
Some Type1 font causes "Font read error: Pair Kerning Table read error".
Courier New font sometimes causes "'GDEF' markAttach ClassDef error".
Occasionally rules of embeded PDF is not displayed.
Occasionally raster graphic does not displayed in CGM Option.
The specification was changed: When overflow="condense" and axf:overflow-condense="font-stretch" or axf:overflow-condense="font-size" are specified to fo:block-container, the text will be justified. But if text-align-last is specified explicitly, the last line will follow that specification.