From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: makeinfo swallows page breaks
Date: Fri, 22 Mar 2013 11:56:55 +0100 [thread overview]
Message-ID: <871ub7ln2g.fsf@gnu.org> (raw)
In-Reply-To: 87y5dflo5c.fsf@inria.fr
ludo@gnu.org (Ludovic Courtès) skribis:
> Regarding rendering: Andy noted that spaces after a sentence-ending
> periods are not preserved. I’ve investigated, but there are tests that
> assume that whitespace is collapsed, so that will require more thought.
More precisely, Texinfo says (info "(texinfo) Multiple Spaces"):
Ordinarily, TeX collapses multiple whitespace characters (space, tab,
and newline) into a single space. Info output, on the other hand,
preserves whitespace as you type it, except for changing a newline into
a space; this is why it is important to put two spaces at the end of
sentences in Texinfo documents.
So I believe that it means that stexi should preserve whitespace (which
it doesn’t currently), and that it’s the renderer’s job to trim
whitespace or not.
Tests in texinfo.test will have to be adjusted accordingly.
Currently, the parser consumes whitespace:
scheme@(guile-user)> (texi-fragment->stexi "foo. bar.")
$2 = (*fragment* (para "foo. bar."))
WDYT?
Ludo’.
next prev parent reply other threads:[~2013-03-22 10:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 23:14 makeinfo swallows page breaks Ludovic Courtès
2013-03-21 18:25 ` Ludovic Courtès
2013-03-21 18:58 ` Mike Gran
2013-03-21 20:31 ` Ludovic Courtès
2013-03-21 21:56 ` Karl Berry
2013-03-22 10:14 ` Andy Wingo
2013-03-22 10:33 ` Ludovic Courtès
2013-03-22 10:56 ` Ludovic Courtès [this message]
2013-03-22 21:42 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871ub7ln2g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
/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).