This is the mail archive of the
docbook-apps@lists.oasis-open.org
mailing list .
Re: Avoiding extra linebreaks in <li> items in Oper a
- From: Norman Walsh <ndw at nwalsh dot com>
- To: "Bang, Steinar" <Steinar dot bang at tandbergtv dot com>
- Cc: "'docbook-apps at lists dot oasis-open dot org'" <docbook-apps at lists dot oasis-open dot org>
- Date: Sat, 15 Dec 2001 09:00:20 -0500
- Subject: DOCBOOK-APPS: Re: Avoiding extra linebreaks in <li> items in Oper a
- References: <194F8BB4FDB2D311B4010008C733C774017E59B2@no-mail.oslo.tandbergtv.lan>
/ "Bang, Steinar" <Steinar.bang@tandbergtv.com> was heard to say:
| IMO one should always restrict generated HTML to the subset of the
| standard, that works correctly on the greatest number of browsers.
As time passes, I find that I'm becoming less and less tolerant of
browsers that don't properly implement standards. OTOH, as I posted,
Opera behavior in this case might be "correct".
| I haven't looked into what the example does yet, but if what it does
| is to remove the first <p></p> from one or more <para> elements
| in a <listitem>, I don't see anywhere a browser would break, and
| it would fix two cases (Opera, and the HTML to text converters
| the first person in the thread was talking about).
It's easy to fix for the first para in a listitem, but the first
element in a list item can be abstract, address, anchor, authorblurb,
beginpage, blockquote, bridgehead, calloutlist, caution,
classsynopsis, cmdsynopsis, constraintdef, constructorsynopsis,
destructorsynopsis, epigraph, equation, example, fieldsynopsis,
figure, formalpara, funcsynopsis, glosslist, graphic, graphicco,
highlights, important, indexterm, informalequation, informalexample,
informalfigure, informaltable, itemizedlist, literallayout,
mediaobject, mediaobjectco, methodsynopsis, msgset, note, orderedlist,
para, procedure, productionset, programlisting, programlistingco,
qandaset, remark, screen, screenco, screenshot, segmentedlist,
sidebar, simpara, simplelist, synopsis, table, tip, variablelist, or
warning. You want me to special case them all? That'd be deeply
intrusive. And even if that was desired, how would you propose to
speical case something like <screen> where the <pre> is surely
necessary.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | The best people usually owe their
http://www.oasis-open.org/docbook/ | excellence to a combination of
Chair, DocBook Technical Committee | qualities which might have been
| supposed incompatible.--Bertrand
| Russell