From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: makeinfo swallows page breaks
Date: Fri, 22 Mar 2013 11:33:35 +0100 [thread overview]
Message-ID: <87y5dflo5c.fsf@inria.fr> (raw)
In-Reply-To: 87boacboeg.fsf@gnu.org
ludo@gnu.org (Ludovic Courtès) skribis:
> Attached is a patch to use Guile’s Texinfo support [0] to build said
> file. Guile’s Texinfo parser is incomplete but sufficient to handle
> those docstrings.
I went ahead and pushed this after discussion with Mark and Andy on IRC.
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.
Ludo’.
next prev parent reply other threads:[~2013-03-22 10:33 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 [this message]
2013-03-22 10:56 ` Ludovic Courtès
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=87y5dflo5c.fsf@inria.fr \
--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).