From: Jonathan Corbet <corbet@lwn.net>
To: "Nícolas F. R. A. Prado" <nfraprado@protonmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Joel Fernandes <joel@joelfernandes.org>,
Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
rcu@vger.kernel.org, alsa-devel@alsa-project.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
lkcamp@lists.libreplanetbr.org, andrealmeid@collabora.com
Subject: Re: [PATCH v2] docs: Fix reST markup when linking to sections
Date: Thu, 31 Dec 2020 15:45:19 -0700 [thread overview]
Message-ID: <20201231154519.25425c3b@lwn.net> (raw)
In-Reply-To: <20201228144537.135353-1-nfraprado@protonmail.com>
On Mon, 28 Dec 2020 14:46:07 +0000
Nícolas F. R. A. Prado <nfraprado@protonmail.com> wrote:
> During the process of converting the documentation to reST, some links
> were converted using the following wrong syntax (and sometimes using %20
> instead of spaces):
>
> `Display text <#section-name-in-html>`__
>
> This syntax isn't valid according to the docutils' spec [1], but more
> importantly, it is specific to HTML, since it uses '#' to link to an
> HTML anchor.
>
> The right syntax would instead use a docutils hyperlink reference as the
> embedded URI to point to the section [2], that is:
>
> `Display text <Section Name_>`__
>
> This syntax works in both HTML and PDF.
>
> The LaTeX toolchain doesn't mind the HTML anchor syntax when generating
> the pdf documentation (make pdfdocs), that is, the build succeeds but
> the links don't work, but that syntax causes errors when trying to build
> using the not-yet-merged rst2pdf:
>
> ValueError: format not resolved, probably missing URL scheme or undefined destination target for 'Forcing%20Quiescent%20States'
>
> So, use the correct syntax in order to have it work in all different
> output formats.
Applied, thanks.
jon
prev parent reply other threads:[~2020-12-31 22:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-28 14:46 Nícolas F. R. A. Prado
2020-12-28 20:22 ` Mauro Carvalho Chehab
2020-12-31 22:45 ` Jonathan Corbet [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=20201231154519.25425c3b@lwn.net \
--to=corbet@lwn.net \
--cc=alsa-devel@alsa-project.org \
--cc=andrealmeid@collabora.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mchehab+huawei@kernel.org \
--cc=nfraprado@protonmail.com \
--cc=perex@perex.cz \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.com \
/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
Powered by JetHome