From: Anders Kaseorg <andersk@MIT.EDU>
To: Junio C Hamano <gitster@pobox.com>
Cc: Miklos Vajna <vmiklos@frugalware.org>,
Thomas Rast <trast@student.ethz.ch>,
git@vger.kernel.org, bill lam <cbill.lam@gmail.com>
Subject: Re: [PATCH] Document GNU_ROFF in Makefile
Date: Wed, 21 Oct 2009 18:51:33 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0910211824220.5105@dr-wily.mit.edu> (raw)
In-Reply-To: <7vk4yoz8sf.fsf@alter.siamese.dyndns.org>
On Wed, 21 Oct 2009, Junio C Hamano wrote:
> > +# Define GNU_ROFF if you have GNU roff and you don't want to have pretty
> > +# apostrophe so that cut&pasting examples to the shell will work.
>
> This makes it sound as if groff is the only roff implementation that has
> this problem---iow, if we use non-GNU roff then the documentation comes
> out just fine. Is that the case?
Yes:
built without GNU_ROFF built with GNU_ROFF
viewed with non-GNU roff correct (') wrong (no output!)
viewed with GNU groff wrong (´) correct (')
In order to build a manpage that can be viewed correctly on both
platforms, the conditional logic should live in the manpage itself (as per
the bug comments I linked to and Thomas quoted from).
Anders
next prev parent reply other threads:[~2009-10-21 22:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 10:29 quote in help code example bill lam
2009-10-12 19:40 ` Miklos Vajna
2009-10-13 2:16 ` bill lam
2009-10-13 10:19 ` Miklos Vajna
2009-10-13 14:06 ` bill lam
2009-10-13 15:30 ` Miklos Vajna
2009-10-13 20:15 ` Thomas Rast
2009-10-15 12:02 ` Thomas Rast
2009-10-21 8:24 ` [PATCH] Quote ' as \(aq in manpages Thomas Rast
2009-10-21 10:38 ` Miklos Vajna
2009-10-21 18:01 ` Anders Kaseorg
2009-10-21 18:57 ` [PATCH v2] " Thomas Rast
2009-10-21 21:31 ` [PATCH] Document GNU_ROFF in Makefile Miklos Vajna
2009-10-21 22:22 ` Junio C Hamano
2009-10-21 22:51 ` Anders Kaseorg [this message]
2009-10-22 8:19 ` [PATCH v3] Quote ' as \(aq in manpages Thomas Rast
2009-10-21 21:42 ` [PATCH v2] " Anders Kaseorg
2009-10-12 21:06 ` quote in help code example Junio C Hamano
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=alpine.DEB.2.00.0910211824220.5105@dr-wily.mit.edu \
--to=andersk@mit.edu \
--cc=cbill.lam@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=trast@student.ethz.ch \
--cc=vmiklos@frugalware.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 NNTP newsgroup(s).