[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: DOCBOOK-APPS: RE: Table problems in FO
Here's a test case: <?xml version="1.0" encoding="us-ascii"?> <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.2b1//EN" "http://www.oasis-open.org/docbook/xml/4.2CR1/docbookx.dtd"> <article> <title>Test Case</title> <para>This is test case for a problem in which tables with absolute column widths were all coming out of XEP with the default table width instead of the total of the column widths.</para> <table frame="all" colsep="1" rowsep="1"> <title>Table with Absolute Column Widths</title> <tgroup cols="4" align="center"> <colspec colwidth=".5in"/> <colspec colwidth="1in"/> <colspec colwidth=".75in"/> <colspec colwidth="1.5in"/> <thead> <row> <entry>.5in</entry> <entry>1in</entry> <entry>.75in</entry> <entry>1.5in</entry> </row> </thead> <tbody> <row> <entry>text</entry> <entry>text</entry> <entry>text</entry> <entry>text</entry> </row> </tbody> </tgroup> </table> </article> I processed this with the DocBook 1.58.1 stylesheets and XEP 3.13 to recreate the problem. I was able to fix the problem in a customization layer by changing the stylesheet default table width to "auto" instead of "100%". Jeff Beal -----Original Message----- From: Norman Walsh [mailto:ndw@nwalsh.com] Sent: Wednesday, January 01, 2003 3:26 PM To: Jeff Beal Cc: DocBook Mailing List (E-mail) Subject: Re: Table problems in FO -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 / Jeff Beal <jeff.beal@ansys.com> was heard to say: | First, if I don't specifically specify a rowsep or colsep on the tgroup, the | FO stylesheets are not drawing cell borders. I've been poking around for a | bit, and this line from the CALS specification seems to indicate that the | default value for these should be 1: "Default = IMPLIED, (means use value | from tgroupstyle if any, else from <table> if any, else '1')." ). " ( Right you are. Fixed. | My other problem is a little stickier. It involves table widths. We have | been using absolute column widths on all of our tables (2,392 of them, to be | exact.) and our current print engine (Epic 3.0.1) determines the table width | based on the sum of the column widths. The XSL stylesheets don't do that. | Without turning on the tablecolumn.extensions, we get columns that extend | past the edge of the table, or gaps between the edge of the rightmost column | and the leftmost column. With the tablecolumn.extensions, we get a lot of | tables that look either compressed or stretched. Can you provide an example of this problem? If you're specifying absolute widths for all the columns, I don't see how the absence of a width for the table should have any effect. Be seeing you, norm - -- Norman Walsh <ndw@nwalsh.com> | All things are contingent. And http://www.oasis-open.org/docbook/ | there is chaos.--Spalding Gray Chair, DocBook Technical Committee | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.7 <http://mailcrypt.sourceforge.net/> iD8DBQE+E07EOyltUcwYWjsRAtIEAKCImp8mCmPWVPs7OH/y8vAqJF4mpACeN5g9 LbUpKBCpF6nwYIFWL4g4+tY= =O+yf -----END PGP SIGNATURE-----
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC