From: Jani Nikula <jani.nikula@linux.intel.com>
To: Matthew Wilcox <willy@infradead.org>,
Randy Dunlap <rdunlap@infradead.org>
Cc: "Jonathan Corbet" <corbet@lwn.net>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
linux-doc@vger.kernel.org, "Andi Kleen" <ak@linux.intel.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Chang S. Bae" <chang.seok.bae@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: process: changes.rst: Escape --version to fix Sphinx output
Date: Tue, 25 Feb 2020 11:15:51 +0200 [thread overview]
Message-ID: <87v9nvrprs.fsf@intel.com> (raw)
In-Reply-To: <20200224211044.GQ24185@bombadil.infradead.org>
On Mon, 24 Feb 2020, Matthew Wilcox <willy@infradead.org> wrote:
> On Mon, Feb 24, 2020 at 01:08:13PM -0800, Randy Dunlap wrote:
>> Not trying to be contrary, but I would prefer to keep .rst files as much
>> ASCII as possible.
>
> I don't think anybody is arguing otherwise. The question is whether
> minusminus should be left as a pair of minus signs or whether it should
> be converted into an en-dash.
FWIW I think a pair of minus signs is never completely wrong in the
output (even when the semantics is en-dash and the conversion is
desirable) but occasionally converting a pair of minus signs to en-dash
is incorrect. Thus retaining the "smart" conversion requires we use some
form of escaping when we don't want double minus to be converted to
en-dash. I'd lean towards "smartquotes = False".
It'll still possible to add Unicode en-dash directly in the .rst if
people really want that.
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
prev parent reply other threads:[~2020-02-25 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-23 22:22 [PATCH] docs: process: changes.rst: Escape --version to fix Sphinx output Jonathan Neuschäfer
2020-02-24 18:08 ` Jonathan Corbet
2020-02-24 18:47 ` Jonathan Neuschäfer
2020-02-24 18:52 ` Matthew Wilcox
2020-02-24 18:58 ` Jonathan Corbet
2020-02-24 19:12 ` Matthew Wilcox
2020-02-24 21:08 ` Randy Dunlap
2020-02-24 21:10 ` Matthew Wilcox
2020-02-25 9:15 ` Jani Nikula [this message]
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=87v9nvrprs.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=ak@linux.intel.com \
--cc=arnd@arndb.de \
--cc=chang.seok.bae@intel.com \
--cc=corbet@lwn.net \
--cc=darrick.wong@oracle.com \
--cc=j.neuschaefer@gmx.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=willy@infradead.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 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).