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 13:02:42 -0700 [thread overview]
Message-ID: <xmqqy4sa1pct.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqq38ai34bh.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 20 Oct 2014 12:54:10 -0700")
Junio C Hamano <gitster@pobox•com> writes:
> "Philip Oakley" <philipoakley@iee•org> writes:
>
>> From: "Junio C Hamano" <gitster@pobox•com>
>> ...
>>> 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.
>>> --
>>
>> I've just had a look at how it formats when the zero is back-tick
>> quoted s /ASCII 0/ASCII `0`/ and it looks OK with both Chromium and
>> Firefox on my hack Ubuntu laptop - the character is colourised and
>> full sized, and the --man page output looks unchanged and clearly a
>> zero.
>>
>> my hacky attempt at an in-line patch (squash in?) below:
>
> You'd need a matching change to 34 in the same document to preserve
> the consistency the original patch sought, though ;-)
Not that I think such a change makes much sense.
If there was a way to force use of a font whose numerals and I/O are
more clearly distinguishable and we do so for all HTML documents we
generate, that would be a good change that is not limited to these
places, though.
next prev parent reply other threads:[~2014-10-20 20:03 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
2014-10-20 19:28 ` Philip Oakley
2014-10-20 19:54 ` Junio C Hamano
2014-10-20 20:02 ` Junio C Hamano [this message]
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=xmqqy4sa1pct.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=philipoakley@iee$(echo .)org \
/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