Hi David,
I appreciate your concerted efforts to get XEP to conform to the
specification. I can understand how hard that can be when the specification
is not clear.
As a user of multiple XSL-FO processors, it is frustrating when the
different vendors solve these grey areas in different ways. Each may be
convinced they have the right interpretation, but the results on paper can
be very different. Then we have to add messy choose statements to our
stylesheets to adjust various properties for different processors.
I'm wondering if there is a forum where XSL-FO vendors can discuss these
grey areas and try to reach a concensus on how to interpret the spec. That
forum could maybe include one or more authors of the spec if they were
willing to participate. Imagine how valuable that information would be for
the authors of the next version of spec too. Does such a forum exist? If
not, can you suggest a way of starting one? It should be hosted by a
neutral party, I would think.
Bob Stayton
Sagehill Enterprises
DocBook Consulting
bobs@sagehill.net
----- Original Message -----
From: "David Tolpin" <dvd@davidashen.net>
To: <xep-support@renderx.com>
Sent: Thursday, October 28, 2004 9:48 AM
Subject: Re: [xep-support] Table width in XEP 4
>
> Hi Jirka,
>
> I've re-read the code and notes. Here is the summary:
> I think there is a contradiction in descriptions of table models
> in XSL FO and CSS. The contradiction is resolved in the following
> way:
>
> since CSS2 describes fixed layout in terms of column widths
> and automatic layout in terms of cell widths (explicitely
> set or calculated), then XEP treats columns with explicit widths
> as in the case of fixed layout. If the determined table width
> is less than content-width, then all columns with explicitely
> specified widths are widened to fill the content-width.
>
> If, however, no column widths are specified explicitely and
> the layout is automatic (which is the default value, I was
> wrong), then the table behaves as with automatic layout, that
> is, it shrinks to the sum of column widths.
>
> The exception for width='auto' does not apply to XSL FO tables,
> just because width is a shorthand for inline-progression-dimension,
> and there is nothing about inline-progression-dimension to treat
> it differently for tables.
>
> It is easy to modify the algorithm in any way, but I need a consistent
> opinion.
>
> David
> -------------------
> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
> in the body of the message to majordomo@renderx.com from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
>
>
-------------------
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to majordomo@renderx.com from the address
you are subscribed from.
(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
Received on Thu Oct 28 13:39:20 2004
This archive was generated by hypermail 2.1.8 : Thu Oct 28 2004 - 13:39:21 PDT