Thanks Bob! 

Its strange that no one has had any problems in the past. It could be that the 
processors blow right by it and only complain about it lightly.

I filed a bug report: #3000898

Thanks
Dean


In a message dated 05/12/10 17:25:50 Pacific Daylight Time, [email protected] 
writes:
I also find this behavior a bit odd.  It is not accidental, as there is a 
specific bit 
of code that turns off column-width when set to 1: 

<xsl:if test="$colwidth != 'proportional-column-width(1)'"> 
 <xsl:attribute name="column-width"> 
   <xsl:value-of select="$colwidth"/> 
 </xsl:attribute> 
</xsl:if> 

The $colwidth variable is computed, and if its value is 
"proportional-column-width(1)" 
then no column-width attribute is output at all!  I have no idea why this step 
is 
taken.  This bit of code has existed in the table.xsl file since it was first 
created 
by Norm Walsh in 2001.  It may have been a limitation of early FO processors, 
but it 
certainly isn't desirable behavior now. 

Please file a bug report on SourceForge for this item. 

Bob Stayton 
Sagehill Enterprises 
[email protected] 


----- Original Message ----- 
From: [email protected] 
To: [email protected] 
Sent: Wednesday, May 12, 2010 4:42 PM 
Subject: [docbook-apps] Table column proportional values 


Hello everyone, 

I started paying attention to the warning messages that FOP puts out and 
discovered an 
issue in one of my tables. It appears that the 'colwidth' attribute is a bit 
touchy 
with the values that it gets. If a value is specified as "1*" it will not 
generate the 
proportional XSL-FO code that it needs and then out puts a message: 



WARNING: table-layout="fixed" and column-width unspecified => falling back to 
proportional-column-width(1) (See position 560:47) 

This in itself is not a big problem, but when tracking down why it did that, 
the 
1.75.2 version of the stylesheets emits some code that doesn't seem right. I'm 
using 
XSLTPROC but I get the same results with Saxon 6.5.5 and without any 
customization 
layer. 

Example 1: 
               <colspec colname="c1" colwidth="1*" align="left"/> 
               <colspec colname="c2" colwidth="2*" align="left"/> 
               <colspec colname="c3" colwidth="2*" align="left"/> 

produces in the FO file: 
         <fo:table-column column-number="1"/> 
         <fo:table-column column-number="2" 
column-width="proportional-column-width(2)"/> 
         <fo:table-column column-number="3" 
column-width="proportional-column-width(2)"/> 

and thus produces the warning. Whereas changing the '1*' to '3*' in the first 
column 
produces no warning. 

Example 2: 
               <colspec colname="c1" colwidth="3*" align="left"/> 
               <colspec colname="c2" colwidth="2*" align="left"/> 
               <colspec colname="c3" colwidth="2*" align="left"/> 

produces in the FO  file: 
         <fo:table-column column-number="1" 
column-width="proportional-column-width(3)"/> 
         <fo:table-column column-number="2" 
column-width="proportional-column-width(2)"/> 
         <fo:table-column column-number="3" 
column-width="proportional-column-width(2)"/> 

Obviously the work around is to refrain from using '1*' in our tables but that 
would 
be a pain. Is this an error in the stylesheets or my thinking/processing? 

Regards, 
Dean Nelson 


--------------------------------------------------------------------- 
To unsubscribe, e-mail: [email protected] 
For additional commands, e-mail: [email protected] 

Reply via email to