[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87v9nvrprs.fsf@intel.com>
Date: Tue, 25 Feb 2020 11:15:51 +0200
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Matthew Wilcox <willy@...radead.org>,
Randy Dunlap <rdunlap@...radead.org>
Cc: Jonathan Corbet <corbet@....net>,
Jonathan Neuschäfer <j.neuschaefer@....net>,
linux-doc@...r.kernel.org, Andi Kleen <ak@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
"Darrick J. Wong" <darrick.wong@...cle.com>,
Arnd Bergmann <arnd@...db.de>,
"Chang S. Bae" <chang.seok.bae@...el.com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: process: changes.rst: Escape --version to fix Sphinx output
On Mon, 24 Feb 2020, Matthew Wilcox <willy@...radead.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
Powered by blists - more mailing lists