From: Jeff King <peff@peff.net>
To: mofaph <mofaph@gmail.com>
Cc: David Kastrup <dak@gnu.org>, git <git@vger.kernel.org>
Subject: Re: info: display '--' as '-'
Date: Tue, 7 Aug 2012 02:01:57 -0400 [thread overview]
Message-ID: <20120807060157.GA13222@sigill.intra.peff.net> (raw)
In-Reply-To: <CANes+HZ3EH70x6KiaPsV=SQpbjr5o+pEzj2+4Xx613GPZv0SLw@mail.gmail.com>
On Mon, Aug 06, 2012 at 11:08:39AM +0800, mofaph wrote:
> I am using Git 1.7.11.4 now. I compile and then install it from the repo.
>
> $ git checkout v1.7.11.4
> $ make prefix=$HOME/opt/git/1.7.11.4 all doc info
> $ make prefix=$HOME/opt/git/1.7.11.4 install{,-doc,-html,-info}
>
> Recently, I found some problem when I read the git.info.
>
> For example, you can see it in "3.7.1 Getting conflict-resolution help during a
> merge":
>
> $ git log -merge
> $ gitk -merge
>
> See, it should be type like this:
>
> $ git log --merge
> $ gitk --merge
>
> You will see this typo almost in the whole info file.
Yeah, I can reproduce it here. The data goes through these
transformations to get to the final info form:
user-manual.txt (source)
-> user-manual.xml (via asciidoc)
-> user-manual.texi (via docbook2x-texi)
-> git.info (via makeinfo)
The data looks OK in user-manual.texi, but "--" is converted to "-" in
git.info. So either:
1. There is a bug in makeinfo, which should not be doing this
conversion inside a "@display" section.
2. There is a bug in docbook2x-texi, which should be quoting the
contents of the <literallayout> when generating the @display
section.
I don't know enough about texinfo to say which. But I'm sure that the
contents of user-manual.xml are correct, because I do actually speak
docbook, which means the problem happens after that step.
Cc-ing David Kastrup, who added the info version originally, and might
be more clueful about that part of the toolchain.
-Peff
next prev parent reply other threads:[~2012-08-07 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-06 3:08 info: display '--' as '-' mofaph
2012-08-07 6:01 ` Jeff King [this message]
2012-08-07 7:17 ` David Kastrup
2012-08-07 19:42 ` Jeff King
2012-08-07 20:07 ` [PATCH] docs: monospace listings in docbook output Jeff King
2012-08-07 8:29 ` info: display '--' as '-' Andreas Schwab
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=20120807060157.GA13222@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=mofaph@gmail.com \
/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 NNTP newsgroup(s).