public inbox for
 help / color / mirror / Atom feed
From: Tammy Fox <>
Cc: Norman Walsh <>
Subject: Re: blank line in lists
Date: Wed, 31 Oct 2001 14:44:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Oct 31, 2001 at 06:38:00AM -0500, Norman Walsh wrote:
> / "Alan W. Irwin" <> was heard to say:
> | Is he saying in a mixed content environment (I presume lists are examples of
> | that) that no filling or justification of paragraphs is done?  That is what
> | would happen if white space were preserved.  Of course, "preserved" is a
> | stronger statement than "significant" so I guess what I really need is
> | a definition of significant.
> | 
> | Would Norm or some other expert here be willing to expand on the remark?
> "Significant" in this case means "passed through to the application". So,
> if you say:
> <para>
> Some text</para>
> What the application sees is "Begin a paragraph" "Newline" "Some text"
> "End a paragraph".
> So if the application thinks newlines are significant in paragraphs,
> you get an extra newline.
> What's really odd though is that I can't reproduce this problem
> without the intervening indexterm. And I expect the intervening
> indexterm is just a backend bug.
> (What are you generating? TeX, RTF, HTML, ... ?)

I am trying to generate PS and PDF when I see this problem. 
The HTML output looks fine because it ignores whitespace.


  parent reply	other threads:[~2001-10-31 14:44 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
2001-10-31 14:44   ` Tammy Fox [this message]
     [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).