From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: "GitList" <git@vger.kernel.org>
Subject: Re: [PATCH] doc: fix 'git status --help' character quoting
Date: Mon, 20 Oct 2014 10:14:31 -0700 [thread overview]
Message-ID: <xmqqy4sa3bpk.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <8D139BC1FB1E4335B4375FB0F056BB0B@PhilipOakley> (Philip Oakley's message of "Mon, 20 Oct 2014 11:46:30 +0100")
"Philip Oakley" <philipoakley@iee.org> writes:
> From: "Junio C Hamano" <gitster@pobox.com>
>> Philip Oakley <philipoakley@iee.org> writes:
>>
>>> Correct backtick quoting for some of the modification states to give
>>> consistent web rendering.
>>
>> This is to match the way how "XY PATH1 -> PATH2" is typeset, I
>> presume. Some in the body text are already `XY` to match, but some
>> others are not,
>> and you are fixing them, all of which look good.
>
> Do you need me to add this to the commit message?
Nah, it already mentions "consistent"; I was just double checking
that I correctly understod consistency with what part of existing
doc is achieved with the patch.
> The reason I proposed the change is because on the web view, on my
> machine, I questioned whether the specially formatted character
> (remember its quotation is consumed by ascidoc) looked too much like
> an Oh, so I specially checked on the original .txt to see if it was
> correct there, which led me to the proposal for '00' in this case.
>
> I'd be just as happy with a single zero, as long as it's distinct from
> O (as you probably know, in the depths of hsitory typewriters didn't
> even have 0 and 1 keys - the O and l were used interchangably and many
> fonts keep too much to that pattern of undifferetiability!)
Yes, and that is why I said
>> there is
>> no risk for anybody to mistake "O" (oh) as part of digits, whether
>> you use decimal or hexadecimal.
;-)
> Note the more recent http://git-scm.com/docs/git-status has the
> formatted round o and
I think it is just the font. I just opened the above page with
Chrome and futzed the text from '0' to '0123456789' to see how it
look. That round thing is consistent with how other digits are
rendered.
https://plus.google.com/u/0/+JunioCHamano/posts/dzNXV2FwP6K
(sorry for a URL to plus)
> https://www.kernel.org/pub/software/scm/git/docs/git-status.html
> (which IIUC is out of date) has an unformatted 0.
next prev parent reply other threads:[~2014-10-20 17:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-19 14:17 [PATCH] doc: fix 'git status --help' character quoting Philip Oakley
2014-10-19 22:26 ` Junio C Hamano
2014-10-20 10:46 ` Philip Oakley
2014-10-20 11:31 ` Philip Oakley
2014-10-20 17:14 ` Junio C Hamano [this message]
2014-10-20 19:28 ` Philip Oakley
2014-10-20 19:54 ` Junio C Hamano
2014-10-20 20:02 ` Junio C Hamano
2014-10-21 22:08 ` Philip Oakley
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=xmqqy4sa3bpk.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.