Hi,
I noticed the same thing - that the auto-adjusting-table-column-width feature
in XEP stopped working when I tested to upgrade to 1.76.something.
IIRC, it had to do with how the colwidth attribute is handled: in 1.76 and
later, if colwidth isn’t set for a column, it is automatically assumed that
”1*” should be used, whereas in earlier versions no column width at all is
specified in the FO.
I wrote a customization that re-enabled XEP’s auto-column-width feature that we
ended up never using since we didn't migrate from 1.75 (if it’s not broken…).
But I think I may be able to dig it up again, if anyone should be interested.
Best Regards
/Ola
---
Ola Widin
Kanin Design Information Interaktion
Phone: +46 (0) 709-37 86 10
E-mail: o...@kanindesign.se
Web: www.kanindesign.se
27 apr 2015 kl. 23:43 skrev Jan Tosovsky j.tosov...@email.cz:
Dear All,
I've migrated some old customization layer and found it behaves differently
for certain tables.
When no colwidths are specified, I expect all columns occupy just required
width (as in case of HTML tables). But in 1.78.1 such a table is stretched
to the all available width and columns are distributed evenly (XEP). It
looks ugly especially if you have few narrow columns.
Using a diff tool I found it is caused by removing the condition mentioned
in this thread:
https://lists.oasis-open.org/archives/docbook-apps/201005/msg00061.html
I fixed it (inserted that condition back) in my customization layer, it work
as expected, but it would be nice to fix/improve the trunk code as well.
Or is it rather XEP bug which doesn't follow specification and renders
tables incorrectly?
Thanks, Jan
winmail.dat
-
To unsubscribe, e-mail: docbook-apps-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: docbook-apps-h...@lists.oasis-open.org
