git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Jeff King <peff@peff.net>
To: Fabrizio Cucci <fabrizio.cucci@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Back quote typo in error messages (?)
Date: Wed, 15 Feb 2017 16:56:34 -0500	[thread overview]
Message-ID: <20170215215633.deyxp76j7o3ceoq3@sigill.intra.peff.net> (raw)
In-Reply-To: <CAOxYW4xqk4j6Uu86jq2Vi9Bpgihxfr2Tw-DQLc+7YTZiPmDtiA@mail.gmail.com>

On Wed, Feb 15, 2017 at 09:51:30PM +0000, Fabrizio Cucci wrote:

> > Some people use the matched backtick/single-quote to emulate the
> > non-symmetric start/end quotes used in traditional typography (and in
> > fact, ``foo'' in languages like asciidoc are typically rendered using
> > smart-quotes).
> 
> I definitely didn't know about the use of them in traditional typography!
> But I couldn't find any example of non-symmetric quotes in AsciiDoc...

Grep for "``" in Git's documentation directory, and you will see many
examples (asciidoc only accepts the double-quote form, not singles).

You can also try:

  echo "this is \`\`quoted'' text" >foo.txt
  asciidoc foo.txt

and then open "foo.html" in your browser.

> > I don't know how much we care about standardizing that punctuation.
> 
> I mentioned it was very minor but, still, in my opinion a project like
> Git deserves consistent punctuation! :)

I think patches would be welcome, but as Junio said, it probably should
wait for the next cycle.

-Peff

  reply	other threads:[~2017-02-15 21:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15 21:06 Back quote typo in error messages (?) Fabrizio Cucci
2017-02-15 21:21 ` Jeff King
2017-02-15 21:31   ` Junio C Hamano
2017-02-15 21:51   ` Fabrizio Cucci
2017-02-15 21:56     ` Jeff King [this message]
2017-02-16 18:41       ` Fabrizio Cucci
2017-02-16 19:02         ` Jeff King
2017-02-16 20:58           ` Fabrizio Cucci

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170215215633.deyxp76j7o3ceoq3@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=fabrizio.cucci@gmail.com \
    --cc=git@vger.kernel.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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).