Re: Collapsing borders: FOTree stage -- progress update

2005-08-28 Thread Manuel Mall
On Sun, 28 Aug 2005 10:33 am, Manuel Mall wrote: On Sat, 27 Aug 2005 02:07 am, Andreas L Delmelle wrote: Hi all, snip/ * The first step I took was moving much of the logic that is currently in CollapsingBorderModelEyeCatching (in the layout package) to CommonBorderPaddingBackground.

Re: Collapsing borders: FOTree stage -- progress update

2005-08-28 Thread Andreas L Delmelle
On Aug 28, 2005, at 04:33, Manuel Mall wrote: I must admit I know very little about collapsing borders. Therefore if my comment is useless just ignore it. Well, I certainly don't think it's useless... I have recently worked on all this percentage stuff. This applies also to border-width

Re: Collapsing borders: FOTree stage -- progress update

2005-08-28 Thread Andreas L Delmelle
On Aug 28, 2005, at 14:38, Andreas L Delmelle wrote: On Aug 28, 2005, at 00:06, Jeremias Maerki wrote: AFAIK you're trying to move the pre-resolvable pieces into the FO tree while you only do the specialities in the LMs, right? Exactly. Come to think of it, maybe that last idea won't be

Re: Automatic column widths in fop

2005-08-28 Thread Andreas L Delmelle
On Aug 28, 2005, at 15:57, Manuel Mall wrote: This is just a clarification question to those in the know. In HTML when specifying a table browsers usually choose the smallest width without causing unforced breaks in columns. That is in XSL-FO terms the ipd of the table can be smaller than the

Re: FOP website, release preparations: refactoring necessary

2005-08-28 Thread J.Pietschmann
Jeremias Maerki wrote: (It's probably best to collapse Development and Design into one tab. Too many tabs are not ideal. I second that. J.Pietschmann

Bug report for Fop [2005/08/28]

2005-08-28 Thread bugzilla
+---+ | Bugzilla Bug ID | | +-+ | | Status: UNC=Unconfirmed NEW=New ASS=Assigned

Re: Automatic column widths in fop

2005-08-28 Thread Andreas L Delmelle
On Aug 28, 2005, at 16:21, Manuel Mall wrote: [Me:] We could either: - drop the table completely (+ warn about this, of course) - explicitly notify the user that, because auto-layout is not supported, the default value of auto is ignored and replaced by 100% I second that for the time being.