On 05/19/2017 08:49 AM, Grundtvig Nielsen Niels wrote:
… marked as ‘low importance’, since I’ve worked out what the problem is
and how to correct it :-} but just so you know, it seems that using
<colspec> in DITA source can sometimes give odd results: specifically,
when the columns are not specified left-to-right in the code, the output
renders an additional column.
I’ve only been waiting since March for my colleagues to order the
update, and it is of course possible that this tiny glitch has
disappeared in newer versions.
In fact, specifying a <colspec colnum="1"/> AFTER a <colspec
colnum="2"/> is not allowed.
Excerpts from the CALS table specification:
---
<colspec>s can be numbered or unnumbered, and if numbered should be
increasing in sequential order starting at 1. Unnumbered <colspec>s are
interpreted as being numbered incrementally (one more than the previous
column number), with the first <colspec> starting at 1. Any mismatch in
<colspec> numbering, or a number of <colspec>s greater than cols, is an
error.
---
Next version of XMLmind DITA Converter detects this case and reports it
as an (non-fatal) error.
--
XMLmind XML Editor Support List
xmleditor-support@xmlmind.com
http://www.xmlmind.com/mailman/listinfo/xmleditor-support
