Martijn Claus wrote: > > A working list in the rtf is essential for our customers, since the > customer can edit afterwards and references to the chapter/sections > numbers etc are made (which only works correctly when it is a real list, > otherwise it is only possible to make a reference to the number + > chaptername since it sees that as the title. Heuristics supporting our > type of numbering or a proprietary attribute with enough options to > specify a custom format would be perfect. > > With regard to the heuristics, apart from them being really simple, if > the first listitem is considered a list item (if it starts with a 1 for > example) the second, third, fourth etc item of that list should get that > listtype too. This is currently not the case. So this heuristic only > works for lists starting with a 1 or a and that contain only 1 item.
I'm sorry but I cannot reproduce the problem you describe, whatever the format of the generated file. When the first item is detected as being a typed list item using our rather crude heuristic, then all the following items get the same list type. (Re-re-re-tested that with a DocBook orderedlist converted to RTF, WordML, .docx and edited in MS Word 2007.) I suspect that you are saying that because in fact you generate several consecutive fo:list-blocks. > > In my opinion 3 things should be done: > 1 improving the heuristic that it also detects lists like 1.1 (1.2, 1.3) > and 2.3.1 (2.3.2, 2.3.3) and more reasonably common cases like a) b) c), > a b c etc. "a) b) c)" is already detected, as well as a number of other common cases. > 2 fixing that also other items in the same list (where the first item is > a detected listtype by the heuristic) don't get hardcoded but are made > into real listitems. > 3 adding support for 'custom' listtypes by supporting proprietary > attribute(s) in the xmlfo. Thank your for this feedback. > > For my company (and our customers) these 3 things are very important. > Therefore I have 2 more questions, which of these features are going to > make it into the next release and what is the scheduled release date of > that release? I'm sorry but I cannot answer any of the above questions. > (or is there another way to get this > heuristicfix/bug/feature faster?) I'm sorry but the answer is no. -- XMLmind FO Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/xfc-support
