public inbox for newlib-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jeff Johnston <jjohnstn@sourceware.org>
To: newlib-cvs@sourceware.org
Subject: [newlib-cygwin] Fix warning about duplicate id in docbook XML
Date: Thu,  5 May 2022 00:37:38 +0000 (GMT)	[thread overview]
Message-ID: <20220505003738.472F8385736A@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=a9d2d7baae28847972fe37753b8d5a6c581ac73e

commit a9d2d7baae28847972fe37753b8d5a6c581ac73e
Author: Jon Turney <jon.turney@dronecode.org.uk>
Date:   Mon May 2 13:55:16 2022 +0100

    Fix warning about duplicate id in docbook XML
    
    ../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.

Diff:
---
 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)


                 reply	other threads:[~2022-05-05  0:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220505003738.472F8385736A@sourceware.org \
    --to=jjohnstn@sourceware.org \
    --cc=newlib-cvs@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).