From: Remi Andruccioli <remi.andruccioli@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: cdrom: Fix a typo and rst markup
Date: Thu, 13 Aug 2020 00:13:33 +0200 [thread overview]
Message-ID: <88e58f2a-c829-8572-a858-e73cdfe41027@gmail.com> (raw)
In-Reply-To: <20200811104432.0fbe21db@lwn.net>
On Tue, 11 Aug 2020 18:44:32 +0200, Jonathan Corbet <corbet@lwn.net> wrote:
> On Sat, 8 Aug 2020 18:31:23 +0200
> Remi Andruccioli <remi.andruccioli@gmail.com> wrote:
>
>> "The capability fags" should be "The capability flags".
>>
>> In rst markup, a incorrect markup expression is causing bad rendering in
>> Sphinx output. Replace the erroneous single quote by a backquote.
>>
>> Signed-off-by: Remi Andruccioli <remi.andruccioli@gmail.com>
>> ---
>> Documentation/cdrom/cdrom-standard.rst | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> I've applied this, thanks.
Thanks to you Jonathan.
>
> The backtick replacement makes the warning go away, but a better fix would
> be to remove the backticks entirely; I'm not sure why they are used as
> quotes in that file.
Yes, I agree with you. Actually I did it that way to stay consistent with the
rest of the file although I noticed something was wrong with the rst markup.
After investigating today, this file comes from an old LaTeX file that later
was converted to rst with some tool. That tool replaced different LaTeX
commands from the original tex file by backticks (minus the one from my fix).
After recovering the original tex file and compiling it I could figure out
what was wrong and see the original intention of the authors in the LaTeX
compiled result: some words/expressions appear 'quoted' while filenames are
rendered in a mono font.
So even the current Sphinx output is wrong since the conversion of this
file, as everything gets currently rendered in italics.
Last version of the tex file can be recovered at:
b693d0b372afb39432e1c49ad7b3454855bc6bed
Conversion to rst was done in:
e327cfcb25422c91f4bb8e8a3488386ac95955f1
I'll see what I can do to replace all those backticks by the proper rst
markup according to the original tex file.
>
> jon
>
Yours,
Remi Andruccioli
prev parent reply other threads:[~2020-08-12 22:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-08 16:31 [PATCH] docs: cdrom: Fix a typo and rst markup Remi Andruccioli
2020-08-11 16:44 ` Jonathan Corbet
2020-08-12 22:13 ` Remi Andruccioli [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=88e58f2a-c829-8572-a858-e73cdfe41027@gmail.com \
--to=remi.andruccioli@gmail.com \
--cc=axboe@kernel.dk \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@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.
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).