public inbox for
 help / color / mirror / Atom feed
From: Norman Walsh <>
To: "Alan W. Irwin" <>
Subject: Re: blank line in lists
Date: Wed, 31 Oct 2001 07:28:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <Pine.LNX.4.40.0110310634160.23002-100000@starling.mylan.home>

/ "Alan W. Irwin" <> was heard to say:
| Let's concentrate on the jade html backend although I suspect the problem
| occurs for all jade backends.  To verify the problem I suggest you try jade
| with html output, and you should see that propagated nl *looking directly at
| the raw html file result* at the start of paragraphs in mixed environments
| like lists.

Yes, I know what the markup looks like, but...

| because the browser interpretation of that leading nl in the HTML varies
| between browsers. As I recall mozilla ignored it while netscape 4.7 and
| konqueror paid attention to it leading to the problem that the original
| poster was discussing.

Netscape 6.2 seems to ignore the leading whitespace, which I think is the
correct behavior for HTML.

| Concentrating on the html here, if the html standards say leading nl's in
| paragraphs are valid in the context of lists or other mixed environments
| then it is up to the individual browser to ignore them, and obviously the
| problem is not jade's fault.

That, I believe, is the case.

| However, if the html standards say leading
| nl's for paragraphs within lists are invalid, then this is jade's problem
| which should be fixed.  In case of doubt about the html standards, I
| understand there are validators which should make it easy to tell whether
| the jade html output is valid for the leading nl situation we have been
| discussing.

There's no question of validity or not, a newline can occur anywhere
in a <p>.  But what the browsers are supposed to do may be an open

There are a class of problems that arise because things are allowed in
DocBook that are not allowed in HTML (lists inside paragraphs for
one). They are not easy to fix in Jade. In practice, I generally heave my
generated HTML through tidy. It's a hack, but it usually helps. Except where
tidy %@%!W@$@#s up, of course :-(

                                        Be seeing you,

Norman Walsh <> | In the life of saints, technically so            | called, the spiritual facilities are
                              | strong, but what gives the impression
                              | of extravagance proves usually on
                              | examination to be a relative deficiency
                              | of intellect.--William James

  reply	other threads:[~2001-10-31  7:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.40.0110261601400.28945-100000@starling.mylan.home>
2001-10-31  3:38 ` Norman Walsh
2001-10-31  7:19   ` Alan W. Irwin
2001-10-31  7:28     ` Norman Walsh [this message]
2001-10-31 14:44   ` Tammy Fox
     [not found] <Pine.LNX.4.40.0110261442550.28945-100000@starling.mylan.home>
     [not found] ` <1004124386.2147.279.camel@peecee>
2001-10-31  2:57   ` Norman Walsh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).