Andreas, thank you a lot and sorry for my long silence. I had to make about
a month's break with my project of settings things up with FOP...
Your ideas really helped, and this problem has gone with the help of your
approach.
Just for me to have it finalized: is it a good idea to post this issue as a
bug, or is it already a known TODO item?
My best regards,
Sergey
----- Original Message -----
From: "Andreas L Delmelle" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, March 02, 2007 12:05 PM
Subject: Re: 0.93: problem with fo:table, width="100%" in a page header
On Mar 2, 2007, at 08:45, USHAKOV, Sergey wrote:
Hi Sergey,
I have played a little bit more after your comments, and now I am even
more
confused.
1. Removing width="100%" does not help and brings in one more problem: a
new
message appears: "INFO: table-layout="fixed" and width="auto", but
auto-layout not supported => assuming width="100%"" :)) That is close to
what I was starting with...
Oops. It seems my message was unclear: you shouldn't remove width="100%"
from the table itself, but only remove percentage-widths from the
table-cells (IF they appear there...)
Looking at the example you mailed to me off-list, it seems to be the
width="33%" specified on the fo:table-cells that's causing the message to
appear.
If possible, I'd try switching to a layout with explicit fo:table-
columns. This can be fairly simple:
<fo:table table-layout="fixed" width="100%">
<fo:table-column column-width="proportional-column-width(1)"
number-columns-repeated="3" />
<fo:table-body>
<fo:table-cell>
...
This will give you a table where each column is 1/3 of the whole
table-width, which seems to be what you are looking for.
2. Changing width="100%" to an absolute value width="180mm" does not
help
either (and the complaints are the same as for 100%), and this is
amazing...
FWIW: I'll see if I can commit a small patch containing some changes I
made locally. The big problem with tracing the origin of the error
message
"Cannot find LM to handle given FO for LengthBase"
is that no context info is displayed, so you don't really know which FO
is causing it (only that it is /a/ percentage on /a/ FO somewhere in your
document...)
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
