specs/libX11: Turn chapter references into links

Signed-off-by: Alan Coopersmith <alan.coopersmith@oracle.com>

8 files changed, 26 insertions, 16 deletions

diff --git a/specs/libX11/AppD.xml b/specs/libX11/AppD.xml
index cacf1afd..3c8af3f6 100644
--- a/specs/libX11/AppD.xml
+++ b/specs/libX11/AppD.xml
@@ -1051,7 +1051,7 @@ geometry specifications.
 The
 <function>XGetDefault</function>
 function provides a primitive interface to the resource manager facilities 
-discussed in chapter 15. <!-- xref -->
+discussed in <link linkend="resource_manager_functions">chapter 15</link>.
 It is only useful in very simple applications.
 </para>
 <para>
diff --git a/specs/libX11/CH01.xml b/specs/libX11/CH01.xml
index c2132e43..21750aba 100644
--- a/specs/libX11/CH01.xml
+++ b/specs/libX11/CH01.xml
@@ -316,8 +316,8 @@ reference this file directly.
       <indexterm><primary>Headers</primary><secondary>&lt;X11/Xcms.h&gt;</secondary></indexterm>
       <para>
 This file contains symbols for much of the color management facilities
-described in chapter 6.  All functions, types, and symbols with the
-prefix "Xcms", <!-- xref -->
+described in <link linkend="color_management_functions">chapter 6</link>.
+All functions, types, and symbols with the prefix "Xcms",
 plus the Color Conversion Contexts macros, are declared in this file.
 <filename class="headerfile">&lt;X11/Xlib.h&gt;</filename>
 must be included before including this file.
@@ -333,7 +333,9 @@ must be included before including this file.
       <para>
 This file declares various functions, types, and symbols used for
 inter-client communication and application utility functions,
-which are described in chapters 14 and 16. <!-- xref -->
+which are described in chapters
+<link linkend="inter_client_communication_functions">14</link> and
+<link linkend="application_utility_functions">16</link>.
 <filename class="headerfile">&lt;X11/Xlib.h&gt;</filename> must be included before including this file.
       </para>
     </listitem>
@@ -346,7 +348,8 @@ which are described in chapters 14 and 16. <!-- xref -->
       <indexterm><primary>Headers</primary><secondary>&lt;X11/Xresource.h&gt;</secondary></indexterm>
       <para>
 This file declares all functions, types, and symbols for the
-resource manager facilities, which are described in chapter 15.
+resource manager facilities, which are described in
+<link linkend="resource_manager_functions">chapter 15</link>.
 <filename class="headerfile">&lt;X11/Xlib.h&gt;</filename> <!-- xref -->
 must be included before including this file.
       </para>
@@ -680,7 +683,7 @@ rather than presume control of the entire screen.
 What you do inside of your top-level window, however,
 is up to your application.
 For further information,
-see chapter 14 <!-- xref -->
+see <link linkend="inter_client_communication_functions">chapter 14</link>
 and the <citetitle>Inter-Client Communication Conventions Manual</citetitle>.
     </para>
   </listitem>
diff --git a/specs/libX11/CH02.xml b/specs/libX11/CH02.xml
index c8135aed..4a57266b 100644
--- a/specs/libX11/CH02.xml
+++ b/specs/libX11/CH02.xml
@@ -3205,7 +3205,9 @@ for threads using
 <!-- .LP -->
 In addition to the connection to the X server, an Xlib implementation
 may require connections to other kinds of servers (for example, to
-input method servers as described in chapter 13).  Toolkits and clients
+input method servers as described in
+<link linkend="locales_and_internationalized_text_functions">chapter 13</link>).
+Toolkits and clients
 that use multiple displays, or that use displays in combination with
 other inputs, need to obtain these additional connections to correctly
 block until input is available and need to process that input
diff --git a/specs/libX11/CH03.xml b/specs/libX11/CH03.xml
index b74ac4c7..d26a814c 100644
--- a/specs/libX11/CH03.xml
+++ b/specs/libX11/CH03.xml
@@ -1072,7 +1072,7 @@ or
 <symbol>False</symbol>
 (default).
 Window managers use this information to avoid tampering with pop-up windows
-(see also chapter 14).
+(see also <link linkend="inter_client_communication_functions">chapter 14</link>).
 </para>
 </sect2>
 <sect2 id="Colormap_Attribute">
@@ -1167,7 +1167,7 @@ which are discussed in the appropriate toolkit documentation.
 If you do not use a toolkit, however,
 you must provide some standard information or hints for the window
 manager by using the Xlib inter-client communication functions
-(see chapter 14).
+(see <link linkend="inter_client_communication_functions">chapter 14</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -1211,7 +1211,8 @@ you should set these properties for top-level windows before mapping them.
 <para>
 <!-- .LP -->
 For further information,
-see chapter 14 and the <emphasis remap='I'>Inter-Client Communication Conventions Manual</emphasis>.
+see <link linkend="inter_client_communication_functions">chapter 14</link> and
+the <emphasis remap='I'>Inter-Client Communication Conventions Manual</emphasis>.
 </para>
 <para>
 <!-- .LP -->
diff --git a/specs/libX11/CH04.xml b/specs/libX11/CH04.xml
index bd37ae6b..957d390b 100644
--- a/specs/libX11/CH04.xml
+++ b/specs/libX11/CH04.xml
@@ -887,7 +887,7 @@ To avoid name clashes with user symbols, the
 name for each atom has the XA_ prefix.
 For an explanation of the functions that let you get and set
 much of the information stored in these predefined properties,
-see chapter 14. <!-- xref -->
+see <link linkend="inter_client_communication_functions">chapter 14</link>.
 </para>
 <para>
 <!-- .LP -->
@@ -1397,7 +1397,8 @@ is used to represent 32-bit quantities.
 Xlib provides functions that you can use to obtain, 
 change, update, or interchange window properties.
 In addition, Xlib provides other utility functions for inter-client
-communication (see chapter 14). <!-- xref -->
+communication
+(see <link linkend="inter_client_communication_functions">chapter 14</link>).
 </para>
 <para>
 <!-- .LP -->
diff --git a/specs/libX11/CH10.xml b/specs/libX11/CH10.xml
index 4ecbddec..8a06a706 100644
--- a/specs/libX11/CH10.xml
+++ b/specs/libX11/CH10.xml
@@ -24,7 +24,8 @@ This chapter discusses the following topics associated with events:
 </itemizedlist>
 
 <para>
-Functions for handling events are dealt with in the next chapter.
+Functions for handling events are dealt with in
+<link linkend="event_handling_functions">the next chapter</link>.
 </para>
 
 <sect1 id="Event_Types">
@@ -999,7 +1000,7 @@ and the pointer events
 and
 <symbol>MotionNotify</symbol>.
 For information about the keyboard event-handling utilities,
-see chapter 11.
+see <link linkend="event_handling_functions">chapter 11</link>.
 </para>
 <para>
 <!-- .LP -->
diff --git a/specs/libX11/CH14.xml b/specs/libX11/CH14.xml
index f317ea40..b6483066 100644
--- a/specs/libX11/CH14.xml
+++ b/specs/libX11/CH14.xml
@@ -251,7 +251,8 @@ of top-level windows (that is, those that were created as children
 of the root window).
 Note that the subwindows that you create are ignored by window managers.
 Therefore,
-you should use the basic window functions described in chapter 3
+you should use the basic window functions described in
+<link linkend="window_functions">chapter 3</link>
 to manipulate your application's subwindows.
 </para>
 <para>
diff --git a/specs/libX11/CH16.xml b/specs/libX11/CH16.xml
index bc79f969..fecbb2f4 100644
--- a/specs/libX11/CH16.xml
+++ b/specs/libX11/CH16.xml
@@ -655,7 +655,8 @@ if the specified KeySym is a PF key.
 <!-- .XE -->
 <para>
 <!-- .LP -->
-Chapter 13 describes internationalized text input facilities,
+<link linkend="locales_and_internationalized_text_functions">Chapter 13</link>
+describes internationalized text input facilities,
 but sometimes it is expedient to write an application that
 only deals with Latin-1 characters and ASCII controls,
 so Xlib provides a simple function for that purpose.