I've come across a strange quirk in how Arbortext Editor 5.3 deals with
tables in a particular situation.
I am using namespaced CALS table mark-up in my schema with which
(non-technical) users are creating tables using Arbortext's WYSIWYG
tool. It appears that these users are adding additional rows to their
tables by highlighting a previous row and copying and pasting this row
at the end of the table just before the closing </table> element. While
I appreciate this isn't the correct way of adding table rows (which I
have told my users) it has illustrated a particular issue.
The first thing I noticed was that all the table mark-up was repeated
from <tgroup> onwards, although as valid mark-up it isn't necessarily a
big issue. However, I also noticed that all namespace prefixes from the
inserted row mark-up had disappeared, as per the following example:
<namespace:table>
<namespace:tgroup cols="2">
<namespace:colspec colname="col1"/">
<namespace:colspec colname="col2"/">
<namespace:tbody>
<namespace:row>
<namespace:entry>
<namespace:block>
<namespace:text>Some text</namespace:text>
</namespace:block>
</namespace:entry>
<namespace:entry>
<namespace:block>
<namespace:text>Some text</namespace:text>
</namespace:block>
</namespace:entry>
</namespace:row>
<namespace:row>
<namespace:entry>
<namespace:block>
<namespace:text>Some text</namespace:text>
</namespace:block>
</namespace:entry>
<namespace:entry>
<namespace:block>
<namespace:text>Some text</namespace:text>
</namespace:block>
</namespace:entry>
</namespace:row>
</namespace:tbody>
</namespace:tgroup>
<tgroup cols="2">
<colspec align="left" colname="col1"<br"/>colwidth="1.00*"/>
<colspec align="left" colname="col2"<br"/>colwidth="1.00*"/>
<tbody>
<row>
<entry>
<block>
<text>Some text</text>
</block>
</entry>
<entry>
<block>
<text>Some text</text>
</block>
</entry>
</row>
</tbody>
</tgroup>
</namespace:table>
Not only is this pretty strange behaviour it is also invalid to the
schema. However, Arbortext doesn't recognise this mark-up as being
invalid when it is initially inserted, it only does so once the file has
been closed and reopened again. This means that invalid table mark-up
can be created without users necessarily knowing they are doing it.
As I say, I have corrected my users so that additional rows are being
inserted in a more appropriate manner from now on using the UI provided
so this problem should disappear from our content but I thought I'd
raise in case anyone else had come across this issue? Does anyone know
if this is expected/acknowledged behaviour, has it already been fixed in
a maintenance release or should it be raised as a bug?
cheers
Mark Jones
LexisNexis is a trading name of REED ELSEVIER (UK) LIMITED - Registered office - 1-3 STRAND, LONDON WC2N 5JR
Registered in England - Company No. 02746621
