OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

docbook-apps message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: RE: DOCBOOK-APPS: PassiveTeX table kluge


Pretty much.  In looking at the stylesheets, this may be a bit of work.  I
thought I could make the following two changes and have it work:

Add this line:

  <fo:table-column column-number="153" column-width="0in"/>

just before the final <xsl:choose> element in the template matching "tgroup"

In the template matching "row", add this line:

  <fo:table-cell column-number="153"/>

inside the <fo:table-row/> element.  

FOP blew up on my test document, complaining that columns 3 through 152 were
never defined.  But, the FO spec says "There is no requirement for
column-numbers to be monotonically increasing from formatting object to
formatting object."  That sounds to me that it's the order of the
<fo:table-column>'s that determines the order of the columns, not their
numbering, and the numbering is just a means of identifying a particular
column.  (Which would allow you to pick an arbitrarily high column number
for the empty column, as above, and leave the other columns alone.)  FOP, at
least, disagrees, but if PassiveTex agrees with me, those changes may work.
Otherwise, you may want to look into either a pre- or post-processing step.
(I have a couple of ideas on that, too, but won't be able to tackle them
until tomorrow.)

Jeff

-----Original Message-----
From: Dennis Grace [mailto:dgrace@us.ibm.com]
Sent: Monday, September 23, 2002 5:31 PM
To: Jeff Beal
Cc: Docbook-apps
Subject: RE: DOCBOOK-APPS: PassiveTeX table kluge



Jeff Beal said:

>>>>>
I haven't looked into this particular problem with Passivetex, but this
sort
of solution seems to be entirely doable in an XSL customization layer.
That
way, you don't have to worry about keeping the contents of your two tables
in sync with each other.
<<<<<

Ooh, I like that idea. Hadn't thought of it.

So, for each table or informaltable, the FO customization layer would
increment the cols by one, insert the colspec, increment any other existing
colspecs, add an empty entry after each <row>.  Am I forgetting anything?

Dennis Grace

Information Developer
IBM Linux Technology Center
(512) 838-3937  T/L 678-3937  cell: (512)-296-7830
dgrace@us.ibm.com

There are only 10 kinds of people in the world: those who understand binary
and those who don't.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC