From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: appendices/devbook-guide/
Date: Sun, 22 Jun 2025 09:29:14 +0000 (UTC) [thread overview]
Message-ID: <1750581411.18bdafb3fcd4aa22b70d3102f8e210b2d88cf22f.ulm@gentoo> (raw)
commit: 18bdafb3fcd4aa22b70d3102f8e210b2d88cf22f
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Sat Jun 21 17:32:07 2025 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Sun Jun 22 08:36:51 2025 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=18bdafb3
devbook-guide: Clarify intra-document references
Apparently, there is confusion about the syntax of intra-document
references; sometimes contributors copy the fragment identifier from
HTML output.
For now, this would produce correct links in HTML output, but it
relies on the properties of the conversion algorithm presently used
in the XSL stylesheet. However, the algorithm was adjusted at least
twice in the past (commit 1fb5bbc, commit 200818b) and may be changed
again in the future.
Therefore, clarify that the "#" separator must be followed by the
literal section title.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
appendices/devbook-guide/text.xml | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/appendices/devbook-guide/text.xml b/appendices/devbook-guide/text.xml
index e606588..81d8428 100644
--- a/appendices/devbook-guide/text.xml
+++ b/appendices/devbook-guide/text.xml
@@ -552,6 +552,12 @@ I could have written the two examples above in more compact form:
<uri link="::quickstart/#First ebuild"/>, respectively.
</p>
+<important>
+The component after the octothorpe must be the <e>literal</e> section title.
+Don't copy the fragment identifier from HTML output! So, in the above example,
+it is not <c>#first-ebuild</c> but <c>#First ebuild</c>.
+</important>
+
</body>
</subsection>
</section>
next reply other threads:[~2025-06-22 9:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-22 9:29 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-09-09 5:10 [gentoo-commits] proj/devmanual:master commit in: appendices/devbook-guide/ Ulrich Müller
2025-06-15 14:06 Sam James
2024-10-31 18:59 Ulrich Müller
2024-10-25 11:21 Ulrich Müller
2024-05-08 5:57 Ulrich Müller
2023-11-05 16:48 Ulrich Müller
2023-11-05 16:45 Ulrich Müller
2023-10-05 20:29 Ulrich Müller
2022-02-16 18:56 Ulrich Müller
2021-07-31 17:59 Ulrich Müller
2021-03-19 19:23 Ulrich Müller
2021-03-19 19:23 Ulrich Müller
2021-03-19 19:22 Ulrich Müller
2021-03-12 19:32 Ulrich Müller
2021-03-11 11:24 Ulrich Müller
2020-12-14 19:35 Ulrich Müller
2020-08-21 16:53 Ulrich Müller
2020-03-06 16:30 Ulrich Müller
2020-03-06 16:30 Ulrich Müller
2020-03-01 12:32 Ulrich Müller
2020-02-22 21:27 Ulrich Müller
2020-01-28 5:55 Ulrich Müller
2020-01-16 18:50 Ulrich Müller
2020-01-15 22:36 Ulrich Müller
2020-01-15 22:14 Ulrich Müller
2020-01-15 21:30 Ulrich Müller
2020-01-15 21:30 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
2020-01-15 21:29 Ulrich Müller
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=1750581411.18bdafb3fcd4aa22b70d3102f8e210b2d88cf22f.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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