This is the mail archive of the
docbook@lists.oasis-open.org
mailing list for the DocBook project.
Re: Changing <p>...</p> to <p> in DSSSL stylesheets
- To: docbook at lists dot oasis-open dot org
- Subject: Re: DOCBOOK: Changing <p>...</p> to <p> in DSSSL stylesheets
- From: Peter Flynn <pflynn at imbolc dot ucc dot ie>
- Date: Wed, 03 Nov 1999 15:48:27 +0000 (GMT)
- Reply-To: docbook at lists dot oasis-open dot org
> The problem is that the structure of the document cannot be represented
> in HTML. In fact the current output is erroneous as well and browsers
> almost certainly (1) imply the </p> before the <ul> and (2) ignore the
> (now erroneous) </p> after the </ul>.
Not just that, but it's misleading too :-) If I see a content model that
allows <LIST> inside <PARA> then I assume it means an inline list like
you see (a) in continuous text and (b) in the {paralist} LaTeX package.
> If I thought that preserving the original structure was of paramount
> importance, I suppose I'd do something like this, but I don't.
> The goal is reasonable looking HTML in the browser. You can, after all,
> exercise precise control if you want by tweaking your source document.
Right. When you try to pump this stuff into HTML you have to lose some
control. We tried, honest.
> | When using <p><ul>...</ul> it would be impossible to control
> | the spacing after the list with CSS1.
>
> Why couldn't I add the appropriate property to the <ul> to control
> it's space-after?
CSS is broken wrt inline lists I think.
///Peter