1 files changed, 58 insertions, 58 deletions
diff --git a/specs/CH13.xml b/specs/CH13.xml
index e3292cc..b6c77cb 100755
--- a/specs/CH13.xml
+++ b/specs/CH13.xml
@@ -82,16 +82,16 @@ modification.
 <title>Additional Arguments</title>
 <para>
 Arguments were added to the procedure definitions for
-<function>XtInitProc</function>,
-<function>XtSetValuesFunc</function>,
+<xref linkend='XtInitProc' xrefstyle='select: title'/>,
+<xref linkend='XtSetValuesFunc' xrefstyle='select: title'/>,
 and
-<function>XtEventHandler</function>
+<xref linkend='XtEventHandler' xrefstyle='select: title'/>
 to provide more information and to
 allow event handlers to abort further dispatching of the current event
 (caution is advised!).  The added arguments to
-<function>XtInitProc</function>
+<xref linkend='XtInitProc' xrefstyle='select: title'/>
 and
-<function>XtSetValuesFunc</function>
+<xref linkend='XtSetValuesFunc' xrefstyle='select: title'/>
 make the initialize_hook and set_values_hook methods
 obsolete, but the hooks have been retained for those widgets that used
 them in Release 3.
@@ -124,7 +124,7 @@ specification change is small.
 <title>Query Geometry</title>
 <para>
 A composite widget layout routine that calls
-<function>XtQueryGeometry</function>
+<xref linkend='XtQueryGeometry' xrefstyle='select: title'/>
 is now expected to store the complete new geometry in the intended structure;
 previously the specification said ``store the changes it intends to
 make''.  Only by storing the complete geometry does the child have
@@ -139,7 +139,7 @@ to take advantage of the new information.
 <para>
 In order to provide a mechanism for widgets to be notified when they
 become unrealized through a call to
-<function>XtUnrealizeWidget</function>,
+<xref linkend='XtUnrealizeWidget' xrefstyle='select: title'/>,
 the callback
 list name ``unrealizeCallback'' has been defined by the Intrinsics.  A
 widget class that requires notification on unrealize may declare a
@@ -208,7 +208,7 @@ interface.
 In the now obsolete old type converter interface, converters are
 reminded that they must return the size of the converted value as well
 as its address.  The example indicated this, but the description of
-<function>XtConverter</function>
+<xref linkend='XtConverter' xrefstyle='select: title'/>
 was incomplete.
 </para>
 </sect2>
@@ -217,7 +217,7 @@ was incomplete.
 <title>KeySym Case Conversion Procedure</title>
 <para>
 The specification for the
-<function>XtCaseProc</function>
+<xref linkend='XtCaseProc' xrefstyle='select: title'/>
 function type has been changed
 to match the Release 3 implementation, which included necessary
 additional information required by the function (a pointer to the
@@ -335,7 +335,7 @@ values when overriding the system defaults.
 <sect2 id="Customization_Resource">
 <title>Customization Resource</title>
 <para>
-<function>XtResolvePathname</function>
+<xref linkend='XtResolvePathname' xrefstyle='select: title'/>
 supports a new substitution string, %C, for specifying separate
 application class resource files according to arbitrary user-specified
 categories.  The primary motivation for this addition was separate
@@ -366,7 +366,7 @@ description of the process by which the resource database(s) is
 initialized, the net effect is the same as in prior releases with the
 exception of the added per-screen resource specification and the new
 customization substitution string in
-<function>XtResolvePathname</function>.
+<xref linkend='XtResolvePathname' xrefstyle='select: title'/>.
 </para>
 </sect2>
 
@@ -398,9 +398,9 @@ to do so.
 The internationalization additions also define event filters
 as a part of the Xlib Input Method specifications.  The
 Intrinsics enable the use of event filters through additions to
-<function>XtDispatchEvent</function>.
+<xref linkend='XtDispatchEvent' xrefstyle='select: title'/>.
 Applications that may not be dispatching all events through
-<function>XtDispatchEvent</function>
+<xref linkend='XtDispatchEvent' xrefstyle='select: title'/>
 should be reviewed in the context of this new input method mechanism.
 </para>
 
@@ -444,12 +444,12 @@ on the fly.
 <title>Arguments to Existing Functions</title>
 <para>
 The <emphasis remap='I'>args</emphasis> argument to
-<function>XtAppInitialize</function>,
-<function>XtVaAppInitialize</function>,
-<function>XtOpenDisplay</function>,
-<function>XtDisplayInitialize</function>,
+<xref linkend='XtAppInitialize' xrefstyle='select: title'/>,
+<xref linkend='XtVaAppInitialize' xrefstyle='select: title'/>,
+<xref linkend='XtOpenDisplay' xrefstyle='select: title'/>,
+<xref linkend='XtDisplayInitialize' xrefstyle='select: title'/>,
 and
-<function>XtInitialize</function>
+<xref linkend='XtInitialize' xrefstyle='select: title'/>
 were changed from
 <function>Cardinal</function>*
 to int* to conform to pre-existing convention and avoid otherwise
@@ -490,7 +490,7 @@ the specification now more exactly describes the process.
 <para>
 As a convenience, an interface to locate a widget class extension
 record on a linked list,
-<function>XtGetClassExtension</function>,
+<xref linkend='XtGetClassExtension' xrefstyle='select: title'/>,
 has been added.
 </para>
 
@@ -505,7 +505,7 @@ extension record.
 
 <para>
 The wording of the process followed by
-<function>XtUnmanageChildren</function>
+<xref linkend='XtUnmanageChildren' xrefstyle='select: title'/>
 has changed slightly to better handle changes to the managed set
 during phase 2 destroy processing.
 </para>
@@ -525,12 +525,12 @@ compute the region.
 <sect2 id="General_Application_Development">
 <title>General Application Development</title>
 <para>
-<function>XtOpenApplication</function>
+<xref linkend='XtOpenApplication' xrefstyle='select: title'/>
 is a new convenience procedure to initialize the toolkit, create an
 application context, open an X display connection, and create the
 root of the widget instance tree.  It is identical to the interface
 it replaces,
-<function>XtAppInitialize</function>,
+<xref linkend='XtAppInitialize' xrefstyle='select: title'/>,
 in all respects except that it takes an additional argument specifying
 the widget class of the root shell to create.
 This interface is now the recommended one so that clients may easily
@@ -540,14 +540,14 @@ The old convenience procedures appear in the compatibility section.
 
 <para>
 The toolkit initialization function
-<function>XtToolkitInitialize</function>
+<xref linkend='XtToolkitInitialize' xrefstyle='select: title'/>
 may be called multiple times without penalty.
 </para>
 
 <para>
 In order to optimize changes in geometry to a set of geometry-managed
 children, a new interface,
-<function>XtChangeManagedSet</function>,
+<xref linkend='XtChangeManagedSet' xrefstyle='select: title'/>,
 has been added.
 </para>
 </sect2>
@@ -580,9 +580,9 @@ operations by participating applications.  The
 structures
 the application's notification of and responses to messages from the session
 manager by use of various callback lists and by use of the new interfaces
-<function>XtSessionGetToken</function>
+<xref linkend='XtSessionGetToken' xrefstyle='select: title'/>
 and
-<function>XtSessionReturnToken</function>.
+<xref linkend='XtSessionReturnToken' xrefstyle='select: title'/>.
 There is also a new command line argument, -xtsessionID, which facilitates
 the session manager in restarting applications based on the Intrinsics.
 </para>
@@ -621,23 +621,23 @@ In Release 6, support is provided for registering selectors
 and event handlers for events generated by X protocol extensions
 and for dispatching those events to the appropriate widget.
 The new event handler registration interfaces are
-<function>XtInsertEventTypeHandler</function>
+<xref linkend='XtInsertEventTypeHandler' xrefstyle='select: title'/>
 and
-<function>XtRemoveEventTypeHandler</function>.
+<xref linkend='XtRemoveEventTypeHandler' xrefstyle='select: title'/>.
 Since the mechanism to indicate selection of extension events is specific
 to the extension being used, the Intrinsics introduces
-<function>XtRegisterExtensionSelector</function>,
+<xref linkend='XtRegisterExtensionSelector' xrefstyle='select: title'/>,
 which allows the application to select for the events of interest.
 In order to change the dispatching algorithm to accommodate extension events
 as well as core X protocol events,
 the Intrinsics event dispatcher may now be replaced or enveloped
 by the application with
-<function>XtSetEventDispatcher</function>.
+<xref linkend='XtSetEventDispatcher' xrefstyle='select: title'/>.
 The dispatcher may wish to call
-<function>XtGetKeyboardFocusWidget</function>
+<xref linkend='XtGetKeyboardFocusWidget' xrefstyle='select: title'/>
 to determine the widget with the current Intrinsics keyboard focus.
 A dispatcher, after determining the destination widget, may use
-<function>XtDispatchEventToWidget</function>
+<xref linkend='XtDispatchEventToWidget' xrefstyle='select: title'/>
 to cause the event to be dispatched to the event handlers registered
 by a specific widget.
 </para>
@@ -646,12 +646,12 @@ by a specific widget.
 To permit the dispatching of events
 for nonwidget drawables, such as pixmaps that are not associated
 with a widget's window,
-<function>XtRegisterDrawable</function>
+<xref linkend='XtRegisterDrawable' xrefstyle='select: title'/>
 and
-<function>XtUnregisterDrawable</function>
+<xref linkend='XtUnregisterDrawable' xrefstyle='select: title'/>
 have been added to the library.  A related update was made to
 the description of
-<function>XtWindowToWidget</function>.
+<xref linkend='XtWindowToWidget' xrefstyle='select: title'/>.
 </para>
 
 <para>
@@ -659,39 +659,39 @@ The library is now thread-safe, allowing one thread at a time to
 enter the library and protecting global data as necessary from concurrent use.
 Threaded toolkit applications are supported by the
 new interfaces
-<function>XtToolkitThreadInitialize</function>,
-<function>XtAppLock</function>,
-<function>XtAppUnlock</function>,
-<function>XtAppSetExitFlag</function>,
+<xref linkend='XtToolkitThreadInitialize' xrefstyle='select: title'/>,
+<xref linkend='XtAppLock' xrefstyle='select: title'/>,
+<xref linkend='XtAppUnlock' xrefstyle='select: title'/>,
+<xref linkend='XtAppSetExitFlag' xrefstyle='select: title'/>,
 and
-<function>XtAppGetExitFlag</function>.
+<xref linkend='XtAppGetExitFlag' xrefstyle='select: title'/>.
 Widget writers may also use
-<function>XtProcessLock</function>
+<xref linkend='XtProcessLock' xrefstyle='select: title'/>
 and
-<function>XtProcessUnlock</function>.
+<xref linkend='XtProcessUnlock' xrefstyle='select: title'/>.
 </para>
 
 <para>
 Safe handling of POSIX signals and other asynchronous notifications
 is now provided by use of
-<function>XtAppAddSignal</function>,
-<function>XtNoticeSignal</function>,
+<xref linkend='XtAppAddSignal' xrefstyle='select: title'/>,
+<xref linkend='XtNoticeSignal' xrefstyle='select: title'/>,
 and
-<function>XtRemoveSignal</function>.
+<xref linkend='XtRemoveSignal' xrefstyle='select: title'/>.
 </para>
 
 <para>
 The application can receive notification of an impending block
 in the Intrinsics event manager by registering interest through
-<function>XtAppAddBlockHook</function>
+<xref linkend='XtAppAddBlockHook' xrefstyle='select: title'/>
 and
-<function>XtRemoveBlockHook</function>.
+<xref linkend='XtRemoveBlockHook' xrefstyle='select: title'/>.
 </para>
 
 <para>
-<function>XtLastEventProcessed</function>
+<xref linkend='XtLastEventProcessed' xrefstyle='select: title'/>
 returns the most recent event passed to
-<function>XtDispatchEvent</function>
+<xref linkend='XtDispatchEvent' xrefstyle='select: title'/>
 for a specified display.
 </para>
 </sect2>
@@ -731,23 +731,23 @@ ignore NumLock and apply the normal protocol semantics.
 The targets of selection requests may be parameterized, as described
 by the revised <emphasis remap='I'>Inter-Client Communication Conventions Manual.</emphasis>.
 When such requests are made,
-<function>XtSetSelectionParameters</function>
+<xref linkend='XtSetSelectionParameters' xrefstyle='select: title'/>
 is used by the requestor to specify the target parameters and
-<function>XtGetSelectionParameters</function>
+<xref linkend='XtGetSelectionParameters' xrefstyle='select: title'/>
 is used by the selection owner to retrieve the parameters.
 When a parameterized target is specified in the context of a bundled
 request for multiple targets,
-<function>XtCreateSelectionRequest</function>,
-<function>XtCancelSelectionRequest</function>,
+<xref linkend='XtCreateSelectionRequest' xrefstyle='select: title'/>,
+<xref linkend='XtCancelSelectionRequest' xrefstyle='select: title'/>,
 and
-<function>XtSendSelectionRequest</function>
+<xref linkend='XtSendSelectionRequest' xrefstyle='select: title'/>
 are used to envelop the assembly of the request.
 When the parameters themselves are the names of properties,
 the Intrinsics provides support for the economical use of property atom names;
 see
-<function>XtReservePropertyAtom</function>
+<xref linkend='XtReservePropertyAtom' xrefstyle='select: title'/>
 and
-<function>XtReleasePropertyAtom</function>.
+<xref linkend='XtReleasePropertyAtom' xrefstyle='select: title'/>.
 </para>
 </sect2>
 
@@ -762,9 +762,9 @@ The hook callbacks permit the external agent to register interest
 in groups or classes of toolkit activity and to be notified of the
 type and details of the activity as it occurs.  The new interfaces
 related to this effort are
-<function>XtHooksOfDisplay</function>,
+<xref linkend='XtHooksOfDisplay' xrefstyle='select: title'/>,
 which returns the hook registration widget, and
-<function>XtGetDisplays</function>,
+<xref linkend='XtGetDisplays' xrefstyle='select: title'/>,
 which returns a list of the X displays associated with an application context.
 </para>
 </sect2>