On Feb 28, 2006, at 14:48, Glen Mazza wrote:
[EMAIL PROTECTED] wrote:
10:01:48,302 WARN [FONode] Warning(Unknown location): fo:table-
column, In the separate border model (border-collapse="separate"),
borders cannot be specified on a fo:table-column, but a non-zero
value for border was found. The border will be ignored.
I don't like this phrasing. One can place (specify) any property
on any FO. (See first sentence of Chapter 5.[1]) I wonder if the
FOP developer who did this is mistaking FO Tree properties (where
the users can set whatever properties they want) with area traits
(in which certain traits will indeed be ignored or set to zero, as
per the spec.)
FYI: Agreed, and has already been modified in FOP Trunk. Nils Meier
recently raised an issue on fop-dev which made me revise this.
Currently, it is phrased as follows
"In the separate border model, borders are not applicable to fo:table-
column, but a non-zero value for border was found."
It's more meant as a reminder to people that, unless they're using
border="from-table-column()" on their fo:table-cells, those borders
will have no effect whatsoever, so the solution is: remove all border-
specs from the columns, and the warning will go away... unless, they
*are* using them as described, of course.
Hmm, if the user specified those borders, he/she would expect them to
have some effect on the ouput (?)
Maybe this warning should just be removed altogether?
Anyone?
Cheers,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
