git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Rast <trast@student.ethz.ch>
To: Jeff King <peff@peff.net>
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Thomas Rast" <trast@student.ethz.ch>,
	"Carlos Martín Nieto" <cmn@elego.de>,
	"Matthieu Moy" <Matthieu.Moy@imag.fr>,
	git@vger.kernel.org
Subject: Re: [PATCH] docs: stop using asciidoc no-inline-literal
Date: Thu, 26 Apr 2012 11:50:23 +0200	[thread overview]
Message-ID: <87sjfqn7og.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <87d36uomlq.fsf@thomas.inf.ethz.ch> (Thomas Rast's message of "Thu, 26 Apr 2012 11:42:41 +0200")

Thomas Rast <trast@inf.ethz.ch> writes:

> -``Com M Itter'') and `<email>` is the person's email address
> -(``cm@example.com'').  `LT` and `GT` are the literal less-than (\x3c)
> -and greater-than (\x3e) symbols.  These are required to delimit
> +`Com M Itter`) and `<email>` is the person's email address
> +(`cm@example.com`).  `LT` and `GT` are the literal less-than (`\x3c`)
> +and greater-than (`\x3e`) symbols.  These are required to delimit
[...]
>
> On my box (asciidoc 8.4.5) the preimage renders as
>
>   `Com M Itter''
>
> in fixed-width font.

Note that ``foo'' is the correct way to have it render “foo” (with the
smart quotes).  So it's not even a formatting error on our end, just
massive quoting rules brain damage that ruins the use of quotes here.

(I had this in the original email, but then edited it out.  Sorry for
any undue confusion caused.)

> In the process of debugging this, I noticed that
> the quoting rules are hilariously screwy.  It seems that within a
> paragraph, saying
>
>   ``foo'' means `bar`
>    ^^^^^^^^^^^^^
>
> treats the underlined part as a `-quoted chunk of text, and renders it
> appropriately using a fixed-width font.  The trailing ` has no effect
> unless it is followed by another ` within the same paragraph.  But the `
> right at the start of the "quoted" text has no effect either!  Moreover,
> this behaviour is the same regardless of the 'asciidoc7compatible'
> setting.  I wonder if it has since been fixed, but the above might be a
> good idea anyway.  (The quoting around \xAB is just for good measure.)

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2012-04-26  9:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-26  8:51 [PATCH] docs: stop using asciidoc no-inline-literal Jeff King
2012-04-26  9:03 ` Jeff King
2012-04-26  9:09 ` Matthieu Moy
2012-04-26  9:13   ` Jeff King
2012-04-26  9:42 ` Thomas Rast
2012-04-26  9:50   ` Thomas Rast [this message]
2012-04-26 12:50   ` Jeff King
2012-04-26 13:09     ` Thomas Rast

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=87sjfqn7og.fsf@thomas.inf.ethz.ch \
    --to=trast@student.ethz.ch \
    --cc=Matthieu.Moy@imag.fr \
    --cc=cmn@elego.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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).