From: Norman Walsh <ndw@nwalsh.com>
To: "Alan W. Irwin" <irwin@beluga.phys.uvic.ca>
Cc: docbook-tools-discuss@sourceware.cygnus.com
Subject: Re: blank line in lists
Date: Wed, 31 Oct 2001 03:38:00 -0000 [thread overview]
Message-ID: <877ktcjazr.fsf@nwalsh.com> (raw)
In-Reply-To: <Pine.LNX.4.40.0110261601400.28945-100000@starling.mylan.home>
/ "Alan W. Irwin" <irwin@beluga.phys.uvic.ca> 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, ... ?)
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | "Abstraction, abstraction and
http://nwalsh.com/ | abstraction." This is the answer to the
| question, "What are the three most
| important words in programming?"--Paul
| Hudak
next parent reply other threads:[~2001-10-31 3:38 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 [this message]
2001-10-31 7:19 ` Alan W. Irwin
2001-10-31 7:28 ` Norman Walsh
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877ktcjazr.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
--cc=docbook-tools-discuss@sourceware.cygnus.com \
--cc=irwin@beluga.phys.uvic.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).