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: Wed, 15 Jan 2020 21:30:00 +0000 (UTC) [thread overview]
Message-ID: <1579123728.e01f0401b79a3de5a0bb29e98918ee72cef249c7.ulm@gentoo> (raw)
commit: e01f0401b79a3de5a0bb29e98918ee72cef249c7
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Wed Jan 15 21:25:12 2020 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Jan 15 21:28:48 2020 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e01f0401
devbook-guide: Update "Internal Coding Style" section.
Describe only the tags that are actually used in DevBook XML.
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
appendices/devbook-guide/text.xml | 21 +++++++++++----------
1 file changed, 11 insertions(+), 10 deletions(-)
diff --git a/appendices/devbook-guide/text.xml b/appendices/devbook-guide/text.xml
index 35ecace..b14a2a7 100644
--- a/appendices/devbook-guide/text.xml
+++ b/appendices/devbook-guide/text.xml
@@ -546,11 +546,11 @@ Both sections are described next.
<p>
<b>Newlines</b> must be placed immediately after <e>every</e> DevBook XML tag
(both opening as closing), except for:
-<c><version></c>, <c><date></c>, <c><title></c>,
-<c><th></c>, <c><ti></c>,
-<c><li></c>, <c><i></c>, <c><e></c>,
-<c><uri></c>, <c><path></c>, <c><b></c>, <c><c></c>,
-<c><mail></c>.
+<c><title></c>,
+<c><th></c>, <c><ti></c>, <c><li></c>,
+<c><dt></c>, <c><dd></c>,
+<c><b></c>, <c><c></c>, <c><e></c>, <c><d/></c>,
+<c><uri></c>.
</p>
<p>
@@ -564,11 +564,12 @@ Both sections are described next.
<p>
<b>Word-wrapping</b> must be applied at 80 characters except inside
-<c><pre></c>. You may only deviate from this rule when there is no other
-choice (for instance when a URL exceeds the maximum amount of characters). The
-editor must then wrap whenever the first whitespace occurs. You should try to
-keep the <e>rendered</e> content of <c><pre></c> elements within 80
-columns to help console users.
+<c><pre></c> and <c><codesample></c>. You may only deviate from
+this rule when there is no other choice (for instance when a URL exceeds the
+maximum amount of characters). The editor must then wrap whenever the first
+whitespace occurs. You should try to keep the <e>rendered</e> content of
+<c><pre></c> and <c><codesample></c> elements within 80 columns
+to help console users.
</p>
<p>
next reply other threads:[~2020-01-15 21:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 21:30 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-31 18:59 [gentoo-commits] proj/devmanual:master commit in: appendices/devbook-guide/ 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: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=1579123728.e01f0401b79a3de5a0bb29e98918ee72cef249c7.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