I looked these questions up in the OASIS standard for Cals tables, located at:

http://www.oasis-open.org/specs/tm9502.html

The relevant text is regarding rowsep in entrytbl is:

"ROWSEP: If other than zero, display the internal horizontal rulings below <entrytbl> (but not for the last row of the table, where the table frame setting applies). If zero, do not display ruling. The <entrytbl> rowsep overrides possible different rowseps on <entry>s in the last row of the <entrytbl>. Default source for <row>s and possibly <entry>s in <entrytbl>."

The answer to your first question is that, yes, @rowsep on entrytbl does override the inherited value from its ancestors, so rowsep="0" should have no rule on the cell containing the subtable.

Regarding your second question, the relevant text on entry is:
"Default = IMPLIED, from the closest ancestor with explicit specification of 
rowsep:

 a.. <row> then

 b.. <spanspec> or <colspec> then

 c.. <tgroup> or <entrytbl> then

 d.. <table>."

That says to me that an entry inside an entrytbl will inherit the rowsep value from entrytbl. So in this case it appears that rowsep serves two purposes. To override the inheritance, you would have to put rowsep on every row in the entrytbl, since tbody does not take rowsep.

Bob Stayton
Sagehill Enterprises
b...@sagehill.net


----- Original Message ----- From: "ben.guillon" <ben.guil...@gmail.com>
To: <docbook@lists.oasis-open.org>
Sent: Tuesday, March 16, 2010 5:26 PM
Subject: [docbook] entrytbl/@rowsep role


Hi,

Can you confirm the role of the <entrytbl> @rowsep. AFAIK, its role is the same than for a normal <entry>, that is: if entrytbl/@rowsep=0, the cell will not have a rule below itself, whatever the tgroup/@rowsep or row/@rowsep value is. in brief, the entrytbl/@rowsep has precedence over al the enclosing elements @rowsep. Am I right?

Just to be sure: if you have the XML:

<table frame="all">
  <title>Test table with sub-tables and screen elements</title>
  <tgroup cols="1" align="left" colsep="1" rowsep="1" >
     <colspec colsep="1" rowsep="1" />
     <tbody>
           <row>
             <entrytbl cols="2" rowsep="0">
                <!-- ... -->
             </entrytbl>
           </row>
           <row>
             <entrytbl cols="2" rowsep="0">
                <!-- ... -->
             </entrytbl>
           </row>
      </tbody>
   </tgroup>
<table>

Do you confirm it should give:

  -------------
  | subtable1 |
  |           |
  | subtable2 |
  |           |
  | .......   |
  |           |
  | subtableN |
  -------------

Another question about the entrytbl/@rowsep role: is it inherited by the contained rows? For instance, if entrytbl/@rowsep=0, do the rows without @rowsep in the entrytbl have no rule below them?

Example:

<table frame="all">
  <title>Test table with sub-tables and screen elements</title>
  <tgroup cols="1" align="left" colsep="1" rowsep="1" >
     <colspec colsep="1" rowsep="1" />
     <tbody>
           <row>
             <entrytbl cols="2" rowsep="0">
                <tbody>
                  <row> ... </row> <!-- no rule below -->
                  <row> ... </row> <!-- no rule below -->
                  <row> ... </row> <!-- no rule below -->
                </tbody>
             </entrytbl>
           </row>
           <row>
             <entrytbl cols="2" rowsep="1">
                <tbody>
                  <row> ... </row> <!-- rule below -->
                  <row rowsep="0"> ... </row> <!-- no rule below -->
                  <row> ... </row> <!-- rule below -->
                </tbody>
             </entrytbl>
           </row>
      </tbody>
   </tgroup>
<table>

Thanks for your help.

Regards,
BG

---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org





---------------------------------------------------------------------
To unsubscribe, e-mail: docbook-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-h...@lists.oasis-open.org

Reply via email to