On 10/27/2018 01:12 PM, David Clunie wrote:
Did you guys ever fix this bug, which assumes that a list
of numbers is supposed to be auto-numbered?
It just bit me again, for a list that was numbered 0, 90,
180, 270, which got rendered 0, 1, 2, 3 as a result of
the auto-numbering detection.
Your release notes on the web suggest that that this might
have been fixed in 5.4.4, with a command-line option
for -detectLists=false.
Yes, we did our best to fix this issue.
Excerpts from http://www.xmlmind.com/foconverter/changes.html#v5.4.4
---
Version 5.4.4 (April 26, 2017)
Enhancements:
* XMLmind XSL-FO Converter engine: user request: command-line
option -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.
---
Before purchasing anything from us, I would strongly suggest to first
download latest Evaluation Edition (VERSION 6.0 RELEASED TODAY)
http://www.xmlmind.com/foconverter/downloadeval.shtml#xfc_engine
and give it a try. Just in case you find new issues which would prevent
you from using our product.
--
XMLmind FO Converter Support List
xfc-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xfc-support
