From: Jonathan Corbet <corbet@lwn.net>
To: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
Cc: linux-doc@vger.kernel.org, Andi Kleen <ak@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Randy Dunlap <rdunlap@infradead.org>,
"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: Mon, 24 Feb 2020 11:08:15 -0700 [thread overview]
Message-ID: <20200224110815.6f7561d1@lwn.net> (raw)
In-Reply-To: <20200223222228.27089-1-j.neuschaefer@gmx.net>
On Sun, 23 Feb 2020 23:22:27 +0100
Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
> Without double-backticks, Sphinx wrongly turns "--version" into
> "–version" with a Unicode EN DASH (U+2013), that is visually easy to
> confuse with a single ASCII dash.
>
> Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
This certainly seems worth addressing. But I would *really* rather find
a way to tell Sphinx not to do that rather than making all of these
tweaks - which we will certainly find ourselves having to do over and
over again. I can try to look into that in a bit, but if somebody were
to beat me to it ... :)
Thanks,
jon
next prev parent reply other threads:[~2020-02-24 18:08 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 [this message]
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
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=20200224110815.6f7561d1@lwn.net \
--to=corbet@lwn.net \
--cc=ak@linux.intel.com \
--cc=arnd@arndb.de \
--cc=chang.seok.bae@intel.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.