A few days ago, I tried to make addParbreak() work properly when listitems have anchors in the beginning (that's why they often show breaks before their contents), but it was quite icky -- and required more extensive changes than I expected. So instead, here's what we get if we pull the anchors out of the Word list and store them separately. Less icky.
On Mon, Nov 30, 2009 at 07:29:13AM +0000, corvid wrote:
A few days ago, I tried to make addParbreak() work properly when listitems have anchors in the beginning (that's why they often show breaks before their contents), but it was quite icky -- and required more extensive changes than I expected.
So instead, here's what we get if we pull the anchors out of the Word list and store them separately. Less icky.
It looks OK to me, especially if it helps to fix the list item's extra-line-break bug, by means of code clarity. -- Cheers Jorge.-
On Mon, Nov 30, 2009 at 10:38:08AM -0300, Jorge Arellano Cid wrote:
On Mon, Nov 30, 2009 at 07:29:13AM +0000, corvid wrote:
A few days ago, I tried to make addParbreak() work properly when listitems have anchors in the beginning (that's why they often show breaks before their contents), but it was quite icky -- and required more extensive changes than I expected.
So instead, here's what we get if we pull the anchors out of the Word list and store them separately. Less icky.
It looks OK to me, especially if it helps to fix the list item's extra-line-break bug, by means of code clarity.
Looks fine to me too. Maybe you could also garbage collect core::Content::ANCHOR to avoid confusion, or is it still used? Cheers, Johannes
participants (3)
-
corvid＠lavabit.com -
jcid＠dillo.org -
Johannes.Hofmann＠gmx.de