November 17, 2011
CSS – The following issues have been corrected:
- When checking the syntax of a formula, the calculation of an absolute unit plus a relative unit produced an error.
- avoid-widow-words did not become effective.
- A closing parenthesis at the end of a line did not become half-width.
- When the block progression dimension was specified, block was rotated 90 degrees, and the size of the block was auto, text-align:center did not work correctly.
- When min-height and -ah-display-align were specified to the block, the arrangement of the block contents might become inaccurate
- When there was a br tag which was not surrounded by div, the position of the float might shift.
XSL – The following issues have been corrected:
- The specification when converting U 0085 and U 2028 into U 000A in the text was not controlled between XML 1.1 and 1.0 version.
- The block with the absolute position was arranged to the wrong page.
- When Variation Sequence was used, a font error occurred with PS output.
- keep-together.within-page=”always” did not become effective.
- starts-row=”true” specified as the table footer instead of table-row might not function correctly.
- When the table was rotated and the table break occurred, the content of the table cell was outputted also to the adjacent cell.
- When double line was specified to the cell of table-header, a part of line after the page break did not become double line.
- The table row overflowed region-body with a specific data.
- When overflow=”error-if-overflow” was specified to region-body and overflow occurred, an error was not shown by the table overflow in the in-line progression dimension.
- When axf:punctuation-trim=”all” and axf:overflow-condense=”font-stretch” were specified, the content overflowed the flame.
- When the document had multiple flows which were assigned to multiple region bodies, the region body for the page master assigned to the last page appeared on the second to last page.
- Retrieve table marker in the table header caused the table columns overflow on mulit-column pages.
Common – The following issues have been corrected:
- When axf:alt-glyph was specified, the character might fall off partially while outputting to PS and XPS.
- auto-fallback-font=”false” did not become effective on the font selection by script.
- The formatting process did not end when ligature-mode=”latin” was specified.
- The character of 𠮷 in vertical writing data did not become vertical when outputting to PDF.
- When Variation Sequence was used, spaces between ideographic characters and European characters were not being added.
- Font aliases were not correctly saved in the Area Tree.
- 2pass option caused the page number citation to be incorrect.
- When intrusion-displace=”block” was specified and data has float=”inside” or float=”outside”, even if a page break occurred on the way, the position of the block was affected by the float.
- The float broke across page and didn't honor intrusion displace.
- Cursive Arabic scripts were not outputted correctly.
- Text overlapped when specific fonts were used.
- Formatter crashed when opening CGM.
- PDF output of Formatter caused an error in Acrobat when using STIX font.
- When a font with font-weight, without bold was used, the inaccurate dash pattern was outputted to the outline.
- Unnecessary page was created after the spanned block.
Other – The following issues have been corrected:
- The position of text was incorrect when specific fonts were used.
- Text in the private use area was not shown in PDF.
- MathML caused a system error when the predefined symbol element of the content element was not the first child element of the parent.
- EMF did not have all of the content rendered in Formatter.
- Runtime error occurred with the COM interface when the option setting file was not correctly set.
- EMF images were not rendered partially. CGM images were not rendered when using CGM plugin.