From: Jon Turney <jon.turney@dronecode.org.uk>
To: newlib@sourceware.org
Cc: Jon Turney <jon.turney@dronecode.org.uk>
Subject: [PATCH 4/5] Fix warning about duplicate id in docbook XML
Date: Mon, 2 May 2022 13:55:16 +0100 [thread overview]
Message-ID: <20220502125518.19808-5-jon.turney@dronecode.org.uk> (raw)
In-Reply-To: <20220502125518.19808-1-jon.turney@dronecode.org.uk>
../newlib/libc/libc.xml:22242: element refentry: validity error : ID iconv already defined
<refentry id="iconv">
Use a separate namespace for chaper ids, to avoid collision between the
ids for the chapter and function 'iconv', now that iconv documentation
is generated unconditionally.
---
newlib/doc/chapter-texi2docbook.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/newlib/doc/chapter-texi2docbook.py b/newlib/doc/chapter-texi2docbook.py
index 1a7803091..834a14e7c 100755
--- a/newlib/doc/chapter-texi2docbook.py
+++ b/newlib/doc/chapter-texi2docbook.py
@@ -29,7 +29,7 @@ def main():
l = l.strip()
l = l.lower()
if first_node:
- print ('<chapter id="%s" xmlns:xi="http://www.w3.org/2001/XInclude">' % l.replace(' ', '_'))
+ print ('<chapter id="%s_chapter" xmlns:xi="http://www.w3.org/2001/XInclude">' % l.replace(' ', '_'))
first_node = False
elif l.startswith("@chapter "):
l = l.replace("@chapter ", "", 1)
--
2.36.0
next prev parent reply other threads:[~2022-05-02 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 12:55 [PATCH 0/5] Various improvements to newlib manpages build Jon Turney
2022-05-02 12:55 ` [PATCH 1/5] Simplify rules for creating man pages Jon Turney
2022-05-08 19:42 ` Mike Frysinger
2022-05-02 12:55 ` [PATCH 2/5] Add build avoidance for 'make man' Jon Turney
2022-05-02 12:55 ` [PATCH 3/5] Silence xsltproc when writing manpages Jon Turney
2022-05-02 12:55 ` Jon Turney [this message]
2022-05-02 12:55 ` [PATCH 5/5] Generate manpages for functions in chapter sys.tex Jon Turney
2022-05-05 0:37 ` [PATCH 0/5] Various improvements to newlib manpages build Jeff Johnston
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=20220502125518.19808-5-jon.turney@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=newlib@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).