Hmm, you're right. That should make things easier.
BTW, I've got the raw algorithm together now to handle borders and
tables and footers. Now I only have to deal with a few deals (mostly
border stuff). After that I'm happy to call a vote for merging the
branch back into HEAD.
On 09.05.2005 10:44:
Jeremias Maerki wrote:
> So far I can only see the brute-force method (discarding element
> lists after the break and somehow backtrack while cleverly optimizing so
> as not to create too many discarded objects - still a non-trivial thing
> over all).
Andrea's idea of "recycling" elements instead
On 04.05.2005 22:16:40 Jeremias Maerki wrote:
> > IIUC, this borderline case would result in the entire table basically being
> > one row-group (? In every row there is always one cell spanning from the
> > previous row as well as another cell spanning to the next)
>
> Yes. Funny example to run t
On 04.05.2005 21:09:00 Andreas L. Delmelle wrote:
> > -Original Message-
> > From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
> >
> > On 27.04.2005 18:28:55 Andreas L. Delmelle wrote:
> >
> > > BTW: Does this problem pose itself only if a single cell
> > > or row spans more than two pages,
> -Original Message-
> From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
>
> On 27.04.2005 18:28:55 Andreas L. Delmelle wrote:
>
> > BTW: Does this problem pose itself only if a single cell
> > or row spans more than two pages, or also when an entire
> > row-group does so?
>
> Possibly, yes.
Just found this unanswered. Sorry.
On 27.04.2005 18:28:55 Andreas L. Delmelle wrote:
> > > I've already documented a known problem [5] (at
> > > the bottom). I just hope it won't bite us later on.
> > >
> > > [5]
> > http://wiki.apache.org/xmlgraphics-fop/TableLayout/KnuthElementsForTables
> >
>
> -Original Message-
> From: Luca Furini [mailto:[EMAIL PROTECTED]
>
> > Jeremias Maerki wrote:
>
> > I'm a bit concerned about the increasing complexity of this. It takes
> > considerable time just to understand and play through all these examples
> > and after that implementing it so that
On 26.04.2005 18:44:38 Luca Furini wrote:
> > I've already documented a known problem [5] (at
> > the bottom). I just hope it won't bite us later on.
> >
> > [5]
> > http://wiki.apache.org/xmlgraphics-fop/TableLayout/KnuthElementsForTables
>
> I don't think it is a dangerous problem: it can be r
Jeremias Maerki wrote:
> I'm a bit concerned about the increasing complexity of this. It takes
> considerable time just to understand and play through all these examples
> and after that implementing it so that the code is still readable. Of
> course, we documented our findings pretty well, althou
My latest example is now fully explored and seems to work. It took me
almost all day, but at least I got some valuable insight for the
extended algorithm I need to write as the next step. I hope we now have
everything together and I don't get any surprises.
http://wiki.apache.org/xmlgraphics-fop/T
I've just updated [1] with all break possibilities for the third example
[2] I mentioned in an earlier post [3].
[1] http://people.apache.org/~jeremias/fop/KnuthBoxesForTablesWithBorders.pdf
[2] http://people.apache.org/~jeremias/fop/table-border-special1.fo
[3]
http://mail-archives.apache.org/mo
11 matches
Mail list logo
