specs/libX11: Turn many "see section ..." into links

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

16 files changed, 124 insertions, 76 deletions

diff --git a/specs/libX11/AppC.xml b/specs/libX11/AppC.xml
index 08d15555..da687ecb 100644
--- a/specs/libX11/AppC.xml
+++ b/specs/libX11/AppC.xml
@@ -1262,7 +1262,8 @@ returned to.
 If your procedure returns a zero value, 
 the error is not suppressed, and 
 the client's error handler is called.
-(For further information, see section 11.8.2.)
+(For further information,
+see <link linkend="Using_the_Default_Error_Handlers">section 11.8.2</link>.)
 If your procedure returns nonzero, 
 the error is suppressed, and 
 <function>_XReply</function>
diff --git a/specs/libX11/AppD.xml b/specs/libX11/AppD.xml
index afe65907..cacf1afd 100644
--- a/specs/libX11/AppD.xml
+++ b/specs/libX11/AppD.xml
@@ -753,7 +753,8 @@ with the following syntax:
 <programlisting>
 XGetStandardColormap(dpy, DefaultRootWindow(dpy), &amp;cmap, XA_RGB_GRAY_MAP);
 </programlisting>
-See section 14.3 for the semantics of standard colormaps.
+See <link linkend="Standard_Colormaps">section 14.3</link> for the
+semantics of standard colormaps.
 </para>
 <para>
 <!-- .LP -->
@@ -1548,7 +1549,7 @@ dash-offset, dash-list, fill-style, and fill-rule.
 <para>
 <!-- .LP -->
 These functions have been superseded by the context management functions
-(see section 16.10). 
+(see <link linkend="Using_the_Context_Manager">section 16.10</link>).
 It is often necessary to associate arbitrary information with resource IDs.
 Xlib provides the 
 <function>XAssocTable</function>
diff --git a/specs/libX11/CH01.xml b/specs/libX11/CH01.xml
index 7a2d115d..c2132e43 100644
--- a/specs/libX11/CH01.xml
+++ b/specs/libX11/CH01.xml
@@ -255,7 +255,7 @@ Because Xlib usually does not transmit requests to the server immediately
 actually occur.
 For debugging purposes, however,
 Xlib provides a mechanism for forcing synchronous behavior
-(see section 11.8.1). <!-- xref -->
+(see <link linkend="Enabling_or_Disabling_Synchronization">section 11.8.1</link>).
 When synchronization is enabled,
 errors are reported as they are generated.
     </para>
@@ -812,7 +812,7 @@ Where applicable,
 the last paragraph of the explanation lists the possible
 Xlib error codes that the function can generate.
 For a complete discussion of the Xlib error codes,
-see section 11.8.2. <!-- xref -->
+see <link linkend="Using_the_Default_Error_Handlers">section 11.8.2</link>.
 	  </para>
 	</listitem>
 	<listitem>
diff --git a/specs/libX11/CH02.xml b/specs/libX11/CH02.xml
index 901a3850..c8135aed 100644
--- a/specs/libX11/CH02.xml
+++ b/specs/libX11/CH02.xml
@@ -158,7 +158,8 @@ using the
 <function>DefaultScreen</function>
 macro or the 
 <function>XDefaultScreen</function>
-function if you are using languages other than C (see section 2.2.1).
+function if you are using languages other than C
+(see <link linkend="Display_Macros_">section 2.2.1</link>).
     </para>
   </listitem>
   </varlistentry>
@@ -242,12 +243,12 @@ For information about using macros and functions to obtain information from
 the
 <type>Display</type>
 structure,
-see section 2.2.1.
+see <link linkend="Display_Macros_">section 2.2.1</link>.
 </para>
 <para>
 <!-- .LP -->
 X servers may implement various types of access control mechanisms
-(see section 9.8).
+(see <link linkend="Controlling_Host_Access">section 9.8</link>).
 </para>
 </sect1>
 <sect1 id="Obtaining_Information_about_the_Display_Image_Formats_or_Screens">
@@ -886,7 +887,7 @@ Specifies the appropriate screen number on the host server.
 <indexterm significance="preferred"><primary>XDefaultVisual</primary></indexterm>
 Both return the default visual type for the specified screen.
 For further information about visual types,
-see section 3.1.
+see <link linkend="Visual_Types">section 3.1</link>.
 </para>
 <para>
 <!-- .LP -->
@@ -1476,7 +1477,9 @@ Applications are required to present data to the X server
 in a format that the server demands.
 To help simplify applications,
 most of the work required to convert the data is provided by Xlib
-(see sections 8.7 and 16.8).
+(see sections
+<link linkend="Transferring_Images_between_Client_and_Server">8.7</link> and
+<link linkend="Manipulating_Images">16.8</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -2166,7 +2169,7 @@ structure.
 <indexterm significance="preferred"><primary>XDefaultVisualOfScreen</primary></indexterm>
 Both return the default visual of the specified screen.
 For information on visual types,
-see section 3.1.
+see <link linkend="Visual_Types">section 3.1</link>.
 </para>
 <para>
 <!-- .LP -->
@@ -2209,7 +2212,7 @@ The value returned can be one of
 <symbol>NotUseful</symbol>,
 or
 <symbol>Always</symbol>
-(see section 3.2.4).
+(see <link linkend="Backing_Store_Attribute">section 3.2.4</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -2252,7 +2255,8 @@ If
 the screen supports save unders.
 If
 <symbol>False</symbol>,
-the screen does not support save unders (see section 3.2.5).
+the screen does not support save unders
+(see <link linkend="Save_Under_Flag">section 3.2.5</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -2543,7 +2547,8 @@ structure.
 <indexterm significance="preferred"><primary>MaxCmapsOfScreen</primary></indexterm>
 <indexterm significance="preferred"><primary>XMaxCmapsOfScreen</primary></indexterm>
 Both return the maximum number of installed colormaps supported 
-by the specified screen (see section 9.3).
+by the specified screen
+(see <link linkend="Managing_Installed_Colormaps">section 9.3</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -2580,7 +2585,8 @@ structure.
 <indexterm significance="preferred"><primary>MinCmapsOfScreen</primary></indexterm>
 <indexterm significance="preferred"><primary>XMinCmapsOfScreen</primary></indexterm>
 Both return the minimum number of installed colormaps supported 
-by the specified screen (see section 9.3).
+by the specified screen
+(see <link linkend="Managing_Installed_Colormaps">section 9.3</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -2871,7 +2877,7 @@ close_mode argument is
 <symbol>RetainPermanent</symbol>
 or
 <symbol>RetainTemporary</symbol>,
-see section 2.6.
+see <link linkend="Using_X_Server_Connection_Close_Operations_">section 2.6</link>.
 </para>
 <para>
 <!-- .LP -->
@@ -3020,7 +3026,8 @@ It deletes all but the predefined atom identifiers.
   </listitem>
   <listitem>
     <para>
-It deletes all properties on all root windows (see section 4.3).
+It deletes all properties on all root windows
+(see <link linkend="Properties_and_Atoms">section 4.3</link>).
     </para>
   </listitem>
   <listitem>
diff --git a/specs/libX11/CH03.xml b/specs/libX11/CH03.xml
index 9cbacd83..b74ac4c7 100644
--- a/specs/libX11/CH03.xml
+++ b/specs/libX11/CH03.xml
@@ -23,7 +23,8 @@ Because default windows and visual types are defined for each screen,
 most simple applications need not deal with this complexity.
 Xlib provides macros and functions that return the default root window, 
 the default depth of the default root window, and the default visual type
-(see sections 2.2.1 and 16.7).
+(see sections <link linkend="Display_Macros_">2.2.1</link>
+and <link linkend="Determining_the_Appropriate_Visual_Type">16.7</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -31,7 +32,9 @@ Xlib uses an opaque
 <structname>Visual</structname>
 <indexterm significance="preferred"><primary>Visual</primary></indexterm>
 structure that contains information about the possible color mapping.
-The visual utility functions (see section 16.7) use an
+The visual utility functions
+(see <link linkend="Determining_the_Appropriate_Visual_Type">section 16.7</link>)
+use an
 <structname>XVisualInfo</structname>
 structure to return this information to an application.
 The members of this structure pertinent to this discussion are class, red_mask,
@@ -217,7 +220,8 @@ All
 <symbol>InputOutput</symbol>
 windows have a border width of zero or more pixels, an optional background, 
 an event suppression mask (which suppresses propagation of events from 
-children), and a property list (see section 4.3).
+children), and a property list
+(see <link linkend="Properties_and_Atoms">section 4.3</link>).
 The window border and background can be a solid color or a pattern, called
 a tile.
 All windows except the root have a parent and are clipped by their parent.
@@ -231,7 +235,8 @@ obscured area.
 </para>
 <para>
 <!-- .LP -->
-Windows also have associated property lists (see section 4.3).
+Windows also have associated property lists
+(see <link linkend="Properties_and_Atoms">section 4.3</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -644,7 +649,7 @@ Otherwise, the initial contents of the exposed regions are undefined.
 events are then generated for the regions, even if the background-pixmap
 is
 <symbol>None</symbol>
-(see section 10.9).
+(see <link linkend="Exposure_Events">section 10.9</link>).
 </para>
 </sect2>
 <sect2 id="Border_Attribute">
@@ -813,7 +818,8 @@ the corresponding pair defines the change in position of the window
 within the parent.
 When a window is so repositioned, a
 <symbol>GravityNotify</symbol>
-event is generated (see section 10.10.5).
+event is generated
+(see <link linkend="GravityNotify_Events">section 10.10.5</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -1868,7 +1874,8 @@ windows and then decide to map the window to its final location.
 A window manager that wants to provide decoration might
 reparent the child into a frame first.
 For further information,
-see sections 3.2.8 and 10.10.
+see <link linkend="Override_Redirect_Flag">sections 3.2.8</link>
+and <link linkend="Window_State_Change_Events_">10.10</link>.
 Only a single client at a time can select for 
 <symbol>SubstructureRedirectMask</symbol>.
 </para>
@@ -2398,7 +2405,8 @@ children of the window are affected as specified.
 If a window's size actually changes,
 the window's subwindows move according to their window gravity.
 Depending on the window's bit gravity,
-the contents of the window also may be moved (see section 3.2.3).
+the contents of the window also may be moved
+(see <link linkend="Gravity_Attributes">section 3.2.3</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -3558,7 +3566,7 @@ Specifies the structure from which the values (as specified by the value mask)
 are to be taken.
 The value mask should have the appropriate bits
 set to indicate which attributes have been set in the structure 
-(see section 3.2).
+(see <link linkend="Window_Attributes">section 3.2</link>).
     </para>
   </listitem>
   </varlistentry>
diff --git a/specs/libX11/CH04.xml b/specs/libX11/CH04.xml
index d224216d..bd37ae6b 100644
--- a/specs/libX11/CH04.xml
+++ b/specs/libX11/CH04.xml
@@ -291,7 +291,7 @@ and can be one of the following:
 <para>
 <!-- .LP -->
 For additional information on gravity,
-see section 3.2.3. <!-- xref -->
+see <link linkend="Gravity_Attributes">section 3.2.3</link>.
 </para>
 <para>
 <!-- .LP -->
@@ -817,7 +817,7 @@ the current state of the mouse buttons and the modifier keys.
 <!-- .LP -->
 Note that the logical state of a device (as seen through Xlib)
 may lag the physical state if device event processing is frozen
-(see section 12.1). <!-- xref -->
+(see <link linkend="Pointer_Grabbing_">section 12.1</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -1040,7 +1040,7 @@ The built-in font property names are:
 <para>
 <!-- .LP -->
 For further information about font properties,
-see section 8.5. <!-- xref -->
+see <link linkend="Font_Metrics">section 8.5</link>.
 </para>
 <para>
 <!-- .LP -->
@@ -1381,7 +1381,8 @@ error.
 <para>
 <!-- .LP -->
 You can attach a property list to every window.
-Each property has a name, a type, and a value (see section 4.3). <!-- xref -->
+Each property has a name, a type, and a value
+(see <link linkend="Properties_and_Atoms">section 4.3</link>).
 The value is an array of 8-bit, 16-bit, or 32-bit quantities,
 whose interpretation is left to the clients.  The type
 <type>char</type>
@@ -1934,7 +1935,7 @@ The lifetime of a property is not tied to the storing client.
 Properties remain until explicitly deleted, until the window is destroyed,
 or until the server resets.
 For a discussion of what happens when the connection to the X server is closed,
-see section 2.6.  <!-- xref -->
+see <link linkend="Using_X_Server_Connection_Close_Operations_">section 2.6</link>.
 The maximum size of a property is server dependent and can vary dynamically
 depending on the amount of memory the server has available.
 (If there is insufficient space, a
diff --git a/specs/libX11/CH06.xml b/specs/libX11/CH06.xml
index ab5cec03..bd3c1adc 100644
--- a/specs/libX11/CH06.xml
+++ b/specs/libX11/CH06.xml
@@ -172,7 +172,7 @@ Possible visual types are
 <symbol>TrueColor</symbol>,
 or 
 <symbol>DirectColor</symbol>
-(see section 3.1).
+(see <link linkend="Visual_Types">section 3.1</link>).
 </para>
 <sect1 id="Color_Structures">
 <title>Color Structures</title>
@@ -294,7 +294,7 @@ it indicates that the color specification is in a device-dependent form;
 otherwise, it is in a device-independent form.
 If the 31st bit is set,
 this indicates that the color space has been added to Xlib at run time
-(see section 6.12.4).
+(see <link linkend="Creating_Additional_Color_Spaces">section 6.12.4</link>).
 The format value for a color space added at run time may be different each
 time the program is executed.
 If references to such a color space must be made outside the client
@@ -917,7 +917,7 @@ if alloc is
 the colormap initially has no allocated entries,
 and clients can allocate them.
 For information about the visual types,
-see section 3.1.
+see <link linkend="Visual_Types">section 3.1</link>.
 </para>
 <para>
 <!-- .LP -->
diff --git a/specs/libX11/CH07.xml b/specs/libX11/CH07.xml
index ff1a9d83..32c94f15 100644
--- a/specs/libX11/CH07.xml
+++ b/specs/libX11/CH07.xml
@@ -3197,7 +3197,7 @@ errors.
 Xlib provides a set of basic functions for performing
 region arithmetic.
 For information about these functions,
-see section 16.5.
+see <link linkend="Manipulating_Regions">section 16.5</link>.
 </para>
 </sect2>
 <sect2 id="Setting_the_Arc_Mode_Subwindow_Mode_and_Graphics_Exposure_">
diff --git a/specs/libX11/CH08.xml b/specs/libX11/CH08.xml
index 5f450fe9..e6eae13b 100644
--- a/specs/libX11/CH08.xml
+++ b/specs/libX11/CH08.xml
@@ -5268,7 +5268,7 @@ frequently used data formats by replacing
 functions in the procedure vector with special case functions.
 Supported operations include destroying the image, getting a pixel,
 storing a pixel, extracting a subimage of an image, and adding a constant
-to an image (see section 16.8).
+to an image (see <link linkend="Manipulating_Images">section 16.8</link>).
 </para>
 <para>
 <!-- .LP -->
diff --git a/specs/libX11/CH09.xml b/specs/libX11/CH09.xml
index eff97c39..2389e824 100644
--- a/specs/libX11/CH09.xml
+++ b/specs/libX11/CH09.xml
@@ -194,7 +194,7 @@ The save-set of a client is a list of other clients' windows that,
 if they are inferiors of one of the client's windows at connection close,
 should not be destroyed and should be remapped if they are unmapped.
 For further information about close-connection processing,
-see section 2.6.
+see <link linkend="Using_X_Server_Connection_Close_Operations_">section 2.6</link>.
 To allow an application's window to survive when a window manager that
 has reparented a window fails,
 Xlib provides the save-set functions that you can 
@@ -992,7 +992,7 @@ If
 <symbol>AllTemporary</symbol>
 is specified, the resources of all clients that have terminated in
 <symbol>RetainTemporary</symbol>
-are destroyed (see section 2.5).
+are destroyed (see <link linkend="Closing_the_Display">section 2.5</link>).
 This permits implementation of window manager facilities that aid debugging.
 A client can set its close-down mode to
 <symbol>RetainTemporary</symbol>.
diff --git a/specs/libX11/CH10.xml b/specs/libX11/CH10.xml
index ee1e3919..4ecbddec 100644
--- a/specs/libX11/CH10.xml
+++ b/specs/libX11/CH10.xml
@@ -226,8 +226,8 @@ dispatchers.
 The X server can send events at any time in the input stream. 
 Xlib stores any events received while waiting for a reply in an event queue 
 for later use.
-Xlib also provides functions that allow you to check events 
-in the event queue (see section 11.3).
+Xlib also provides functions that allow you to check events in the event queue
+(see <link linkend="Event_Queue_Management">section 11.3</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -350,7 +350,8 @@ or
 <symbol>ClientMessage</symbol>
 cannot be masked.
 Selection-related events are only sent to clients cooperating
-with selections (see section 4.5).
+with selections
+(see <link linkend="Obtaining_and_Changing_Window_Properties">section 4.5</link>).
 When the keyboard or pointer mapping is changed,
 <symbol>MappingNotify</symbol>
 is always sent to clients.
@@ -1282,7 +1283,8 @@ and
 structures, this member is called a keycode.
 It is set to a number that represents a physical key on the keyboard.
 The keycode is an arbitrary representation for any key on the keyboard
-(see sections 12.7 and 16.1).
+(see sections <link linkend="Manipulating_the_Keyboard_Encoding">12.7</link>
+ and <link linkend="Using_Keyboard_Utility_Functions">16.1</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -1900,7 +1902,7 @@ It generates
 <symbol>EnterNotify</symbol>
 and
 <symbol>LeaveNotify</symbol>
-events (see section 10.6.1)
+events (see <link linkend="Normal_Entry_Exit_Events">section 10.6.1</link>)
 with the mode members of the 
 <type>XEnterWindowEvent</type>
 and
@@ -1932,7 +1934,7 @@ It generates
 <symbol>EnterNotify</symbol>
 and
 <symbol>LeaveNotify</symbol>
-events (see section 10.6.1)
+events (see <link linkend="Normal_Entry_Exit_Events">section 10.6.1</link>)
 with the mode members of the
 <type>XEnterWindowEvent</type>
 and
diff --git a/specs/libX11/CH11.xml b/specs/libX11/CH11.xml
index 677707b8..3fe6f23d 100644
--- a/specs/libX11/CH11.xml
+++ b/specs/libX11/CH11.xml
@@ -273,7 +273,8 @@ and processed by the X server.
 Any errors generated must be handled by the error handler.
 For each protocol error received by Xlib,
 <function>XSync</function>
-calls the client application's error handling routine (see section 11.8.2).
+calls the client application's error handling routine
+(see <link linkend="Using_the_Default_Error_Handlers">section 11.8.2</link>).
 Any events generated by the server are enqueued into the library's 
 event queue.
 </para>
@@ -1512,7 +1513,7 @@ determines which clients should receive the specified events,
 and ignores any active grabs.
 This function requires you to pass an event mask.
 For a discussion of the valid event mask names,
-see section 10.3.
+see <link linkend="Event_Masks">section 10.3</link>.
 This function uses the w argument to identify the destination window as follows:
 </para>
 <itemizedlist>
diff --git a/specs/libX11/CH13.xml b/specs/libX11/CH13.xml
index 4f2594d6..37121ba4 100644
--- a/specs/libX11/CH13.xml
+++ b/specs/libX11/CH13.xml
@@ -3520,7 +3520,8 @@ and
 except that they work with font sets instead of single fonts
 and interpret the text based on the locale of the font set
 instead of treating the bytes of the string as direct font indexes.
-See section 8.6 for details of the use of Graphics Contexts (GCs)
+See <link linkend="Drawing_Text">section 8.6</link> for details
+of the use of Graphics Contexts (GCs)
 and possible protocol errors.
 If a 
 <errorname>BadFont</errorname>
@@ -4553,7 +4554,7 @@ is being used to do input for
 multiple text entry areas, it will also be necessary
 to set the focus window of the
 input context whenever the focus window changes
-(see section 13.5.6.3).
+(see <link linkend="Focus_Window">section 13.5.6.3</link>).
 </para>
 </sect3>
 <sect3 id="Geometry_Management">
@@ -4671,7 +4672,8 @@ may change the geometry desired by the input method.
 </para>
 <para>
 <!-- .LP -->
-The table of <acronym>XIC</acronym> values (see section 13.5.6)
+The table of <acronym>XIC</acronym> values
+(see <link linkend="Input_Context_Values">section 13.5.6</link>)
 indicates the values that can cause the desired geometry to change
 when they are set.
 It is the responsibility of the client to renegotiate the geometry
@@ -5857,7 +5859,8 @@ The following keys apply to this table.
 <para>
 <!-- .LP -->
 <symbol>XNR6PreeditCallback</symbol>
-is obsolete and its use is not recommended (see section 13.5.4.6).
+is obsolete and its use is not recommended
+(see <link linkend="Preedit_Callback_Behavior">section 13.5.4.6</link>).
 </para>
 
 <sect3 id="Query_Input_Style">
@@ -7506,7 +7509,7 @@ The
 <symbol>XNGeometryCallback</symbol>
 argument is a structure of type 
 <structname>XIMCallback</structname>
-(see section 13.5.6.13.12).
+(see <link linkend="Preedit_and_Status_Callbacks">section 13.5.6.13.12</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -7561,7 +7564,8 @@ The
 <symbol>XNDestroyCallback</symbol>
 argument is a pointer to a structure of type
 <structname>XIMCallback</structname>
-(see section 13.5.6.13.12).  This callback is triggered when the input method 
+(see <link linkend="Preedit_and_Status_Callbacks">section 13.5.6.13.12</link>).
+This callback is triggered when the input method
 stops its service for any reason; for example, when a connection to an IM
 server is broken.  After the destroy callback is called, 
 the input context is destroyed and the input method is closed.
@@ -7585,7 +7589,7 @@ The
 <symbol>XNStringConversionCallback</symbol>
 argument is a structure of type
 <structname>XIMCallback</structname>
-(see section 13.5.6.13.12).
+(see <link linkend="Preedit_and_Status_Callbacks">section 13.5.6.13.12</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -8034,7 +8038,7 @@ or
 <symbol>XIMStatusArea</symbol>.
 It is used for geometry negotiation between the client and the input method
 and has no other effect on the input method 
-(see section 13.5.1.5).
+(see <link linkend="Geometry_Management">section 13.5.1.5</link>).
 </para>
 </sect4>
 <sect4 id="Spot_Location">
@@ -8783,7 +8787,8 @@ The callback is passed an
 structure in the call_data argument.
 The text member is an
 <structname>XIMStringConversionText</structname>
-structure (see section 13.5.6.9) to be filled in by the client
+structure (see <link linkend="String_Conversion_">section 13.5.6.9</link>)
+to be filled in by the client
 and describes the text to be sent to the input method.
 The data pointed to by the 
 string and feedback elements of the
diff --git a/specs/libX11/CH14.xml b/specs/libX11/CH14.xml
index d0eb36f1..f317ea40 100644
--- a/specs/libX11/CH14.xml
+++ b/specs/libX11/CH14.xml
@@ -14,11 +14,14 @@ see the Inter-Client Communication Conventions Manual.
 Xlib provides a number of standard properties and programming interfaces that are <acronym>ICCCM</acronym>
 compliant. The predefined atoms for some of these properties are defined in the &lt;X11/Xatom.h&gt;
 header file, where to avoid name conflicts with user symbols their #define name has an XA_ prefix.
-For further information about atoms and properties, see section 4.3.
+For further information about atoms and properties,
+see <link linkend="Properties_and_Atoms">section 4.3</link>.
 </para>
 <para>
 Xlib’s selection and cut buffer mechanisms provide the primary programming interfaces by which
-peer client applications communicate with each other (see sections 4.5 and 16.6). The functions
+peer client applications communicate with each other
+(see sections <link linkend="Selections">4.5</link> and
+<link linkend="Using_Cut_Buffers">16.6</link>). The functions
 discussed in this chapter provide the primary programming interfaces by which client applications
 communicate with their window and session managers as well as share standard colormaps.
 </para>
@@ -1179,7 +1182,12 @@ In addition,
 Xlib provides separate convenience functions that you can use to set each 
 of these properties.
 For further information about these convenience functions,
-see sections 14.1.4, 14.1.5, 14.2.1, and 14.2.2, respectively.
+see sections
+<link linkend="Setting_and_Reading_the_WM_NAME_Property">14.1.4</link>,
+<link linkend="Setting_and_Reading_the_WM_ICON_NAME_Property">14.1.5</link>,
+<link linkend="Setting_and_Reading_the_WM_COMMAND_Property">14.2.1</link>, and
+<link linkend="Setting_and_Reading_the_WM_CLIENT_MACHINE_Property">14.2.2</link>,
+respectively.
 <!-- .sp -->
 </para>
 <para>
@@ -3926,12 +3934,14 @@ If the normal_hints argument is non-NULL,
 <function>XmbSetWMProperties</function>
 calls
 <function>XSetWMNormalHints</function>,
-which sets the <property>WM_NORMAL_HINTS</property> property (see section 14.1.7).
+which sets the <property>WM_NORMAL_HINTS</property> property
+(see <link linkend="Setting_and_Reading_the_WM_NORMAL_HINTS_Property">section 14.1.7</link>).
 If the wm_hints argument is non-NULL, 
 <function>XmbSetWMProperties</function>
 calls
 <function>XSetWMHints</function>,
-which sets the <property>WM_HINTS</property> property (see section 14.1.6).
+which sets the <property>WM_HINTS</property> property
+(see <link linkend="Setting_and_Reading_the_WM_HINTS_Property">section 14.1.6</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -3944,7 +3954,7 @@ An argc of zero indicates a zero-length command.
 <!-- .LP -->
 The hostname of the machine is stored using 
 <function>XSetWMClientMachine</function>
-(see section 14.2.2).
+(see <link linkend="Setting_and_Reading_the_WM_CLIENT_MACHINE_Property">section 14.2.2</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -4129,21 +4139,24 @@ If the window_name argument is non-NULL,
 <function>XSetWMProperties</function>
 calls
 <function>XSetWMName</function>,
-which, in turn, sets the <property>WM_NAME</property> property (see section 14.1.4).
+which, in turn, sets the <property>WM_NAME</property> property
+(see <link linkend="Setting_and_Reading_the_WM_NAME_Property">section 14.1.4</link>).
 If the icon_name argument is non-NULL,
 <function>XSetWMProperties</function>
 calls
 <function>XSetWMIconName</function>,
-which sets the <property>WM_ICON_NAME</property> property (see section 14.1.5).
+which sets the <property>WM_ICON_NAME</property> property
+(see <link linkend="Setting_and_Reading_the_WM_ICON_NAME_Property">section 14.1.5</link>).
 If the argv argument is non-NULL, 
 <function>XSetWMProperties</function>
 calls
 <function>XSetCommand</function>,
-which sets the <property>WM_COMMAND</property> property (see section 14.2.1).
+which sets the <property>WM_COMMAND</property> property
+(see <link linkend="Setting_and_Reading_the_WM_COMMAND_Property">section 14.2.1</link>).
 Note that an argc of zero is allowed to indicate a zero-length command.
 Note also that the hostname of this machine is stored using
 <function>XSetWMClientMachine</function>
-(see section 14.2.2).
+(see <link linkend="Setting_and_Reading_the_WM_CLIENT_MACHINE_Property">section 14.2.2</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -4151,12 +4164,14 @@ If the normal_hints argument is non-NULL,
 <function>XSetWMProperties</function>
 calls
 <function>XSetWMNormalHints</function>,
-which sets the <property>WM_NORMAL_HINTS</property> property (see section 14.1.7).
+which sets the <property>WM_NORMAL_HINTS</property> property
+(see <link linkend="Setting_and_Reading_the_WM_NORMAL_HINTS_Property">section 14.1.7</link>).
 If the wm_hints argument is non-NULL, 
 <function>XSetWMProperties</function>
 calls
 <function>XSetWMHints</function>,
-which sets the <property>WM_HINTS</property> property (see section 14.1.6).
+which sets the <property>WM_HINTS</property> property
+(see <link linkend="Setting_and_Reading_the_WM_HINTS_Property">section 14.1.6</link>).
 </para>
 <para>
 <!-- .LP -->
@@ -4164,7 +4179,8 @@ If the class_hints argument is non-NULL,
 <function>XSetWMProperties</function>
 calls
 <function>XSetClassHint</function>,
-which sets the <property>WM_CLASS</property> property (see section 14.1.8).
+which sets the <property>WM_CLASS</property> property
+(see <link linkend="Setting_and_Reading_the_WM_CLASS_Property">section 14.1.8</link>).
 If the res_name member in the
 <structname>XClassHint</structname>
 structure is set to the NULL pointer and the RESOURCE_NAME environment 
diff --git a/specs/libX11/CH15.xml b/specs/libX11/CH15.xml
index 7abc6173..760adcfe 100644
--- a/specs/libX11/CH15.xml
+++ b/specs/libX11/CH15.xml
@@ -566,7 +566,7 @@ The
 function converts the null-terminated string (generally a fully qualified name)
 to a list of quarks.
 Note that the string must be in the valid ResourceName format 
-(see section 15.1).
+(see <link linkend="Resource_File_Syntax">section 15.1</link>).
 If the string is not in the Host Portable Character Encoding,
 the conversion is implementation-dependent.
 </para>
@@ -650,7 +650,8 @@ The caller must allocate sufficient space for the quarks list before calling
 <!-- .eM -->
 Component names in the list are separated by a period or 
 an asterisk character.
-The string must be in the format of a valid ResourceName (see section 15.1).
+The string must be in the format of a valid ResourceName
+(see <link linkend="Resource_File_Syntax">section 15.1</link>).
 If the string does not start with a period or an asterisk, 
 a tight binding is assumed.
 For example, the string ``*a.b*c'' becomes:
@@ -752,7 +753,8 @@ function opens the specified file,
 creates a new resource database, and loads it with the specifications
 read in from the specified file.
 The specified file should contain a sequence of entries in valid ResourceLine
-format (see section 15.1); the database that results from reading a file
+format (see <link linkend="Resource_File_Syntax">section 15.1</link>);
+the database that results from reading a file
 with incorrect syntax is implementation-dependent.
 The file is parsed in the current locale, 
 and the database is created in the current locale.
@@ -805,7 +807,8 @@ The
 <function>XrmPutFileDatabase</function>
 function stores a copy of the specified database in the specified file.
 Text is written to the file as a sequence of entries in valid
-ResourceLine format (see section 15.1).
+ResourceLine format
+(see <link linkend="Resource_File_Syntax">section 15.1</link>).
 The file is written in the locale of the database.
 Entries containing resource names that are not in the Host Portable Character
 Encoding or containing values that are not in the encoding of the database
@@ -940,7 +943,8 @@ is similar to
 <function>XrmGetFileDatabase</function>
 except that it reads the information out of a string instead of out of a file.
 The string should contain a sequence of entries in valid ResourceLine
-format (see section 15.1) terminated by a null character;
+format (see <link linkend="Resource_File_Syntax">section 15.1</link>)
+terminated by a null character;
 the database that results from using a string
 with incorrect syntax is implementation-dependent.
 The string is parsed in the current locale, 
@@ -2077,7 +2081,8 @@ If database contains NULL,
 creates a new database and returns a pointer to it.
 <function>XrmPutLineResource</function>
 adds a single resource entry to the specified database.
-The line should be in valid ResourceLine format (see section 15.1)
+The line should be in valid ResourceLine format
+(see <link linkend="Resource_File_Syntax">section 15.1</link>)
 terminated by a newline or null character;
 the database that results from using a string
 with incorrect syntax is implementation-dependent.
diff --git a/specs/libX11/CH16.xml b/specs/libX11/CH16.xml
index db42bb17..bc79f969 100644
--- a/specs/libX11/CH16.xml
+++ b/specs/libX11/CH16.xml
@@ -2132,7 +2132,8 @@ if the rectangle is partially in the specified region.
 Xlib provides functions to manipulate cut buffers,
 a very simple form of cut-and-paste inter-client communication.
 Selections are a much more powerful and useful mechanism for
-interchanging data between clients (see section 4.5)
+interchanging data between client
+(see <link linkend="Selections">section 4.5</link>)
 and generally should be used instead of cut buffers.
 </para>
 <para>
@@ -2736,7 +2737,7 @@ plane n must be located at the address (data + (n * height * bytes_per_line)).
 For a description of the 
 <structname>XImage</structname>
 structure,
-see section 8.7.
+see <link linkend="Transferring_Images_between_Client_and_Server">section 8.7</link>.
 </para>
 <para>
 <!-- .LP -->