[libvirt] [PATCH] docs: fix some broken HTML links
Replace name with id attribute in headers to fix the links.
Signed-off-by: Katerina Koukiou <kkoukiou(a)redhat.com>
---
docs/api_extension.html.in | 12 ++++++------
docs/dbus.html.in | 6 +++---
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/docs/api_extension.html.in b/docs/api_extension.html.in
index 9beec07602..41dd3573f5 100644
--- a/docs/api_extension.html.in
+++ b/docs/api_extension.html.in
@@ -103,7 +103,7 @@
<p>With that said, let's begin.</p>
- <h2><a name='publicapi'>Defining the public
API</a></h2>
+ <h2><a id='publicapi'>Defining the public
API</a></h2>
<p>The first task is to define the public API. If the new API
involves an XML extension, you have to enhance the RelaxNG
@@ -137,7 +137,7 @@
and <a
href="api_extension/0002-add-new-public-API.patch">0002-add-new-public-API.patch</a>
for example code.</p>
- <h2><a name='internalapi'>Defining the internal
API</a></h2>
+ <h2><a id='internalapi'>Defining the internal
API</a></h2>
<p>
Each public API call is associated with a driver, such as a host
@@ -166,7 +166,7 @@
<p class="example">See <a
href="api_extension/0003-define-internal-driver-API.patch">0003-define-internal-driver-API.patch</a></p>
- <h2><a name='implpublic'>Implementing the public
API</a></h2>
+ <h2><a id='implpublic'>Implementing the public
API</a></h2>
<p>
Implementing the public API is largely a formality in which we wire up
@@ -201,7 +201,7 @@
<p class="example">See <a
href="api_extension/0004-implement-the-public-APIs.patch">0004-implement-the-public-APIs.patch</a></p>
- <h2><a name='remoteproto'>Implementing the remote
protocol</a></h2>
+ <h2><a id='remoteproto'>Implementing the remote
protocol</a></h2>
<p>
Implementing the remote protocol is essentially a
@@ -213,7 +213,7 @@
<p class="example">See <a
href="api_extension/0005-implement-the-remote-protocol.patch">0005-implement-the-remote-protocol.patch</a></p>
- <h3><a name='wireproto'>Defining the wire protocol
format</a></h3>
+ <h3><a id='wireproto'>Defining the wire protocol
format</a></h3>
<p>
Defining the wire protocol involves making additions to:
@@ -252,7 +252,7 @@
src/remote/remote_protocol.h
</code></p>
- <h3><a name='rpcclient'>Implement the RPC
client</a></h3>
+ <h3><a id='rpcclient'>Implement the RPC
client</a></h3>
<p>
Implementing the uses the rpcgen generated .h files. The remote
diff --git a/docs/dbus.html.in b/docs/dbus.html.in
index 6ff71d2770..4dfe4ca427 100644
--- a/docs/dbus.html.in
+++ b/docs/dbus.html.in
@@ -6,14 +6,14 @@
<ul id="toc"></ul>
- <h2><a name="description">Description</a></h2>
+ <h2><a id="description">Description</a></h2>
<p>
libvirt-dbus wraps libvirt API to provide a high-level object-oriented
API better suited for dbus-based applications.
</p>
- <h2><a name="git">GIT source repository</a></h2>
+ <h2><a id="git">GIT source repository</a></h2>
<p>
The D-Bus bindings source code is maintained in a
<a href="https://git-scm.com/">git</a> repository available
on
@@ -32,7 +32,7 @@ git clone https://libvirt.org/git/libvirt-dbus.git
<a
href="https://libvirt.org/git/?p=libvirt-dbus.git">https://l...
</pre>
- <h2><a name="usage">Usage</a></h2>
+ <h2><a id="usage">Usage</a></h2>
<p>
libvirt-dbus exports libvirt API using D-Bus objects with methods and
--
2.15.0