From: Michael J Gruber <git@drmicha•warpmail.net>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org, Junio C Hamano <gitster@pobox•com>
Subject: Re: [PATCH] git-rm.txt: Fix quoting
Date: Wed, 08 Dec 2010 09:08:02 +0100 [thread overview]
Message-ID: <4CFF3CE2.9040908@drmicha.warpmail.net> (raw)
In-Reply-To: <20101207164315.GA21749@sigill.intra.peff.net>
Jeff King venit, vidit, dixit 07.12.2010 17:43:
> On Tue, Dec 07, 2010 at 10:07:11AM +0100, Michael J Gruber wrote:
>
>> Literal " produces typographically incorrect quotations, but "works" in
>> most circumstances. In the subheadings of git-rm.txt, it "works" for the
>> html backend but not for the docbook conversion to nroff: double "" and
>> spurious double spaces appear in the output.
>>
>> Replace "incorrect" quotations by ``correct'' ones, and fix other
>> "quotations" which are really `code fragments`.
>>
>> This should make git-rm.txt "-clean.
>
> Thanks, this is a much better solution than what I posted earlier.
>
> Acked-by: Jeff King <peff@peff•net>
>
>> We still have a lingering inconsistency for denoting code fragments.
>> Single backticks merely are a literal monospaced environment; html outputcolors
>> this, nroff does not indicate it at all. I'm staying consistent with the
>> surrounding text here.
>
> Try setting MAN_BOLD_LITERAL in your config.mak.
Always learning something new about our doc tooclchain... and what a
great name for an option! Although it should be "Man, bold, literally!".
Michael
next prev parent reply other threads:[~2010-12-08 8:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-07 5:07 [BUG] yet another doc formatting problem Jeff King
2010-12-07 8:42 ` Michael J Gruber
2010-12-07 9:07 ` [PATCH] git-rm.txt: Fix quoting Michael J Gruber
2010-12-07 16:43 ` Jeff King
2010-12-08 8:08 ` Michael J Gruber [this message]
2010-12-07 17:19 ` Jonathan Nieder
2010-12-07 17:25 ` Jeff King
2010-12-08 11:15 ` [PATCHv2] " Michael J Gruber
2010-12-07 19:12 ` [PATCH] " 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=4CFF3CE2.9040908@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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