> -----Original Message----- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED]
Hi Jeremias, <snip /> > > [Me:] > > ... I guess you could also see it as active (collapsing) vs. passive > > (separated) border segments. In the collapsing model, the borders are > > 'alive', which seems to be exactly the part that is causing the > > headaches... > > Sort of, although I don't like the analogy with active and passive > because it introduces more terms in an already complicated environment. > I understand perfectly, but this was more meant as an analogy, to illustrate the inherent difficulty when dealing with collapsing borders... I have absolutely no intention of introducing/using these terms in the algorithm/the code (if that's what you're worried about). <snip /> > if you would like to take a stab at the collapsed border > resolution, then please do. I'll leave it aside for the moment and will > concentrate on implementing or fixing the rest of the important features > for table layout (BPD/height props, breaks, keeps, etc.). Will certainly do so. Currently, most of my time was still spent on catching up with you guys... Hopefully there will be no more unforeseen circumstances that keep me away for a few months, so I can finally get some really constructive work done on those 'ideas' of mine... <snip /> > I hope I wasn't disrespectful by snipping out and not replying to parts > of your post. Well, I wouldn't worry too much about that. I'm rather thick-skinned, if you know what I mean... And if my initial reply to the vote came across as disrespectful to you --since you obviously have invested a great deal of your time into that algorithm, and I made it seem like it wasn't worth much-- my apologies of course! Cheers, Andreas
