Skip to main content
1-Visitor
March 10, 2010
Question

Spanning causes introduces colsep

  • March 10, 2010
  • 5 replies
  • 1055 views

Hello,

In Arbortext when I try to span 2 cells in a table my entry gets a attribute colsep="1". I don't need colsep attribute to be inserted when I span 2 cells. Is there a way to turn this off?

Karthik

    5 replies

    1-Visitor
    March 11, 2010
    On Wed, Mar 10, 2010 at 4:04 PM, Karthik Kumar
    <karthik.kumar@merrillcorp.com> wrote:
    > In Arbortext when I try to span 2 cells in a table my entry gets a attribute
    > colsep="1". I don't need colsep attribute to be inserted when I span 2
    > cells. Is there a way to turn this off?

    Can you post an example (preferably a small one) of the markup before
    and after and the exact steps you took in between? Also, what DTD are
    you using (or the table model, anyway), and which version of Editor?

    -Brandon 🙂
    1-Visitor
    March 11, 2010

    Hello Brandon,

    ArborText version is 5.3 and I tried it in our DTD that uses CALS table model. I also tried it on DocBook DTD and the sample attached uses docbook DTD.

    You will notice 2 tables - the first one without cell span and the next one with cells span.

    Before spanning

    <tgroup cols="2">
    <colspec colname="col1"/">
    <colspec colname="col2"/">
    <tbody>
    <row>
    <entry>Cell 1</entry>
    <entry>Cell 2</entry>
    </row>
    <row>
    <entry>Cell 3</entry>
    <entry>Cell 4</entry>
    </row>
    </tbody>
    </tgroup>

    After the spanning it markup changes like:

    <tgroup cols="2">
    <colspec colname="col1"/">
    <colspec colname="col2"/">
    <tbody>
    <row>
    <entry colsep="1" nameend="col2" namest="col1"&lt;br"/>>Cell 1</entry>
    </row>
    <row>
    <entry colsep="1" nameend="col2" namest="col1"&lt;br"/>>Cell 3</entry>
    </row>
    </tbody>
    </tgroup>

    Thanks,

    Karthik

    1-Visitor
    March 12, 2010
    Hi, Karthik...

    On Thu, Mar 11, 2010 at 10:40 AM, Karthik Kumar
    <karthik.kumar@merrillcorp.com> wrote:
    > ArborText version is 5.3 and I tried it in our DTD that uses CALS table
    > model. I also tried it on DocBook DTD and the sample attached uses docbook
    > DTD.
    >
    > You will notice 2 tables - the first one without cell span and the next one
    > with cells span.

    I tried this with both Arbortext Editor 5.3 M120 and 5.4 M010, with
    identical results. I created a new Docbook document and added a
    2-row, 2-column table, filling in the content you had in your example
    such that the markup looked identical to your "before" case.

    > Before spanning
    >
    > <tgroup cols="2">
    > <colspec colname="col1"/">
    > <colspec colname="col2"/">
    > <tbody>
    > <row>
    > <entry>Cell 1</entry>
    > <entry>Cell 2</entry>
    > </row>
    > <row>
    > <entry>Cell 3</entry>
    > <entry>Cell 4</entry>
    > </row>
    > </tbody>
    > </tgroup>

    I then spanned the cells in the first row using the "Table", "Span
    Cells" menu item. After that, I spanned the cells in the second row
    using the Alt+F11 keyboard shortcut. In both versions of Editor, the
    resulting markup was:

    <tgroup cols="2">
    <colspec colname="col1"/">
    <colspec colname="col2"/">
    <tbody>
    <row>
    <entry nameend="col2" namest="col1">Cell 1 Cell 2</entry>
    </row>
    <row>
    <entry nameend="col2" namest="col1">Cell 3 Cell 4</entry>
    </row>
    </tbody>
    </tgroup>

    > After the spanning it markup changes like:
    >
    > <tgroup cols="2">
    > <colspec colname="col1"/">
    > <colspec colname="col2"/">
    > <tbody>
    > <row>
    > <entry colsep="1" nameend="col2" namest="col1"&lt;br"/>>>Cell 1</entry>
    > </row>
    > <row>
    > <entry colsep="1" nameend="col2" namest="col1"&lt;br"/>>>Cell 3</entry>
    > </row>
    > </tbody>
    > </tgroup>

    Note that my markup does not include the "colsep" attributes and that
    it also includes all of the content of the two cells that were
    spanned, where yours includes only the content of the first cell. In
    order to figure out why you're seeing this behavior, we need to
    eliminate the differences between our cases.

    Which patch level (M???) of 5.3 are you on? Can you give me more
    detailed steps that I need to follow to produce this result? Could
    there be any preference settings in your environment that might be
    affecting the results?

    -Brandon 🙂
    1-Visitor
    March 12, 2010

    Thank you so much Brandon for trying this. Both of us did exactly the same thing and we are seeing different result.

    I found one thing today - When I spanned the cell on AT 5.3 M010 it puts colsep. However when I tried it os AT 5.4 it does not put colsep. May be this is because of the patch.

    Karthik

    1-Visitor
    March 12, 2010
    Yes, if you're seeing this on 5.3 M010, I'd definitely try a newer
    release before putting any more effort into tracking it down. There
    have been 16 releases of 5.3 since M010 (and 4 of version 5.4), so
    it's quite likely that what you're seeing is a bug that has since been
    fixed.

    -Brandon 🙂

    On Fri, Mar 12, 2010 at 2:38 PM, Karthik Kumar
    <karthik.kumar@merrillcorp.com> wrote:
    > Thank you so much Brandon for trying this. Both of us did exactly the same
    > thing and we are seeing different result.
    >
    > I found one thing today - When I spanned the cell on AT 5.3 M010 it puts
    > colsep. However when I tried it os AT 5.4 it does not put colsep. May be
    > this is because of the patch.
    >
    > Karthik