diff --git a/specs/libX11/AppC.xml b/specs/libX11/AppC.xml
index 52fff317..2baee2cc 100644
--- a/specs/libX11/AppC.xml
+++ b/specs/libX11/AppC.xml
@@ -43,7 +43,7 @@ The basic protocol requests for extensions are
and
XListExtensions .
-
+XQueryExtension
@@ -128,7 +128,7 @@ the result is implementation-dependent.
Uppercase and lowercase matter;
the strings ``thing'', ``Thing'', and ``thinG''
are all considered different names.
-
+XListExtensions
@@ -170,7 +170,7 @@ function returns a list of all extensions supported by the server.
If the data returned by the server is in the Latin Portable Character Encoding,
then the returned strings are in the Host Portable Character Encoding.
Otherwise, the result is implementation-dependent.
-
+XFreeExtensionList
@@ -237,7 +237,7 @@ and is defined in
-
+XExtCodes
@@ -253,7 +253,7 @@ typedef struct _XExtCodes { /* public to extension, cannot be changed */
-
+XInitExtension
@@ -319,7 +319,7 @@ This extension number is unique only to a single connection.
-
+XAddExtension
@@ -367,7 +367,7 @@ format, and the handling of errors.
All of these functions return the previous procedure defined for this
extension.
-
+XESetCloseDisplay
@@ -435,7 +435,7 @@ with these arguments:
XExtCodes *codes;
-
+XESetCreateGC
@@ -503,7 +503,7 @@ your procedure is called with these arguments:
XExtCodes *codes;
-
+XESetCopyGC
@@ -636,7 +636,7 @@ your procedure is called with these arguments:
-
+XESetCreateFont
@@ -717,7 +717,7 @@ your procedure is called with these arguments:
-
+XESetFreeFont
@@ -829,7 +829,7 @@ union of structures.
There also is no way to guarantee that more than 24 elements or 96 characters
in the structure will be fully portable between machines.
-
+XESetWireToEvent
@@ -941,7 +941,7 @@ with the event and use the return value.
-
+_XSetLastRequestRead
@@ -985,7 +985,7 @@ serial number in the event.
-
+XESetEventToWire
@@ -1079,7 +1079,7 @@ structure.
All other members then should be copied from the host format to the
xEvent
structure.
-
+XESetWireToError
@@ -1176,7 +1176,7 @@ then the function should return
False ;
otherwise, it should return
True .
-
+XESetError
@@ -1268,7 +1268,7 @@ If your procedure returns nonzero,
the error is suppressed, and
_XReply
returns the value of ret_code.
-
+XESetErrorString
@@ -1344,7 +1344,7 @@ The following is an example.
Your procedure is called with the error code for every error detected.
You should copy nbytes of a null-terminated string containing the
error message into buffer.
-
+XESetPrintErrorValues
@@ -1428,7 +1428,7 @@ to obtain additional values set by using
XESetWireToError .
The underlying type of the fp argument is system dependent;
on a POSIX-compliant system, fp should be cast to type FILE*.
-
+XESetFlushGC
@@ -1480,7 +1480,7 @@ The procedure set by the
function has the same interface as the procedure set by the
XESetCopyGC
function, but is called when a GC cache needs to be updated in the server.
-
+XESetBeforeFlush
@@ -1581,7 +1581,7 @@ and is defined in
-
+XExtData
@@ -1620,7 +1620,7 @@ union { Display *display;
-
+XEHeadOfExtensionList
@@ -1658,7 +1658,7 @@ of types contained in
-
+XAddToExtensionList
@@ -1698,7 +1698,7 @@ The structure argument is a pointer to one of the data structures
enumerated above.
You must initialize ext_data->number with the extension number
before calling this function.
-
+XFindOnExtensionList
@@ -1749,7 +1749,7 @@ The
XAllocID
macro, which allocates and returns a resource ID, is defined in
<X11/Xlib.h>.
-
+XAllocID
@@ -1784,7 +1784,7 @@ It returns a resource ID that you can use when creating new resources.
The
XAllocIDs
macro allocates and returns an array of resource ID.
-
+XAllocIDs
@@ -1861,7 +1861,7 @@ if any elements have changed.
The
FlushGC
macro is defined as follows:
-
+FlushGC
@@ -1911,7 +1911,7 @@ The
_XFlushGCCache
procedure
is defined as follows:
-
+_XFlushGCCache
@@ -2149,7 +2149,7 @@ which looks like:
-
+xDoSomethingReq
@@ -2187,7 +2187,7 @@ or
-
+xResourceReq
@@ -2237,7 +2237,7 @@ also contains a reply structure typedef:
-
+xDoSomethingReply
@@ -2339,7 +2339,7 @@ call until all arguments to the call have been stored into the buffer.
The precise instructions needed for this locking depend upon the machine
architecture.
Two calls, which are generally implemented as macros, have been provided.
-
+LockDisplay
@@ -2351,7 +2351,7 @@ Two calls, which are generally implemented as macros, have been provided.
-
+UnlockDisplay
UnlockDisplay
@@ -2590,7 +2590,7 @@ packet to arrive.
If any events arrive in the meantime,
_XReply
places them in the queue for later use.
-
+_XReply
@@ -3075,7 +3075,7 @@ the general memory allocators may be too expensive to use
(particularly in output functions, which are performance critical).
The following function returns a scratch buffer for use within a
critical section:
-
+_XAllocScratch
@@ -3132,7 +3132,7 @@ families of functions.
The following function returns a scratch buffer for use across
critical sections:
-
+_XAllocTemp
@@ -3171,7 +3171,7 @@ Specifies the number of bytes required.
This storage can be used across calls that might permit another thread to
execute inside Xlib. The storage must be explicitly returned to Xlib.
The following function returns the storage:
-
+_XFreeTemp
diff --git a/specs/libX11/AppD.xml b/specs/libX11/AppD.xml
index 128ad3dd..d93c5cda 100644
--- a/specs/libX11/AppD.xml
+++ b/specs/libX11/AppD.xml
@@ -53,7 +53,7 @@ This function has been superseded by
and sets all or portions of the
WM_NAME, WM_ICON_NAME, WM_HINTS, WM_COMMAND,
and WM_NORMAL_HINTS properties.
-
+XSetStandardProperties
@@ -201,7 +201,7 @@ To set the size hints for a given window in its normal state, use
XSetNormalHints .
This function has been superseded by
XSetWMNormalHints .
-
+XSetNormalHints
@@ -290,7 +290,7 @@ To return the size hints for a window in its normal state, use
XGetNormalHints .
This function has been superseded by
XGetWMNormalHints .
-
+XGetNormalHints
@@ -361,7 +361,7 @@ To set the zoom hints for a window, use
XSetZoomHints .
This function is no longer supported by the
Inter-Client Communication Conventions Manual.
-
+XSetZoomHints
@@ -431,7 +431,7 @@ To read the zoom hints for a window, use
XGetZoomHints .
This function is no longer supported by the
Inter-Client Communication Conventions Manual.
-
+XGetZoomHints
@@ -498,7 +498,7 @@ To set the value of any property of type WM_SIZE_HINTS, use
XSetSizeHints .
This function has been superseded by
XSetWMSizeHints .
-
+XSetSizeHints
@@ -585,7 +585,7 @@ To read the value of any property of type WM_SIZE_HINTS, use
XGetSizeHints .
This function has been superseded by
XGetWMSizeHints .
-
+XGetSizeHints
@@ -678,7 +678,7 @@ structure associated with one of the described atoms, use
XGetStandardColormap .
This function has been superseded by
XGetRGBColormap .
-
+XGetStandardColormap
@@ -780,7 +780,7 @@ To set a standard colormap, use
XSetStandardColormap .
This function has been superseded by
XSetRGBColormap .
-
+XSetStandardColormap
@@ -862,8 +862,8 @@ and a default position, use
XGeometry .
This function has been superseded by
XWMGeometry .
-
-
+Windowdetermining location
+XGeometry
@@ -1067,7 +1067,7 @@ It is only useful in very simple applications.
-
+XGetDefault
@@ -1148,7 +1148,7 @@ a resource file in the user's home directory is used.
On a POSIX-conformant system,
this file is
"$HOME/.Xdefaults" .
-
+Files$HOME/.Xdefaults
After loading these defaults,
XGetDefault
merges additional defaults specified by the XENVIRONMENT
@@ -1191,10 +1191,10 @@ and have no server support.
That is, they call other Xlib functions, not the server directly.
Thus, if you just have straight lines to draw, using
XDrawLines
-
+XDrawLines
or
XDrawSegments
-
+XDrawSegments
is much faster.
@@ -1202,16 +1202,16 @@ is much faster.
The functions discussed here provide all the functionality of the
X Version 10 functions
XDraw ,
-
+X10 compatibilityXDraw
XDrawFilled ,
-
+X10 compatibilityXDrawFilled
XDrawPatterned ,
-
+X10 compatibilityXDrawPatterned
XDrawDashed ,
-
+X10 compatibilityXDrawDashed
and
XDrawTiled .
-
+X10 compatibilityXDrawTiled
They are as compatible as possible given X Version 11's new line-drawing
functions.
One thing to note, however, is that
@@ -1249,12 +1249,12 @@ set.
To achieve the effects of the X Version 10
XDraw ,
-
+X10 compatibilityXDraw
XDrawDashed ,
-
+X10 compatibilityXDrawDashed
and
XDrawPatterned ,
-
+X10 compatibilityXDrawPatterned
use
XDraw .
@@ -1344,7 +1344,7 @@ is a structure with the following members:
-
+Vertex
@@ -1371,11 +1371,11 @@ is one).
The flags, as defined in
are as follows:
-
-
-
-
-
+VertexRelative
+VertexDontDraw
+VertexCurved
+VertexStartClosed
+VertexEndClosed
@@ -1464,10 +1464,10 @@ tile-stipple-x-origin, tile-stipple-y-origin, dash-offset, and dash-list.
To achieve the effects of the X Version 10
XDrawTiled
-
+X10 compatibilityXDrawTiled
and
XDrawFilled ,
-
+X10 compatibilityXDrawFilled
use
XDrawFilled .
@@ -1566,9 +1566,9 @@ It is often necessary to associate arbitrary information with resource IDs.
Xlib provides the
XAssocTable
functions that you can use to make such an association.
-
-
-
+Hash Lookup
+WindowIDs
+Resource IDs
Application programs often need to be able to easily refer to
their own data structures when an event arrives.
The
@@ -1626,7 +1626,7 @@ To return a pointer to a new
XAssocTable ,
use
XCreateAssocTable .
-
+XCreateAssocTable
@@ -1672,7 +1672,7 @@ To create an entry in a given
XAssocTable ,
use
XMakeAssoc .
-
+XMakeAssoc
@@ -1747,7 +1747,7 @@ To obtain data from a given
XAssocTable ,
use
XLookUpAssoc .
-
+XLookUpAssoc
@@ -1812,7 +1812,7 @@ To delete an entry from a given
XAssocTable ,
use
XDeleteAssoc .
-
+XDeleteAssoc
@@ -1876,7 +1876,7 @@ To free the memory associated with a given
use
XDestroyAssocTable .
-
+XDestroyAssocTable
diff --git a/specs/libX11/CH01.xml b/specs/libX11/CH01.xml
index 8d8e1d69..cef9c210 100644
--- a/specs/libX11/CH01.xml
+++ b/specs/libX11/CH01.xml
@@ -62,15 +62,15 @@ A set of screens for a single user with one keyboard and one pointer
-
+Screen
All the windows in an X server are arranged in strict hierarchies.
At the top of each hierarchy is a root window,
which covers each of the display screens.
Each root window is partially or completely covered by child windows.
All windows, except for root windows, have parents.
There is usually at least one window for each application program.
-
-
+Child window
+Parent Window
Child windows may in turn have their own children.
In this way,
an application program can create an arbitrarily deep tree
@@ -83,7 +83,7 @@ A child window can be larger than its parent.
That is, part or all of
the child window can extend beyond the boundaries of the parent,
but all output to a window is clipped by its parent.
-
+Stacking order
If several children of a window have overlapping locations,
one of the children is considered to be on top of or raised over the
others, thus obscuring them.
@@ -95,7 +95,7 @@ that are also ancestors of the first window.
-
+Window
A window has a border zero or more pixels in width, which can
be any pattern (pixmap) or solid color you like.
A window usually but not always has a background pattern,
@@ -127,10 +127,10 @@ Programs must be prepared to regenerate the contents of windows on demand.
-
-
-
-
+Pixmap
+Drawable
+Tile
+Bitmap
X also provides off-screen storage of graphics objects,
called pixmaps.
Single plane (depth 1) pixmaps are sometimes referred to as bitmaps.
@@ -150,7 +150,7 @@ which will be called when the error is reported.
-
+XSync
If a client does not want a request to execute asynchronously,
it can follow the request with a call to
XSync ,
@@ -162,12 +162,12 @@ that returns a value from the server or waits for input.
-
-
-
-
-
-
+Resource IDs
+Resource IDsWindow
+Resource IDsFont
+Resource IDsPixmap
+Resource IDsCursor
+Resource IDsGContext
Many Xlib functions will return an integer resource ID,
which allows you to refer to objects stored on the X server.
These can be of type
@@ -192,7 +192,7 @@ Xlib provides no support for sharing graphics contexts between applications.
-
+Event
Client programs are informed of events.
Events may either be side effects of a request (for example, restacking windows
generates
@@ -219,7 +219,7 @@ and
ConfigureRequest
events.
These events also arrive asynchronously, but the client may
-
+XSync
wish to explicitly wait for them by calling
XSync
after calling a function that can cause the server to generate events.
@@ -238,10 +238,10 @@ an integer error indication.
If the function fails, it returns a zero.
If the function returns a status of zero,
it has not updated the return arguments.
-
+Status
Because C does not provide multiple return values,
many functions must return their results by writing into client-passed storage.
-
+Errorhandling
By default, errors are handled either by a standard library function
or by one that you provide.
Functions that return pointers to strings return NULL pointers if
@@ -295,7 +295,7 @@ This is the main header file for Xlib.
The majority of all Xlib symbols are declared by including this file.
This file also contains the preprocessor symbol
XlibSpecificationRelease .
-
+XlibSpecificationRelease
This symbol is defined to have the 6 in this release of the standard.
(Release 5 of Xlib was the first release to have this symbol.)
@@ -451,9 +451,9 @@ X10 compatibility functions, which are described in appendix D.
The following symbols are defined by Xlib and used throughout the manual:
-
-
-
+Bool
+True
+False
@@ -464,14 +464,14 @@ and the Boolean values
True
and
False .
-
+None
None
is the universal null resource ID or atom.
-
+XID
@@ -479,7 +479,7 @@ is the universal null resource ID or atom.
The type
XID
is used for generic resource IDs.
-
+XPointer
diff --git a/specs/libX11/CH02.xml b/specs/libX11/CH02.xml
index 0d281067..acee8d70 100644
--- a/specs/libX11/CH02.xml
+++ b/specs/libX11/CH02.xml
@@ -61,7 +61,7 @@ Use internal connections
To open a connection to the X server that controls a display, use
XOpenDisplay .
-
+XOpenDisplay
@@ -85,7 +85,7 @@ Specifies the hardware display name, which determines the display
and communications domain to be used.
On a POSIX-conformant system, if the display_name is NULL,
it defaults to the value of the DISPLAY environment variable.
-
+EnvironmentDISPLAY
@@ -143,7 +143,7 @@ Specifies the number of the display server on that host machine.
You may optionally follow this display number with a period (.).
A single CPU can have more than one display.
Multiple displays are usually numbered starting with zero.
-
+Screen
@@ -190,8 +190,8 @@ about that X server.
connects your application to the X server through TCP
or DECnet communications protocols,
or through some local inter-process communication protocol.
-
-
+ProtocolTCP
+ProtocolDECnet
If the protocol is specified as "tcp", "inet", or "inet6", or
if no protocol is specified and the hostname is a host machine name and a single colon (:)
separates the hostname and display number,
@@ -212,7 +212,7 @@ mechanisms.
-
+Display
If successful,
XOpenDisplay
returns a pointer to a
@@ -283,7 +283,7 @@ Screen information macros
-
+Displaydata structure
All other members of the
Display
structure (that is, those for which no macros are defined) are private to Xlib
@@ -332,8 +332,8 @@ and what data both can return.
-
-
+AllPlanes
+XAllPlanes
Both return a value with all bits set to 1 suitable for use in a plane argument to
a procedure.
@@ -388,8 +388,8 @@ Specifies the appropriate screen number on the host server.
-
-
+BlackPixel
+XBlackPixel
Both return the black pixel value for the specified screen.
@@ -433,8 +433,8 @@ Specifies the appropriate screen number on the host server.
-
-
+WhitePixel
+XWhitePixel
Both return the white pixel value for the specified screen.
@@ -468,8 +468,8 @@ Specifies the connection to the X server.
-
-
+ConnectionNumber
+XConnectionNumber
Both return a connection number for the specified display.
On a POSIX-conformant system,
this is the file descriptor of the connection.
@@ -515,8 +515,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DefaultColormap
+XDefaultColormap
Both return the default colormap ID for allocation on the specified screen.
Most routine allocations of color should be made out of this colormap.
@@ -561,8 +561,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DefaultDepth
+XDefaultDepth
Both return the depth (number of planes) of the default root window for the
specified screen.
Other depths may also be supported on this screen (see
@@ -571,7 +571,7 @@ Other depths may also be supported on this screen (see
-
+XListDepths
To determine the number of depths that are available on a given screen, use
XListDepths .
@@ -677,8 +677,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DefaultGC
+XDefaultGC
Both return the default graphics context for the root window of the
specified screen.
This GC is created for the convenience of simple applications
@@ -719,8 +719,8 @@ Specifies the connection to the X server.
-
-
+DefaultRootWindow
+XDefaultRootWindow
Both return the root window for the default screen.
@@ -753,8 +753,8 @@ Specifies the connection to the X server.
-
-
+DefaultScreenOfDisplay
+XDefaultScreenOfDisplay
Both return a pointer to the default screen.
@@ -798,8 +798,8 @@ Specifies the appropriate screen number on the host server.
-
-
+ScreenOfDisplay
+XScreenOfDisplay
Both return a pointer to the indicated screen.
@@ -832,8 +832,8 @@ Specifies the connection to the X server.
-
-
+DefaultScreen
+XDefaultScreen
Both return the default screen number referenced by the
XOpenDisplay
function.
@@ -881,8 +881,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DefaultVisual
+XDefaultVisual
Both return the default visual type for the specified screen.
For further information about visual types,
see section 3.1.
@@ -928,8 +928,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DisplayCells
+XDisplayCells
Both return the number of entries in the default colormap.
@@ -973,8 +973,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DisplayPlanes
+XDisplayPlanes
Both return the depth of the root window of the specified screen.
For an explanation of depth,
see the glossary.
@@ -1009,15 +1009,15 @@ Specifies the connection to the X server.
-
-
+DisplayString
+XDisplayString
Both return the string that was passed to
XOpenDisplay
when the current display was opened.
On POSIX-conformant systems,
if the passed string was NULL, these return the value of
the DISPLAY environment variable when the current display was opened.
-
+POSIX System Callfork
These are useful to applications that invoke the
fork
system call and want to open a new connection to the same display from the
@@ -1053,7 +1053,7 @@ Specifies the connection to the X server.
-
+XExtendedMaxRequestSize
The
XExtendedMaxRequestSize
function returns zero if the specified display does not support an
@@ -1110,7 +1110,7 @@ Specifies the connection to the X server.
-
+XMaxRequestSize
The
XMaxRequestSize
function returns the maximum request size (in 4-byte units) supported
@@ -1159,8 +1159,8 @@ Specifies the connection to the X server.
-
-
+LastKnownRequestProcessed
+XLastKnownRequestProcessed
Both extract the full serial number of the last request known by Xlib
to have been processed by the X server.
Xlib automatically sets this number when replies, events, and errors
@@ -1196,8 +1196,8 @@ Specifies the connection to the X server.
-
-
+NextRequest
+XNextRequest
Both extract the full serial number that is to be used for the next
request.
Serial numbers are maintained separately for each display connection.
@@ -1232,8 +1232,8 @@ Specifies the connection to the X server.
-
-
+ProtocolVersion
+XProtocolVersion
Both return the major version number (11) of the X protocol associated with
the connected display.
@@ -1267,8 +1267,8 @@ Specifies the connection to the X server.
-
-
+ProtocolRevision
+XProtocolRevision
Both return the minor protocol revision number of the X server.
@@ -1301,8 +1301,8 @@ Specifies the connection to the X server.
-
-
+QLength
+XQLength
Both return the length of the event queue for the connected display.
Note that there may be more events that have not been read into
the queue yet (see
@@ -1349,10 +1349,10 @@ Specifies the appropriate screen number on the host server.
-
-
-
-
+WindowRootWindow
+RootWindow
+WindowXRootWindow
+XRootWindow
Both return the root window.
These are useful with functions that need a drawable of a particular screen
and for creating top-level windows.
@@ -1387,8 +1387,8 @@ Specifies the connection to the X server.
-
-
+ScreenCount
+XScreenCount
Both return the number of available screens.
@@ -1421,8 +1421,8 @@ Specifies the connection to the X server.
-
-
+ServerVendor
+XServerVendor
Both return a pointer to a null-terminated string that provides
some identification of the owner of the X server implementation.
If the data returned by the server is in the Latin Portable Character Encoding,
@@ -1459,8 +1459,8 @@ Specifies the connection to the X server.
-
-
+VendorRelease
+XVendorRelease
Both return a number related to a vendor's release of the X server.
@@ -1504,7 +1504,7 @@ typedef struct {
To obtain the pixmap format information for a given display, use
XListPixmapFormats .
-
+XListPixmapFormats
@@ -1595,8 +1595,8 @@ Specifies the connection to the X server.
-
-
+ImageByteOrder
+XImageByteOrder
Both specify the required byte order for images for each scanline unit in
XY format (bitmap) or for each pixel value in
Z format.
@@ -1635,8 +1635,8 @@ Specifies the connection to the X server.
-
-
+BitmapUnit
+XBitmapUnit
Both return the size of a bitmap's scanline unit in bits.
The scanline is calculated in multiples of this value.
@@ -1670,8 +1670,8 @@ Specifies the connection to the X server.
-
-
+BitmapBitOrder
+XBitmapBitOrder
Within each bitmap unit, the left-most bit in the bitmap as displayed
on the screen is either the least significant or most significant bit in the
unit.
@@ -1710,8 +1710,8 @@ Specifies the connection to the X server.
-
-
+BitmapPad
+XBitmapPad
Each scanline must be padded to a multiple of bits returned
by this macro or function.
@@ -1756,8 +1756,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DisplayHeight
+XDisplayHeight
Both return an integer that describes the height of the screen
in pixels.
@@ -1802,8 +1802,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DisplayHeightMM
+XDisplayHeightMM
Both return the height of the specified screen in millimeters.
@@ -1847,8 +1847,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DisplayWidth
+XDisplayWidth
Both return the width of the screen in pixels.
@@ -1892,8 +1892,8 @@ Specifies the appropriate screen number on the host server.
-
-
+DisplayWidthMM
+XDisplayWidthMM
Both return the width of the specified screen in millimeters.
@@ -1942,8 +1942,8 @@ structure.
-
-
+BlackPixelOfScreen
+XBlackPixelOfScreen
Both return the black pixel value of the specified screen.
@@ -1978,8 +1978,8 @@ structure.
-
-
+WhitePixelOfScreen
+XWhitePixelOfScreen
Both return the white pixel value of the specified screen.
@@ -2014,8 +2014,8 @@ structure.
-
-
+CellsOfScreen
+XCellsOfScreen
Both return the number of colormap cells in the default colormap
of the specified screen.
@@ -2051,8 +2051,8 @@ structure.
-
-
+DefaultColormapOfScreen
+XDefaultColormapOfScreen
Both return the default colormap of the specified screen.
@@ -2087,8 +2087,8 @@ structure.
-
-
+DefaultDepthOfScreen
+XDefaultDepthOfScreen
Both return the depth of the root window.
@@ -2123,8 +2123,8 @@ structure.
-
-
+DefaultGCOfScreen
+XDefaultGCOfScreen
Both return a default graphics context (GC) of the specified screen,
which has the same depth as the root window of the screen.
The GC must never be freed.
@@ -2161,8 +2161,8 @@ structure.
-
-
+DefaultVisualOfScreen
+XDefaultVisualOfScreen
Both return the default visual of the specified screen.
For information on visual types,
see section 3.1.
@@ -2199,8 +2199,8 @@ structure.
-
-
+DoesBackingStore
+XDoesBackingStore
Both return a value indicating whether the screen supports backing
stores.
The value returned can be one of
@@ -2242,8 +2242,8 @@ structure.
-
-
+DoesSaveUnders
+XDoesSaveUnders
Both return a Boolean value indicating whether the
screen supports save unders.
If
@@ -2285,15 +2285,15 @@ structure.
-
-
+DisplayOfScreen
+XDisplayOfScreen
Both return the display of the specified screen.
-
+XScreenNumberOfScreen
EventMaskOfScreen(screen)
@@ -2358,8 +2358,8 @@ structure.
-
-
+EventMaskOfScreen
+XEventMaskOfScreen
Both return the event mask of the root window for the specified screen
at connection setup time.
@@ -2395,8 +2395,8 @@ structure.
-
-
+WidthOfScreen
+XWidthOfScreen
Both return the width of the specified screen in pixels.
@@ -2431,8 +2431,8 @@ structure.
-
-
+HeightOfScreen
+XHeightOfScreen
Both return the height of the specified screen in pixels.
@@ -2467,8 +2467,8 @@ structure.
-
-
+WidthMMOfScreen
+XWidthMMOfScreen
Both return the width of the specified screen in millimeters.
@@ -2503,8 +2503,8 @@ structure.
-
-
+HeightMMOfScreen
+XHeightMMOfScreen
Both return the height of the specified screen in millimeters.
@@ -2539,8 +2539,8 @@ structure.
-
-
+MaxCmapsOfScreen
+XMaxCmapsOfScreen
Both return the maximum number of installed colormaps supported
by the specified screen (see section 9.3).
@@ -2576,8 +2576,8 @@ structure.
-
-
+MinCmapsOfScreen
+XMinCmapsOfScreen
Both return the minimum number of installed colormaps supported
by the specified screen (see section 9.3).
@@ -2613,8 +2613,8 @@ structure.
-
-
+PlanesOfScreen
+XPlanesOfScreen
Both return the depth of the root window.
@@ -2649,8 +2649,8 @@ structure.
-
-
+RootWindowOfScreen
+XRootWindowOfScreen
Both return the root window of the specified screen.
@@ -2666,7 +2666,7 @@ To execute a
NoOperation
protocol request, use
XNoOp .
-
+XNoOp
@@ -2704,7 +2704,7 @@ thereby exercising the connection.
To free in-memory data that was created by an Xlib function, use
XFree .
-
+XFree
@@ -2747,7 +2747,7 @@ A NULL pointer cannot be passed to this function.
To close a display or disconnect from the X server, use
XCloseDisplay .
-
+XCloseDisplay
@@ -2801,8 +2801,8 @@ explicitly so that any pending errors are reported as
performs a final
XSync
operation.
-
-
+Resource IDs
+XCloseDisplay
@@ -2818,7 +2818,7 @@ Xlib provides a function to permit the resources owned by a client
to survive after the client's connection is closed.
To change a client's close-down mode, use
XSetCloseDownMode .
-
+XSetCloseDownMode
@@ -3070,7 +3070,7 @@ multiple threads to use Xlib concurrently.
To initialize support for concurrent threads, use
XInitThreads .
-
+XInitThreads
Status XInitThreads();
@@ -3103,7 +3103,7 @@ It is recommended that single-threaded programs not call this function.
To lock a display across several Xlib calls, use
XLockDisplay .
-
+XLockDisplay
@@ -3148,7 +3148,7 @@ for threads using
To unlock a display, use
XUnlockDisplay .
-
+XUnlockDisplay
@@ -3306,7 +3306,7 @@ thread has externally locked the display using
To stop tracking internal connections for a display, use
XRemoveConnectionWatch .
-
+XRemoveConnectionWatch
@@ -3368,7 +3368,7 @@ was initially registered.
To process input on an internal connection, use
XProcessInternalConnection .
-
+XProcessInternalConnection
@@ -3423,7 +3423,7 @@ the effect is not defined.
To obtain all of the current internal connections for a display, use
XInternalConnectionNumbers .
-
+XInternalConnectionNumbers
diff --git a/specs/libX11/CH03.xml b/specs/libX11/CH03.xml
index 7890b6dd..26405e30 100644
--- a/specs/libX11/CH03.xml
+++ b/specs/libX11/CH03.xml
@@ -6,7 +6,7 @@
-
+Visual Type
On some display hardware,
it may be possible to deal with color resources in more than one way.
For example, you may be able to deal with a screen of either 12-bit depth
@@ -26,7 +26,7 @@ the default depth of the default root window, and the default visual type
Xlib uses an opaque
Visual
-
+Visual
structure that contains information about the possible color mapping.
The visual utility functions (see section 16.7) use an
XVisualInfo
@@ -35,12 +35,12 @@ The members of this structure pertinent to this discussion are class, red_mask,
green_mask, blue_mask, bits_per_rgb, and colormap_size.
The class member specifies one of the possible visual classes of the screen
and can be
-
-
-
-
-
-
+Visual ClassesStaticGray
+Visual ClassesStaticColor
+Visual ClassesTrueColor
+Visual ClassesStaticColor
+Visual ClassesGrayScale
+Visual ClassesPseudoColor
StaticGray ,
StaticColor ,
TrueColor ,
@@ -171,7 +171,7 @@ To obtain the visual ID from a
Visual ,
use
XVisualIDFromVisual .
-
+XVisualIDFromVisual
@@ -208,8 +208,8 @@ function returns the visual ID for the specified visual type.
-
-
+Window
+Windowattributes
All
InputOutput
windows have a border width of zero or more pixels, an optional background,
@@ -297,14 +297,14 @@ windows as inferiors.
Windows have borders of a programmable width and pattern
as well as a background pattern or tile.
-
+Tilepixmaps
Pixel values can be used for solid colors.
-
-
+Resource IDsfreeing
+Freeingresources
The background and border pixmaps can be destroyed immediately after
creating the window if no further explicit references to them
are to be made.
-
+Tilemode
The pattern can either be relative to the parent
or absolute.
If
@@ -317,13 +317,13 @@ When windows are first created,
they are not visible (not mapped) on the screen.
Any output to a window that is not visible on the screen
and that does not have backing store will be discarded.
-
+Windowmapping
An application may wish to create a window long before it is
mapped to the screen.
When a window is eventually mapped to the screen
(using
XMapWindow ),
-
+XMapWindow
the X server generates an
Expose
event for the window if backing store has not been maintained.
@@ -382,7 +382,7 @@ structure are:
#define CWCursor (1L<<14)
-
+XSetWindowAttributes
@@ -933,7 +933,7 @@ However, regions obscured by inferior windows are not included.
-
+Save Unders
Some server implementations may preserve contents of
@@ -1214,7 +1214,7 @@ creates a window that inherits its attributes from its parent window.
-
+WindowInputOnly
The X server acts as if
InputOnly
windows do not exist for
@@ -1236,7 +1236,7 @@ Extension packages can define other classes of windows.
To create an unmapped window and set its window attributes, use
XCreateWindow .
-
+XCreateWindow
@@ -1475,8 +1475,8 @@ The new window initially uses the same cursor as
its parent.
A new cursor can be defined for the new window by calling
XDefineCursor .
-
-
+CursorInitial State
+XDefineCursor
The window will not be visible on the screen unless it and all of its
ancestors are mapped and it is not obscured by any of its ancestors.
@@ -1501,7 +1501,7 @@ To create an unmapped
InputOutput
subwindow of a given parent window, use
XCreateSimpleWindow .
-
+XCreateSimpleWindow
@@ -1671,7 +1671,7 @@ subwindows of a window.
To destroy a window and all of its subwindows, use
XDestroyWindow .
-
+XDestroyWindow
@@ -1741,7 +1741,7 @@ error.
To destroy all subwindows of a specified window, use
XDestroySubwindows .
-
+XDestroySubwindows
@@ -1884,7 +1884,7 @@ event.
To map a given window, use
XMapWindow .
-
+XMapWindow
@@ -1969,7 +1969,7 @@ Similar tiling and exposure take place for any newly viewable inferiors.
-
+XMapWindow
If the window is an
InputOutput
window,
@@ -2010,7 +2010,7 @@ error.
To map and raise a window, use
XMapRaised .
-
+XMapRaised
@@ -2070,7 +2070,7 @@ errors.
To map all subwindows for a specified window, use
XMapSubwindows .
-
+XMapSubwindows
@@ -2108,7 +2108,7 @@ Specifies the window.
The
XMapSubwindows
-
+XMapSubwindows
function maps all subwindows for a specified window in top-to-bottom stacking
order.
The X server generates
@@ -2140,7 +2140,7 @@ Xlib provides functions that you can use to unmap a window or all subwindows.
To unmap a window, use
XUnmapWindow .
-
+XUnmapWindow
@@ -2180,8 +2180,8 @@ The
XUnmapWindow
function unmaps the specified window and causes the X server to generate an
UnmapNotify
-
-
+UnmapNotify Event
+XUnmapWindow
event.
If the specified window is already unmapped,
XUnmapWindow
@@ -2207,7 +2207,7 @@ error.
To unmap all subwindows for a specified window, use
XUnmapSubwindows .
-
+XUnmapSubwindows
@@ -2252,7 +2252,7 @@ It causes the X server to generate an
event on each subwindow and
Expose
events on formerly obscured windows.
-
+UnmapNotify Event
Using this function is much more efficient than unmapping multiple windows
one at a time because the server needs to perform much of the work
only once, for all of the windows, rather than for each window.
@@ -2302,7 +2302,7 @@ structure are:
#define CWStackMode (1<<6)
-
+XWindowChanges
/* Values */
@@ -2512,7 +2512,7 @@ Attempts to configure a root window have no effect.
To configure a window's size, location, stacking, or border, use
XConfigureWindow .
-
+XConfigureWindow
@@ -2618,7 +2618,7 @@ errors.
To move a window without changing its size, use
XMoveWindow .
-
+XMoveWindow
@@ -2720,7 +2720,7 @@ error.
To change a window's size without changing the upper-left coordinate, use
XResizeWindow .
-
+XResizeWindow
@@ -2823,7 +2823,7 @@ errors.
To change the size and location of a window, use
XMoveResizeWindow .
-
+XMoveResizeWindow
@@ -2944,7 +2944,7 @@ errors.
To change the border width of a given window, use
XSetWindowBorderWidth .
-
+XSetWindowBorderWidth
@@ -3021,7 +3021,7 @@ or restack windows.
To raise a window so that no sibling window obscures it, use
XRaiseWindow .
-
+XRaiseWindow
@@ -3094,7 +3094,7 @@ error.
To lower a window so that it does not obscure any sibling windows, use
XLowerWindow .
-
+XLowerWindow
@@ -3168,7 +3168,7 @@ error.
To circulate a subwindow up or down, use
XCirculateSubwindows .
-
+XCirculateSubwindows
@@ -3260,7 +3260,7 @@ errors.
To raise the lowest mapped child of a window that is partially or completely
occluded by another child, use
XCirculateSubwindowsUp .
-
+XCirculateSubwindowsUp
@@ -3322,7 +3322,7 @@ error.
To lower the highest mapped child of a window that partially or
completely occludes another child, use
XCirculateSubwindowsDown .
-
+XCirculateSubwindowsDown
@@ -3381,7 +3381,7 @@ error.
To restack a set of windows from top to bottom, use
XRestackWindows .
-
+XRestackWindows
@@ -3487,7 +3487,7 @@ window attribute, such as a window's background.
To change one or more attributes for a given window, use
XChangeWindowAttributes .
-
+XChangeWindowAttributes
@@ -3645,7 +3645,7 @@ errors.
To set the background of a window to a given pixel, use
XSetWindowBackground .
-
+XSetWindowBackground
@@ -3721,8 +3721,8 @@ errors.
To set the background of a window to a given pixmap, use
XSetWindowBackgroundPixmap .
-
-
+Windowbackground
+XSetWindowBackgroundPixmap
@@ -3772,8 +3772,8 @@ or
-
-
+Resource IDsfreeing
+Freeingresources
The
XSetWindowBackgroundPixmap
function sets the background pixmap of the window to the specified pixmap.
@@ -3814,7 +3814,7 @@ do not change the current contents of the window.
To change and repaint a window's border to a given pixel, use
XSetWindowBorder .
-
+XSetWindowBorder
@@ -3884,7 +3884,7 @@ errors.
To change and repaint the border tile of a given window, use
XSetWindowBorderPixmap .
-
+XSetWindowBorderPixmap
@@ -3945,8 +3945,8 @@ If you attempt to perform this on an
window, a
BadMatch
error results.
-
-
+Resource IDsfreeing
+Freeingresources
@@ -3963,7 +3963,7 @@ errors.
To set the colormap of a given window, use
XSetWindowColormap .
-
+XSetWindowColormap
@@ -4033,8 +4033,8 @@ errors.
To define which cursor will be used in a window, use
XDefineCursor .
-
-
+Windowdefining the cursor
+XDefineCursor
@@ -4102,8 +4102,8 @@ errors.
To undefine the cursor in a given window, use
XUndefineCursor .
-
-
+Windowundefining the cursor
+XUndefineCursor
diff --git a/specs/libX11/CH04.xml b/specs/libX11/CH04.xml
index 6a0dad8a..e29c5ff1 100644
--- a/specs/libX11/CH04.xml
+++ b/specs/libX11/CH04.xml
@@ -33,9 +33,9 @@ exists.
To obtain the parent, a list of children, and number of children for
a given window, use
XQueryTree .
-
-
-
+Child Window
+Parent Window
+XQueryTree
@@ -142,7 +142,7 @@ error.
To obtain the current attributes of a given window, use
XGetWindowAttributes .
-
+XGetWindowAttributes
@@ -200,7 +200,7 @@ structure.
-
+XWindowAttributes
@@ -402,7 +402,7 @@ errors.
To obtain the current geometry of a given drawable, use
XGetGeometry .
-
+XGetGeometry
@@ -563,7 +563,7 @@ asking the X server to perform these operations.
To translate a coordinate in one window to the coordinate
space of another window, use
XTranslateCoordinates .
-
+XTranslateCoordinates
@@ -697,7 +697,7 @@ error.
To obtain the screen coordinates of the pointer
or to determine the pointer coordinates relative to a specified window, use
XQueryPointer .
-
+XQueryPointer
@@ -868,7 +868,7 @@ error.
A property is a collection of named, typed data.
The window system has a set of predefined properties
-
+Atompredefined
(for example, the name of a window, size hints, and so on), and users can
define any other arbitrary information and associate it with windows.
Each property has a name,
@@ -885,7 +885,7 @@ For efficiency reasons,
an atom is used rather than a character string.
XInternAtom
can be used to obtain the atom for property names.
-
+Atom
@@ -903,7 +903,7 @@ see appendix C.
The type of a property is defined by an atom, which allows for
arbitrary extension in this type scheme.
-
+Atom
@@ -1184,8 +1184,8 @@ see section 8.5.
To return an atom for a given name, use
XInternAtom .
-
-
+Atominterning
+XInternAtom
@@ -1266,8 +1266,8 @@ errors.
To return atoms for an array of names, use
XInternAtoms .
-
-
+Atominterning
+XInternAtoms
@@ -1367,8 +1367,8 @@ errors.
To return a name for a given atom identifier, use
XGetAtomName .
-
-
+Atomgetting name
+XGetAtomName
@@ -1426,8 +1426,8 @@ error.
To return the names for an array of atom identifiers, use
XGetAtomNames .
-
-
+Atomgetting name
+XGetAtomNames
@@ -1540,11 +1540,11 @@ communication (see chapter 14).
To obtain the type, format, and value of a property of a given window, use
XGetWindowProperty .
-
+Propertygetting
-
+XGetWindowProperty
@@ -1823,8 +1823,8 @@ errors.
To obtain a given window's property list, use
XListProperties .
-
-
+Propertylisting
+XListProperties
@@ -1891,13 +1891,13 @@ error.
To change a property of a given window, use
XChangeProperty .
-
-
-
-
-
-
-
+Propertychanging
+Propertyappending
+Propertyprepending
+Propertyreplacing
+Propertyformat
+Propertytype
+XChangeProperty
@@ -2098,7 +2098,7 @@ To rotate a window's property list, use
-
+XRotateWindowProperties
@@ -2211,8 +2211,8 @@ errors.
To delete a property on a given window, use
XDeleteProperty .
-
-
+Propertydeleting
+XDeleteProperty
@@ -2285,7 +2285,7 @@ errors.
-
+Selection
Selections are one method used by applications to exchange data.
By using the property mechanism,
applications can exchange data of arbitrary types and can negotiate
@@ -2334,8 +2334,8 @@ The protocol does not constrain the semantics.
To set the selection owner, use
XSetSelectionOwner .
-
-
+Selectionsetting the owner
+XSetSelectionOwner
@@ -2457,8 +2457,8 @@ errors.
To return the selection owner, use
XGetSelectionOwner .
-
-
+Selectiongetting the owner
+XGetSelectionOwner
@@ -2519,8 +2519,8 @@ error.
To request conversion of a selection, use
XConvertSelection .
-
-
+Selectionconverting
+XConvertSelection
diff --git a/specs/libX11/CH05.xml b/specs/libX11/CH05.xml
index 41a70bdc..5aa6cfaf 100644
--- a/specs/libX11/CH05.xml
+++ b/specs/libX11/CH05.xml
@@ -19,7 +19,7 @@ A bitmap is a single bit-plane pixmap.
To create a pixmap of a given size, use
XCreatePixmap .
-
+XCreatePixmap
@@ -131,7 +131,7 @@ errors.
To free all storage associated with a specified pixmap, use
XFreePixmap .
-
+XFreePixmap
@@ -206,7 +206,7 @@ The hotspot defines the point on the cursor that is reported
when a pointer event occurs.
There may be limitations imposed by the hardware on
cursors as to size and whether a mask is implemented.
-
+XQueryBestCursor
XQueryBestCursor
can be used to find out what sizes are possible.
There is a standard font for creating cursors, but
@@ -223,7 +223,7 @@ To create a cursor from the standard cursor font, use
#include <X11/cursorfont.h>
-
+XCreateFontCursor
@@ -290,7 +290,7 @@ errors.
To create a cursor from font glyphs, use
XCreateGlyphCursor .
-
+XCreateGlyphCursor
@@ -429,7 +429,7 @@ errors.
To create a cursor from two bitmaps,
use
XCreatePixmapCursor .
-
+XCreatePixmapCursor
@@ -576,7 +576,7 @@ errors.
To determine useful cursor sizes, use
XQueryBestCursor .
-
+XQueryBestCursor
@@ -664,7 +664,7 @@ The
XQueryBestCursor
function provides a way to find out what size cursors are actually
possible on the display.
-
+Cursorlimitations
It returns the largest size that can be displayed.
Applications should be prepared to use smaller cursors on displays that
cannot support large ones.
@@ -681,7 +681,7 @@ error.
To change the color of a given cursor, use
XRecolorCursor .
-
+XRecolorCursor
@@ -759,7 +759,7 @@ error.
To free (destroy) a given cursor, use
XFreeCursor .
-
+XFreeCursor
diff --git a/specs/libX11/CH06.xml b/specs/libX11/CH06.xml
index ffd558be..f61020fd 100644
--- a/specs/libX11/CH06.xml
+++ b/specs/libX11/CH06.xml
@@ -154,7 +154,7 @@ The
DefaultVisual
macro
returns the default visual type for the specified screen.
-
+Color map
Possible visual types are
StaticGray ,
GrayScale ,
@@ -178,7 +178,7 @@ structure, which contains:
-
+XColor
@@ -200,7 +200,7 @@ display hardware.
The server scales these values down to the range used by the hardware.
Black is represented by (0,0,0),
and white is represented by (65535,65535,65535).
-
+Color
In some functions,
the flags member controls which of the red, green, and blue members is used
and can be the inclusive OR of zero or more of
@@ -225,7 +225,7 @@ structure contains pixel
and color specification information (the spec member in the
XcmsColor
structure).
-
+XcmsColor
@@ -301,7 +301,7 @@ and
Data types that describe the color specification encoding for the various
color spaces are defined as follows:
-
+XcmsRGB
@@ -316,7 +316,7 @@ typedef struct {
unsigned short blue; /* 0x0000 to 0xffff */
} XcmsRGB; /* RGB Device */
-
+XcmsRGBi
@@ -329,7 +329,7 @@ typedef struct {
XcmsFloat blue; /* 0.0 to 1.0 */
} XcmsRGBi; /* RGB Intensity */
-
+XcmsCIEXYZ
@@ -342,7 +342,7 @@ typedef struct {
XcmsFloat Z;
} XcmsCIEXYZ; /* CIE XYZ */
-
+XcmsCIEuvY
@@ -355,7 +355,7 @@ typedef struct {
XcmsFloat Y; /* 0.0 to 1.0 */
} XcmsCIEuvY; /* CIE u'v'Y */
-
+XcmsCIExyY
@@ -368,7 +368,7 @@ typedef struct {
XcmsFloat Y; /* 0.0 to 1.0 */
} XcmsCIExyY; /* CIE xyY */
-
+XcmsCIELab
@@ -381,7 +381,7 @@ typedef struct {
XcmsFloat b_star;
} XcmsCIELab; /* CIE L*a*b* */
-
+XcmsCIELuv
@@ -394,7 +394,7 @@ typedef struct {
XcmsFloat v_star;
} XcmsCIELuv; /* CIE L*u*v* */
-
+XcmsTekHVC
@@ -407,7 +407,7 @@ typedef struct {
XcmsFloat C; /* 0.0 to 100.0 */
} XcmsTekHVC; /* TekHVC */
-
+XcmsPad
@@ -697,10 +697,10 @@ When Xlib converts device-independent color specifications
into device-dependent specifications and vice versa,
it uses knowledge about the color limitations of the screen hardware.
This information, typically called the device profile,
-
+Device profile
is available in a Color Conversion Context (CCC).
-
-
+Color Conversion Context
+CCC
@@ -708,7 +708,7 @@ Because a specified color may be outside the color gamut of the target screen
and the white point associated with the color specification may differ
from the white point inherent to the screen,
Xlib applies gamut mapping when it encounters certain conditions:
-
+White point
@@ -732,10 +732,10 @@ which in turn are used by the color space conversion routines.
Client data is also stored in the CCC for each callback.
The CCC also contains the white point the client assumes to be
associated with color specifications (that is, the Client White Point).
-
-
-
-
+Client White Point
+Gamut compression
+Gamut handling
+White point adjustment
The client can specify the gamut handling callbacks and client data
as well as the Client White Point.
Xlib does not preclude the X client from performing other
@@ -747,17 +747,17 @@ other than white adjustment and gamut compression.
Associated with each colormap is an initial CCC transparently generated by
Xlib.
-
+Color Conversion Contextcreation
Therefore,
when you specify a colormap as an argument to an Xlib function,
you are indirectly specifying a CCC.
-
-
+CCCof colormap
+Color Conversion Contextof colormap
There is a default CCC associated with each screen.
Newly created CCCs inherit attributes from the default CCC,
so the default CCC attributes can be modified to affect new CCCs.
-
-
+CCCdefault
+Color Conversion Contextdefault
@@ -803,7 +803,7 @@ or in the CCC indirectly specified by means of the colormap argument.
To create a colormap for a screen, use
XCreateColormap .
-
+XCreateColormap
@@ -952,7 +952,7 @@ errors.
To create a new colormap when the allocation out of a previously
shared colormap has failed because of resource exhaustion, use
XCopyColormapAndFree .
-
+XCopyColormapAndFree
@@ -1028,7 +1028,7 @@ errors.
To destroy a colormap, use
XFreeColormap .
-
+XFreeColormap
@@ -1106,8 +1106,8 @@ error.
To map a color name to an RGB value, use
XLookupColor .
-
-
+Colornaming
+XLookupColor
@@ -1204,8 +1204,8 @@ error.
To map a color name to the exact RGB value, use
XParseColor .
-
-
+Colornaming
+XParseColor
@@ -1294,8 +1294,8 @@ error.
To map a color name to a value in an arbitrary color space, use
XcmsLookupColor .
-
-
+Colornaming
+XcmsLookupColor
@@ -1424,9 +1424,9 @@ There are two ways of allocating color cells:
explicitly as read-only entries, one pixel value at a time,
or read/write,
where you can allocate a number of color cells and planes simultaneously.
-
+Read-only colormap cells
A read-only cell has its RGB value set by the server.
-
+Read/write colormap cells
Read/write cells do not have defined colors initially;
functions described in the next section must be used to store values into them.
Although it is possible for any client to store values into a read/write
@@ -1448,10 +1448,10 @@ times, the server counts each such allocation, not just the first one.
To allocate a read-only color cell with an RGB value, use
XAllocColor .
-
-
-
-
+Allocationread-only colormap cells
+Read-only colormap cellsallocating
+Colorallocation
+XAllocColor
@@ -1510,10 +1510,10 @@ The corresponding colormap cell is read-only.
In addition,
XAllocColor
returns nonzero if it succeeded or zero if it failed.
-
-
-
-
+Color map
+Colorallocation
+Allocationcolormap
+read-only colormap cells
Multiple clients that request the same effective RGB value can be assigned
the same read-only entry, thus allowing entries to be shared.
When the last client deallocates a shared cell, it is deallocated.
@@ -1538,10 +1538,10 @@ delim %%
To allocate a read-only color cell with a color in arbitrary format, use
XcmsAllocColor .
-
-
-
-
+Allocationread-only colormap cells
+Read-only colormap cellsallocating
+Colorallocation
+XcmsAllocColor
@@ -1642,11 +1642,11 @@ To allocate a read-only color cell using a color name and return the closest
color supported by the hardware in RGB format, use
XAllocNamedColor .
-
-
-
-
-
+Allocationread-only colormap cells
+Read-only colormap cellsallocating
+Colornaming
+Colorallocation
+XAllocNamedColor
@@ -1747,11 +1747,11 @@ To allocate a read-only color cell using a color name and return the closest
color supported by the hardware in an arbitrary format, use
XcmsAllocNamedColor .
-
-
-
-
-
+Allocationread-only colormap cells
+Read-only colormap cellsallocating
+Colornaming
+Colorallocation
+XcmsAllocNamedColor
@@ -1897,10 +1897,10 @@ To allocate read/write color cell and color plane combinations for a
model, use
XAllocColorCells .
-
-
-
-
+Read/write colormap cellsallocating
+Allocationread/write colormap cells
+Colorallocation
+XAllocColorCells
@@ -2053,10 +2053,10 @@ To allocate read/write color resources for a
model, use
XAllocColorPlanes .
-
-
-
-
+Read/write colormap planesallocating
+Allocationread/write colormap planes
+Colorallocation
+XAllocColorPlanes
@@ -2251,11 +2251,11 @@ errors.
-
+Freeingcolors
To free colormap cells, use
XFreeColors .
-
-
+XFreeColors
+Colordeallocation
@@ -2336,10 +2336,10 @@ The set of all pixels is produced by ORing together subsets of
the planes argument with the pixels.
The request frees all of these pixels that
were allocated by the client (using
-
-
-
-
+XAllocColor
+XAllocNamedColor
+XAllocColorCells
+XAllocColorPlanes
XAllocColor ,
XAllocNamedColor ,
XAllocColorCells ,
@@ -2396,8 +2396,8 @@ errors.
To store an RGB value in a single colormap cell, use
XStoreColor .
-
-
+Colorstoring
+XStoreColor
@@ -2488,8 +2488,8 @@ errors.
To store multiple RGB values in multiple colormap cells, use
XStoreColors .
-
-
+Colorstoring
+XStoreColors
@@ -2594,8 +2594,8 @@ errors.
To store a color of arbitrary format in a single colormap cell, use
XcmsStoreColor .
-
-
+Colorstoring
+XcmsStoreColor
@@ -2705,8 +2705,8 @@ errors.
To store multiple colors of arbitrary format in multiple colormap cells, use
XcmsStoreColors .
-
-
+Colorstoring
+XcmsStoreColors
@@ -2849,9 +2849,9 @@ errors.
To store a color specified by name in a single colormap cell, use
XStoreNamedColor .
-
-
-
+Colorstoring
+Colornaming
+XStoreNamedColor
@@ -2980,8 +2980,8 @@ the one that gets reported is arbitrary.
To query the RGB value of a single colormap cell, use
XQueryColor .
-
-
+Colorquerying
+XQueryColor
@@ -3054,8 +3054,8 @@ errors.
To query the RGB values of multiple colormap cells, use
XQueryColors .
-
-
+Colorquerying
+XQueryColors
@@ -3144,8 +3144,8 @@ errors.
To query the color of a single colormap cell in an arbitrary format, use
XcmsQueryColor .
-
-
+Colorquerying
+XcmsQueryColor
@@ -3233,8 +3233,8 @@ errors.
To query the color of multiple colormap cells in an arbitrary format, use
XcmsQueryColors .
-
-
+Colorquerying
+XcmsQueryColors
@@ -3346,11 +3346,11 @@ and query Color Conversion Contexts (CCCs).
Associated with each colormap is an initial CCC transparently generated by
Xlib.
-
+Color Conversion Contextcreation
Therefore, when you specify a colormap as an argument to a function,
you are indirectly specifying a CCC.
-
-
+CCCof colormap
+Color Conversion Contextof colormap
The CCC attributes that can be modified by the X client are:
@@ -3375,8 +3375,8 @@ White point adjustment procedure and client data
The initial values for these attributes are implementation specific.
The CCC attributes for subsequently created CCCs can be defined
by changing the CCC attributes of the default CCC.
-
-
+CCCdefault
+Color Conversion Contextdefault
There is a default CCC associated with each screen.
@@ -3390,10 +3390,10 @@ There is a default CCC associated with each screen.
To obtain the CCC associated with a colormap, use
XcmsCCCOfColormap .
-
-
-
-
+XcmsCCCOfColormap
+ColormapCCC of
+CCCof colormap
+Color Conversion Contextof colormap
@@ -3445,10 +3445,10 @@ to color functions.
To change the CCC associated with a colormap, use
XcmsSetCCCOfColormap .
-
-
-
-
+XcmsSetCCCOfColormap
+ColormapCCC of
+CCCof colormap
+Color Conversion Contextof colormap
@@ -3516,8 +3516,8 @@ creates a new CCC with each new colormap.
You can change the default CCC attributes for subsequently created CCCs
by changing the CCC attributes of the default CCC.
-
-
+CCCdefault
+Color Conversion Contextdefault
A default CCC is associated with each screen.
@@ -3526,9 +3526,9 @@ A default CCC is associated with each screen.
To obtain the default CCC for a screen, use
XcmsDefaultCCC .
-
-
-
+XcmsDefaultCCC
+Color Conversion Contextdefault
+CCCdefault
@@ -3588,8 +3588,8 @@ can return.
-
-
+DisplayOfCCC
+XcmsDisplayOfCCC
@@ -3626,8 +3626,8 @@ Both return the display associated with the specified CCC.
-
-
+VisualOfCCC
+XcmsVisualOfCCC
@@ -3663,8 +3663,8 @@ Both return the visual associated with the specified CCC.
-
-
+ScreenNumberOfCCC
+XcmsScreenNumberOfCCC
@@ -3700,8 +3700,8 @@ Both return the number of the screen associated with the specified CCC.
-
-
+ScreenWhitePointOfCCC
+XcmsScreenWhitePointOfCCC
@@ -3736,8 +3736,8 @@ Both return the white point of the screen associated with the specified CCC.
-
-
+ClientWhitePointOfCCC
+XcmsClientWhitePointOfCCC
@@ -3783,8 +3783,8 @@ Both return the Client White Point of the specified CCC.
To set the Client White Point in the CCC, use
XcmsSetWhitePoint .
-
-
+XcmsSetWhitePoint
+Client White Pointof Color Conversion Context
@@ -3852,10 +3852,10 @@ To set the gamut compression procedure and corresponding client data
in a specified CCC, use
XcmsSetCompressionProc .
-
-
-
-
+XcmsSetCompressionProc
+Gamut compressionsetting in Color Conversion Context
+Gamut compressionprocedure
+Gamut compressionclient data
@@ -3922,10 +3922,10 @@ To set the white point adjustment procedure and corresponding client data
in a specified CCC, use
XcmsSetWhiteAdjustProc .
-
-
-
-
+XcmsSetWhiteAdjustProc
+White point adjustmentsetting in Color Conversion Context
+White point adjustmentprocedure
+White point adjustmentclient data
XcmsWhiteAdjustProc XcmsSetWhiteAdjustProc
@@ -3999,9 +3999,9 @@ Old CCCs that will not be used by the application should be freed using
To create a CCC, use
XcmsCreateCCC .
-
-
-
+XcmsCreateCCC
+Color Conversion Contextcreation
+CCCcreation
@@ -4126,9 +4126,9 @@ function creates a CCC for the specified display, screen, and visual.
To free a CCC, use
XcmsFreeCCC .
-
-
-
+XcmsFreeCCC
+Color Conversion Contextfreeing
+CCCfreeing
@@ -4173,9 +4173,9 @@ To convert an array of color specifications in arbitrary color formats
to a single destination format, use
XcmsConvertColors .
-
-
-
+Color conversion
+Colorconversion
+XcmsConvertColors
@@ -4319,7 +4319,7 @@ If required, the client data is obtained from the CCC.
The gamut compression callback interface must adhere to the
following:
-
+XcmsCompressionProc
@@ -4646,7 +4646,7 @@ No client data is necessary.
The white point adjustment procedure interface must adhere to the following:
-
+XcmsWhiteAdjustProc
@@ -4937,7 +4937,7 @@ This section describes the gamut querying functions that Xlib provides.
These functions allow the client to query the boundary
of the screen's color gamut in terms of the CIE L*a*b*, CIE L*u*v*,
and TekHVC color spaces.
-
+Gamut querying
Functions are also provided that allow you to query
the color specification of:
@@ -4973,7 +4973,7 @@ Black (zero-intensity red, green, and blue)
The white point associated with color specifications passed to
and returned from these gamut querying
functions is assumed to be the Screen White Point.
-
+Screen White Point
This is a reasonable assumption,
because the client is trying to query the screen's color gamut.
@@ -5009,7 +5009,7 @@ To obtain the color specification for black
(zero-intensity red, green, and blue), use
XcmsQueryBlack .
-
+XcmsQueryBlack
@@ -5075,7 +5075,7 @@ To obtain the color specification for blue
(full-intensity blue while red and green are zero), use
XcmsQueryBlue .
-
+XcmsQueryBlue
@@ -5141,7 +5141,7 @@ To obtain the color specification for green
(full-intensity green while red and blue are zero), use
XcmsQueryGreen .
-
+XcmsQueryGreen
@@ -5207,7 +5207,7 @@ To obtain the color specification for red
(full-intensity red while green and blue are zero), use
XcmsQueryRed .
-
+XcmsQueryRed
@@ -5273,7 +5273,7 @@ To obtain the color specification for white
(full-intensity red, green, and blue), use
XcmsQueryWhite .
-
+XcmsQueryWhite
@@ -5347,10 +5347,10 @@ delim %%
-
-
-
-
+Psychometric Hue Angle
+CIE metric lightness
+Psychometric Chroma
+Psychometric Chromamaximum
%CIELab~Psychometric~Chroma ~=~ sqrt(a_star sup 2 ~+~ b_star sup 2 )%
@@ -5361,7 +5361,7 @@ To obtain the CIE L*a*b* coordinates of maximum Psychometric Chroma
for a given Psychometric Hue Angle and CIE metric lightness (L*), use
XcmsCIELabQueryMaxC .
-
+XcmsCIELabQueryMaxC
@@ -5442,10 +5442,10 @@ To obtain the CIE L*a*b* coordinates of maximum CIE metric lightness (L*)
for a given Psychometric Hue Angle and Psychometric Chroma, use
XcmsCIELabQueryMaxL .
-
-
-
-
+Psychometric Hue Angle
+CIE metric lightness
+CIE metric lightnessmaximum
+XcmsCIELabQueryMaxL
@@ -5531,12 +5531,12 @@ To obtain the CIE L*a*b* coordinates of maximum Psychometric Chroma
for a given Psychometric Hue Angle, use
XcmsCIELabQueryMaxLC .
-
-
-
-
-
-
+Psychometric Hue Angle
+Psychometric Chroma
+CIE metric lightness
+Psychometric Chromamaximum
+CIE metric lightnessmaximum
+XcmsCIELabQueryMaxLC
@@ -5605,10 +5605,10 @@ To obtain the CIE L*a*b* coordinates of minimum CIE metric lightness (L*)
for a given Psychometric Hue Angle and Psychometric Chroma, use
XcmsCIELabQueryMinL .
-
-
-
-
+Psychometric Hue Angle
+CIE metric lightness
+CIE metric lightnessminimum
+XcmsCIELabQueryMinL
@@ -5701,10 +5701,10 @@ delim %%
-
-
-
-
+Psychometric Hue Angle
+CIE metric lightness
+Psychometric Chroma
+Psychometric Chromamaximum
%CIELuv~Psychometric~Chroma ~=~ sqrt(u_star sup 2 ~+~ v_star sup 2 )%
@@ -5718,7 +5718,7 @@ To obtain the CIE L*u*v* coordinates of maximum Psychometric Chroma
for a given Psychometric Hue Angle and CIE metric lightness (L*), use
XcmsCIELuvQueryMaxC .
-
+XcmsCIELuvQueryMaxC
@@ -5799,10 +5799,10 @@ To obtain the CIE L*u*v* coordinates of maximum CIE metric lightness (L*)
for a given Psychometric Hue Angle and Psychometric Chroma, use
XcmsCIELuvQueryMaxL .
-
-
-
-
+Psychometric Hue Angle
+CIE metric lightness
+CIE metric lightnessmaximum
+XcmsCIELuvQueryMaxL
@@ -5888,12 +5888,12 @@ To obtain the CIE L*u*v* coordinates of maximum Psychometric Chroma
for a given Psychometric Hue Angle, use
XcmsCIELuvQueryMaxLC .
-
-
-
-
-
-
+Psychometric Hue Angle
+Psychometric Chroma
+CIE metric lightness
+Psychometric Chromamaximum
+CIE metric lightnessmaximum
+XcmsCIELuvQueryMaxLC
@@ -5962,10 +5962,10 @@ To obtain the CIE L*u*v* coordinates of minimum CIE metric lightness (L*)
for a given Psychometric Hue Angle and Psychometric Chroma, use
XcmsCIELuvQueryMinL .
-
-
-
-
+Psychometric Hue Angle
+CIE metric lightness
+CIE metric lightnessminimum
+XcmsCIELuvQueryMinL
@@ -6054,9 +6054,9 @@ is beyond maximum for the given hue angle.
To obtain the maximum Chroma for a given Hue and Value, use
XcmsTekHVCQueryMaxC .
-
-
-
+Chroma
+Chromamaximum
+XcmsTekHVCQueryMaxC
@@ -6137,9 +6137,9 @@ and Value at which the maximum Chroma was found.
To obtain the maximum Value for a given Hue and Chroma, use
XcmsTekHVCQueryMaxV .
-
-
-
+Value
+Valuemaximum
+XcmsTekHVCQueryMaxV
@@ -6222,11 +6222,11 @@ To obtain the maximum Chroma and Value at which it is reached
for a specified Hue, use
XcmsTekHVCQueryMaxVC .
-
-
-
-
-
+Chroma
+Value
+Chromamaximum
+Valuemaximum
+XcmsTekHVCQueryMaxVC
@@ -6300,11 +6300,11 @@ contain maximum Values for a specified Hue and the
Chroma at which the maximum Values are reached, use
XcmsTekHVCQueryMaxVSamples .
-
-
-
-
-
+Chroma
+Value
+Chromamaximum
+Valuemaximum
+XcmsTekHVCQueryMaxVSamples
@@ -6383,9 +6383,9 @@ space.
To obtain the minimum Value for a given Hue and Chroma, use
XcmsTekHVCQueryMinV .
-
-
-
+Value
+Valueminimum
+XcmsTekHVCQueryMinV
@@ -6543,7 +6543,7 @@ thus bypassing conversion between CIE u*v*Y and CIE XYZ.
To add a device-independent color space, use
XcmsAddColorSpace .
-
+XcmsAddColorSpace
@@ -6611,7 +6611,7 @@ To obtain the format associated with the color space
associated with a specified color string prefix, use
XcmsFormatOfPrefix .
-
+XcmsFormatOfPrefix
@@ -6653,7 +6653,7 @@ To obtain the color string prefix associated with the color space
specified by a color format, use
XcmsPrefixOfFormat .
-
+XcmsPrefixOfFormat
@@ -6797,7 +6797,7 @@ The callback in the
structure for parsing a color string for the particular color space must
adhere to the following software interface specification:
-
+XcmsParseStringProc
@@ -7079,8 +7079,8 @@ The conversion functions provided by Xlib are:
-
-
+Function set
+Function setLINEAR_RGB
Functions to convert between device-dependent color spaces
@@ -7096,7 +7096,7 @@ The function set also contains a function that reads
color characterization data off root window properties.
It is this characterization data that will differ between devices within
a class of output devices.
-
+Device Color Characterization
For details about how color characterization data is
stored in root window properties,
see the section on Device Color Characterization in the
@@ -7119,7 +7119,7 @@ its corresponding data may be stored on different root window properties.
To add a function set, use
XcmsAddFunctionSet .
-
+XcmsAddFunctionSet
@@ -7248,7 +7248,7 @@ structure for a particular screen.
The screen initialization callback must adhere to the following software
interface specification:
-
+XcmsScreenInitProc
@@ -7308,8 +7308,8 @@ screen's root window.
It then initializes the specified
XcmsPerScrnInfo
structure.
-
-
+Device profile
+Color Characterization Data
If successful, the procedure fills in the
XcmsPerScrnInfo
structure as follows:
diff --git a/specs/libX11/CH07.xml b/specs/libX11/CH07.xml
index f7eaeb29..73232d76 100644
--- a/specs/libX11/CH07.xml
+++ b/specs/libX11/CH07.xml
@@ -257,9 +257,9 @@ to be useful in a window.
-
-
-
+Display Functions
+Source
+Destination
The function attributes of a GC are used when you update a section of
a drawable (the destination) with bits from somewhere else (the source).
The function in a GC defines how the new destination bits are to be
@@ -377,10 +377,10 @@ are:
Many graphics operations depend on either pixel values or planes in a GC.
-
+Pixel value
The planes attribute is of type long, and it specifies which planes of the
destination are to be modified, one bit per plane.
-
+Planemask
A monochrome display has only one plane and
will be the least significant bit of the word.
As planes are added to the display hardware, they will occupy more
@@ -956,8 +956,8 @@ requests (and any similar requests defined by extensions).
To create a new GC that is usable on a given screen with a
depth of drawable, use
XCreateGC .
-
-
+Graphics contextinitializing
+XCreateGC
@@ -1045,7 +1045,7 @@ errors.
To copy components from a source GC to a destination GC, use
XCopyGC .
-
+XCopyGC
@@ -1131,7 +1131,7 @@ errors.
To change the components in a given GC, use
XChangeGC .
-
+XChangeGC
@@ -1227,7 +1227,7 @@ errors.
To obtain components of a given GC, use
XGetGCValues .
-
+XGetGCValues
@@ -1339,7 +1339,7 @@ if the component has never been explicitly set by the client.
To free a given GC, use
XFreeGC .
-
+XFreeGC
@@ -1393,7 +1393,7 @@ To obtain the
GContext
resource ID for a given GC, use
XGContextFromGC .
-
+XGContextFromGC
@@ -1429,7 +1429,7 @@ An example might be when a protocol extension uses the GC indirectly,
in such a way that the extension interface cannot know what GC will be used.
To force sending GC component changes, use
XFlushGC .
-
+XFlushGC
@@ -1523,7 +1523,7 @@ Arc mode, subwindow mode, and graphics exposure components
To set the foreground, background, plane mask, and function components
for a given GC, use
XSetState .
-
+XSetState
@@ -1616,7 +1616,7 @@ errors.
To set the foreground of a given GC, use
XSetForeground .
-
+XSetForeground
@@ -1675,7 +1675,7 @@ errors.
To set the background of a given GC, use
XSetBackground .
-
+XSetBackground
@@ -1734,7 +1734,7 @@ errors.
To set the display function in a given GC, use
XSetFunction .
-
+XSetFunction
@@ -1794,7 +1794,7 @@ errors.
To set the plane mask of a given GC, use
XSetPlaneMask .
-
+XSetPlaneMask
@@ -1859,7 +1859,7 @@ errors.
To set the line drawing components of a given GC, use
XSetLineAttributes .
-
+XSetLineAttributes
@@ -1968,7 +1968,7 @@ errors.
To set the dash-offset and dash-list for dashed line styles of a given GC, use
XSetDashes .
-
+XSetDashes
@@ -2097,7 +2097,7 @@ errors.
To set the fill-style of a given GC, use
XSetFillStyle .
-
+XSetFillStyle
@@ -2163,7 +2163,7 @@ errors.
To set the fill-rule of a given GC, use
XSetFillRule .
-
+XSetFillRule
@@ -2243,7 +2243,7 @@ as well as to set the tile or stipple shape and the tile or stipple origin.
To obtain the best size of a tile, stipple, or cursor, use
XQueryBestSize .
-
+XQueryBestSize
@@ -2386,7 +2386,7 @@ errors.
To obtain the best fill tile shape, use
XQueryBestTile .
-
+XQueryBestTile
@@ -2492,7 +2492,7 @@ errors.
To obtain the best stipple shape, use
XQueryBestStipple .
-
+XQueryBestStipple
@@ -2598,7 +2598,7 @@ errors.
To set the fill tile of a given GC, use
XSetTile .
-
+XSetTile
@@ -2666,7 +2666,7 @@ errors.
To set the stipple of a given GC, use
XSetStipple .
-
+XSetStipple
@@ -2734,7 +2734,7 @@ errors.
To set the tile or stipple origin of a given GC, use
XSetTSOrigin .
-
+XSetTSOrigin
@@ -2815,7 +2815,7 @@ errors.
To set the current font of a given GC, use
XSetFont .
-
+XSetFont
@@ -2886,7 +2886,7 @@ and the clip-mask or set the clip-mask to a list of rectangles.
To set the clip-origin of a given GC, use
XSetClipOrigin .
-
+XSetClipOrigin
@@ -2961,7 +2961,7 @@ errors.
To set the clip-mask of a given GC to the specified pixmap, use
XSetClipMask .
-
+XSetClipMask
@@ -3029,7 +3029,7 @@ errors.
To set the clip-mask of a given GC to the specified list of rectangles, use
XSetClipRectangles .
-
+XSetClipRectangles
@@ -3203,7 +3203,7 @@ see section 16.5.
To set the arc mode of a given GC, use
XSetArcMode .
-
+XSetArcMode
@@ -3267,7 +3267,7 @@ errors.
To set the subwindow mode of a given GC, use
XSetSubwindowMode .
-
+XSetSubwindowMode
@@ -3331,7 +3331,7 @@ errors.
To set the graphics-exposures flag of a given GC, use
XSetGraphicsExposures .
-
+XSetGraphicsExposures
diff --git a/specs/libX11/CH08.xml b/specs/libX11/CH08.xml
index 4810d4b3..b093545e 100644
--- a/specs/libX11/CH08.xml
+++ b/specs/libX11/CH08.xml
@@ -36,9 +36,9 @@ which sets the pixmap to a known value.
To clear a rectangular area of a given window, use
XClearArea .
-
-
-
+Areasclearing
+Clearingareas
+XClearArea
@@ -178,9 +178,9 @@ errors.
To clear the entire area in a given window, use
XClearWindow .
-
-
-
+Windowclearing
+Clearingwindows
+XClearWindow
@@ -262,9 +262,9 @@ Xlib provides functions that you can use to copy an area or a bit plane.
To copy an area between drawables of the same
root and depth, use
XCopyArea .
-
-
-
+Areascopying
+Copyingareas
+XCopyArea
@@ -457,9 +457,9 @@ errors.
To copy a single bit plane of a given drawable, use
XCopyPlane .
-
-
-
+Planecopying
+Copyingplanes
+XCopyPlane
@@ -686,7 +686,7 @@ use these structures:
-
+XSegment
@@ -699,7 +699,7 @@ typedef struct {
-
+XPoint
@@ -712,7 +712,7 @@ typedef struct {
-
+XRectangle
@@ -726,7 +726,7 @@ typedef struct {
-
+XArc
@@ -754,16 +754,16 @@ for these values.
-
-
-
-
+Pointsdrawing
+Drawingpoints
+XDrawPoints
+XDrawPoint
To draw a single point in a given drawable, use
XDrawPoint .
-
+XDrawPoint
@@ -835,7 +835,7 @@ Specify the x and y coordinates where you want the point drawn.
To draw multiple points in a given drawable, use
XDrawPoints .
-
+XDrawPoints
@@ -964,19 +964,19 @@ errors.
-
-
-
-
-
-
-
+Linesdrawing
+Drawinglines
+XDrawLine
+XDrawLines
+Polygonsdrawing
+Drawingpolygons
+XDrawSegments
To draw a single line between two points in a given drawable, use
XDrawLine .
-
+XDrawLine
@@ -1070,7 +1070,7 @@ Specify the points (x1, y1) and (x2, y2) to be connected.
To draw multiple lines in a given drawable, use
XDrawLines .
-
+XDrawLines
@@ -1158,7 +1158,7 @@ or
To draw multiple, unconnected lines in a given drawable,
use
XDrawSegments .
-
+XDrawSegments
@@ -1319,16 +1319,16 @@ errors.
-
-
-
-
+Rectanglesdrawing
+Drawingrectangles
+XDrawRectangle
+XDrawRectangles
To draw the outline of a single rectangle in a given drawable, use
XDrawRectangle .
-
+XDrawRectangle
@@ -1425,7 +1425,7 @@ Specify the width and height(Wh.
To draw the outline of multiple rectangles
in a given drawable, use
XDrawRectangles .
-
+XDrawRectangles
@@ -1549,17 +1549,17 @@ errors.
-
-
-
-
+Drawingarcs
+XDrawArc
+Arcsdrawing
+XDrawArcs
To draw a single arc in a given drawable, use
XDrawArc .
-
+XDrawArc
@@ -1679,7 +1679,7 @@ arc, in units of degrees * 64.
To draw multiple arcs in a given drawable, use
XDrawArcs .
-
+XDrawArcs
@@ -1907,17 +1907,17 @@ A single arc or multiple arcs
-
-
-
-
+Fillingrectangles
+XFillRectangle
+Rectanglefilling
+XFillRectangles
To fill a single rectangular area in a given drawable, use
XFillRectangle .
-
+XFillRectangle
@@ -2014,7 +2014,7 @@ Specify the width and height(Wh.
To fill multiple rectangular areas in a given drawable, use
XFillRectangles .
-
+XFillRectangles
@@ -2147,9 +2147,9 @@ errors.
To fill a polygon area in a given drawable, use
XFillPolygon .
-
-
-
+Polygonsfilling
+Fillingpolygon
+XFillPolygon
@@ -2343,12 +2343,12 @@ errors.
-
-
-
+XFillArc
+Arcsfilling
+Fillingarcs
To fill a single arc in a given drawable, use
XFillArc .
-
+XFillArc
@@ -2468,7 +2468,7 @@ arc, in units of degrees * 64.
To fill multiple arcs in a given drawable, use
XFillArcs .
-
+XFillArcs
@@ -2591,7 +2591,7 @@ errors.
-
+Font
A font is a graphical description of a set of characters that are used to
increase efficiency whenever a set of small, similar sized patterns are
repeatedly used.
@@ -2665,7 +2665,7 @@ structures contain:
-
+XCharStruct
@@ -2681,7 +2681,7 @@ typedef struct {
-
+XFontProp
@@ -2693,7 +2693,7 @@ typedef struct {
-
+XChar2b
@@ -2705,7 +2705,7 @@ typedef struct { /* normal 16 bit characters are two bytes */
-
+XFontStruct
@@ -3003,9 +3003,9 @@ A basic set of font properties is specified in the X Consortium standard
Xlib provides functions that you can use to load fonts, get font information,
unload fonts, and free font information.
-
-
-
+Fontsgetting information
+Fontsunloading
+Fontsfreeing font information
A few font functions use a
GContext
resource ID or a font ID interchangeably.
@@ -3015,7 +3015,7 @@ resource ID or a font ID interchangeably.
To load a given font, use
XLoadFont .
-
+XLoadFont
@@ -3091,7 +3091,7 @@ errors.
To return information about an available font, use
XQueryFont .
-
+XQueryFont
@@ -3157,7 +3157,7 @@ and
XQueryFont
in a single operation, use
XLoadQueryFont .
-
+XLoadQueryFont
@@ -3225,7 +3225,7 @@ or
XLoadQueryFont ,
use
XFreeFont .
-
+XFreeFont
@@ -3282,7 +3282,7 @@ error.
To return a given font property, use
XGetFontProperty .
-
+XGetFontProperty
@@ -3354,7 +3354,7 @@ To unload a font that was loaded by
XLoadFont ,
use
XUnloadFont .
-
+XUnloadFont
@@ -3419,7 +3419,7 @@ when querying a font type for a list of available sizes and so on.
To return a list of the available font names, use
XListFonts .
-
+XListFonts
@@ -3506,7 +3506,7 @@ when finished with the result to free the memory.
To free a font name array, use
XFreeFontNames .
-
+XFreeFontNames
@@ -3543,7 +3543,7 @@ or
To obtain the names and information about available fonts, use
XListFontsWithInfo .
-
+XListFontsWithInfo
@@ -3650,7 +3650,7 @@ the client should call
To free font structures and font names, use
XFreeFontInfo .
-
+XFreeFontInfo
@@ -3723,8 +3723,8 @@ to close the font.
Xlib provides functions that you can use to compute the width,
the logical extents,
and the server information about 8-bit and 2-byte text strings.
-
-
+XTextWidth
+XTextWidth16
The width is computed by adding the character widths of all the characters.
It does not matter if the font is an 8-bit or 2-byte font.
These functions return the sum of the character metrics in pixels.
@@ -3734,7 +3734,7 @@ These functions return the sum of the character metrics in pixels.
To determine the width of an 8-bit character string, use
XTextWidth .
-
+XTextWidth
@@ -3784,7 +3784,7 @@ Specifies the character count in the specified string.
To determine the width of a 2-byte character string, use
XTextWidth16 .
-
+XTextWidth16
@@ -3842,7 +3842,7 @@ Specifies the character count in the specified string.
To compute the bounding box of an 8-bit character string in a given font, use
XTextExtents .
-
+XTextExtents
@@ -3942,7 +3942,7 @@ structure.
To compute the bounding box of a 2-byte character string in a given font, use
XTextExtents16 .
-
+XTextExtents16
@@ -4089,7 +4089,7 @@ undefined characters in the string are taken to have all zero metrics.
To query the server for the bounding box of an 8-bit character string in a
given font, use
XQueryTextExtents .
-
+XQueryTextExtents
@@ -4201,7 +4201,7 @@ structure.
To query the server for the bounding box of a 2-byte character string
in a given font, use
XQueryTextExtents16 .
-
+XQueryTextExtents16
@@ -4405,7 +4405,7 @@ use the following structures:
-
+XTextItem
@@ -4420,7 +4420,7 @@ typedef struct {
-
+XTextItem16
@@ -4467,14 +4467,14 @@ structure.
-
-
+Textdrawing
+Drawingtext items
To draw 8-bit characters in a given drawable, use
XDrawText .
-
+XDrawText
@@ -4570,7 +4570,7 @@ Specifies the number of text items in the array.
To draw 2-byte characters in a given drawable, use
XDrawText16 .
-
+XDrawText16
@@ -4726,11 +4726,11 @@ errors.
-
-
+Stringsdrawing
+Drawingstrings
To draw 8-bit characters in a given drawable, use
XDrawString .
-
+XDrawString
@@ -4826,7 +4826,7 @@ Specifies the number of characters in the string argument.
To draw 2-byte characters in a given drawable, use
XDrawString16 .
-
+XDrawString16
@@ -4956,21 +4956,21 @@ errors.
-
-
+Image textdrawing
+Drawingimage text
Some applications, in particular terminal emulators, need to
print image text in which both the foreground and background bits of
each character are painted.
This prevents annoying flicker on many displays.
-
-
+XDrawImageString
+XDrawImageString16
To draw 8-bit image text characters in a given drawable, use
XDrawImageString .
-
+XDrawImageString
@@ -5066,7 +5066,7 @@ Specifies the number of characters in the string argument.
To draw 2-byte image text characters in a given drawable, use
XDrawImageString16 .
-
+XDrawImageString16
@@ -5273,7 +5273,7 @@ which describes an image as it exists in the client's memory.
-
+XImage
@@ -5311,7 +5311,7 @@ typedef struct _XImage {
To initialize the image manipulation routines of an image structure, use
XInitImage .
-
+XInitImage
@@ -5369,7 +5369,7 @@ or inconsistency in the structure, in which case the image is not changed.
To combine an image with a rectangle of a drawable on the display,
use
XPutImage .
-
+XPutImage
@@ -5558,7 +5558,7 @@ To return the contents of a rectangle in a given drawable on the display,
use
XGetImage .
This function specifically supports rudimentary screen dumps.
-
+XGetImage
@@ -5745,7 +5745,7 @@ errors.
To copy the contents of a rectangle on the display
to a location within a preexisting image structure, use
XGetSubImage .
-
+XGetSubImage
diff --git a/specs/libX11/CH09.xml b/specs/libX11/CH09.xml
index 5f0ed894..296ff68f 100644
--- a/specs/libX11/CH09.xml
+++ b/specs/libX11/CH09.xml
@@ -29,7 +29,7 @@ programs. Xlib provides management functions to:
To change a window's parent to another window on the same screen, use
XReparentWindow .
There is no way to move a window between screens.
-
+XReparentWindow
@@ -213,7 +213,7 @@ when they are destroyed.
To add or remove a window from the client's save-set, use
XChangeSaveSet .
-
+XChangeSaveSet
@@ -288,7 +288,7 @@ errors.
To add a window to the client's save-set, use
XAddToSaveSet .
-
+XAddToSaveSet
@@ -347,7 +347,7 @@ errors.
To remove a window from the client's save-set, use
XRemoveFromSaveSet .
-
+XRemoveFromSaveSet
@@ -444,7 +444,7 @@ required list.
To install a colormap, use
XInstallColormap .
-
+XInstallColormap
@@ -517,7 +517,7 @@ error.
To uninstall a colormap, use
XUninstallColormap .
-
+XUninstallColormap
@@ -588,7 +588,7 @@ error.
To obtain a list of the currently installed colormaps for a given screen, use
XListInstalledColormaps .
-
+XListInstalledColormaps
@@ -670,7 +670,7 @@ search path for a server.
To set the font search path, use
XSetFontPath .
-
+XSetFontPath
@@ -748,7 +748,7 @@ error.
To get the current font search path, use
XGetFontPath .
-
+XGetFontPath
@@ -800,7 +800,7 @@ To free data returned by
XGetFontPath ,
use
XFreeFontPath .
-
+XFreeFontPath
@@ -845,8 +845,8 @@ connections by the window system server.
While the server is grabbed,
no processing of requests or close downs on any other connection will occur.
A client closing its connection automatically ungrabs the server.
-
-
+Menus
+Windowmanagers
Although grabbing the server is highly discouraged, it is sometimes necessary.
@@ -854,9 +854,9 @@ Although grabbing the server is highly discouraged, it is sometimes necessary.
To grab the server, use
XGrabServer .
-
-
-
+Servergrabbing
+Grabbingserver
+XGrabServer
@@ -892,7 +892,7 @@ You should not grab the X server any more than is absolutely necessary.
To ungrab the server, use
XUngrabServer .
-
+XUngrabServer
@@ -934,7 +934,7 @@ Xlib provides a function to cause the connection to
a client to be closed and its resources to be destroyed.
To destroy a client, use
XKillClient .
-
+XKillClient
@@ -1021,7 +1021,7 @@ or to obtain the current screen saver values.
To set the screen saver mode, use
XSetScreenSaver .
-
+XSetScreenSaver
@@ -1156,7 +1156,7 @@ error.
To force the screen saver on or off, use
XForceScreenSaver .
-
+XForceScreenSaver
@@ -1222,7 +1222,7 @@ error.
To activate the screen saver, use
XActivateScreenSaver .
-
+XActivateScreenSaver
@@ -1250,7 +1250,7 @@ Specifies the connection to the X server.
To reset the screen saver, use
XResetScreenSaver .
-
+XResetScreenSaver
@@ -1278,7 +1278,7 @@ Specifies the connection to the X server.
To get the current screen saver values, use
XGetScreenSaver .
-
+XGetScreenSaver
@@ -1379,8 +1379,8 @@ Change, enable, or disable access
-
-
+Access control list
+Authentication
X does not provide any protection on a per-window basis.
If you find out the resource ID of a resource, you can manipulate it.
To provide some minimal level of protection, however,
@@ -1393,7 +1393,7 @@ leaves host-level access control as the only common mechanism.
-
+Default Protection
The initial set of hosts allowed to open connections typically consists of:
@@ -1409,7 +1409,7 @@ On POSIX-conformant systems, each host listed in the
file.
The ? indicates the number of the
display.
-
+Files/etc/X?.hosts
This file should consist of host names separated by newlines.
DECnet nodes must terminate in :: to distinguish them from Internet hosts.
@@ -1447,7 +1447,7 @@ structure, which contains:
-
+XHostAddress
@@ -1499,7 +1499,7 @@ structure, which contains:
-
+XServerInterpretedAddress
@@ -1525,7 +1525,7 @@ specify the length in byte of the type and value strings.
To add a single host, use
XAddHost .
-
+XAddHost
@@ -1583,7 +1583,7 @@ errors.
To add multiple hosts at one time, use
XAddHosts .
-
+XAddHosts
@@ -1652,7 +1652,7 @@ errors.
To obtain a host list, use
XListHosts .
-
+XListHosts
@@ -1716,7 +1716,7 @@ this memory should be freed by calling
To remove a single host, use
XRemoveHost .
-
+XRemoveHost
@@ -1778,7 +1778,7 @@ errors.
To remove multiple hosts at one time, use
XRemoveHosts .
-
+XRemoveHosts
@@ -1869,7 +1869,7 @@ at connection setup.
To change access control, use
XSetAccessControl .
-
+XSetAccessControl
@@ -1928,7 +1928,7 @@ errors.
To enable access control, use
XEnableAccessControl .
-
+XEnableAccessControl
@@ -1969,7 +1969,7 @@ error.
To disable access control, use
XDisableAccessControl .
-
+XDisableAccessControl
diff --git a/specs/libX11/CH10.xml b/specs/libX11/CH10.xml
index 0e77485c..749d29ec 100644
--- a/specs/libX11/CH10.xml
+++ b/specs/libX11/CH10.xml
@@ -31,10 +31,10 @@ Functions for handling events are dealt with in the next chapter.
-
+Eventtypes
An event is data generated asynchronously by the X server as a result of some
device activity or as side effects of a request sent by an Xlib function.
-
+Event
Device-related events propagate from the source window to ancestor windows
until some client application has selected that event type
or until the event is explicitly discarded.
@@ -50,8 +50,8 @@ do-not-propagate mask of the window's attributes.
However,
MappingNotify
events are always sent to all clients.
-
-
+Input Control
+Output Control
@@ -60,7 +60,7 @@ For each event type,
a corresponding constant name is defined in
which is used when referring to an event type.
-
+Eventcategories
The following table lists the event category
and its associated event type or types.
The processing associated with these events is discussed in section 10.5.
@@ -176,7 +176,7 @@ All the event structures have the following common members:
-
+XAnyEvent
@@ -232,7 +232,7 @@ union.
-
+XEvent
@@ -308,7 +308,7 @@ is used to access any other information in the structure.
-
+Event mask
Clients select event reporting of most events relative to a window.
To do this, pass an event mask to an Xlib event-handling
function that takes an event_mask argument.
@@ -495,7 +495,7 @@ For example, if you pass the event mask
the X server sends back only
ButtonPress
events.
-
+CurrentTime
Most events contain a time member,
which is the time at which an event occurred.
@@ -970,11 +970,11 @@ and
-
-
-
-
-
+EventsButtonPress
+EventsButtonRelease
+EventsKeyPress
+EventsKeyRelease
+EventsMotionNotify
This section discusses the processing that occurs for the
keyboard events
KeyPress
@@ -990,8 +990,8 @@ see chapter 11.
-
-
+KeyPress
+KeyRelease
The X server reports
KeyPress
or
@@ -999,8 +999,8 @@ or
events to clients wanting information about keys that logically change state.
Note that these events are generated for all keys,
even those mapped to modifier bits.
-
-
+ButtonPress
+ButtonRelease
The X server reports
ButtonPress
or
@@ -1009,7 +1009,7 @@ events to clients wanting information about buttons that logically change state.
-
+MotionNotify
The X server reports
MotionNotify
events to clients wanting information about when the pointer logically moves.
@@ -1417,15 +1417,15 @@ follows:
-
-
+EventsEnterNotify
+EventsLeaveNotify
This section describes the processing that
occurs for the window crossing events
EnterNotify
and
LeaveNotify .
-
-
+EnterNotify
+LeaveNotify
If a pointer motion or a window hierarchy change causes the
pointer to be in a different window than before, the X server reports
EnterNotify
@@ -1487,9 +1487,9 @@ bits of the event-mask attribute of the window.
The structure for these event types contains:
-
-
-
+XCrossingEvent
+XEnterWindowEvent
+XLeaveWindowEvent
@@ -1946,14 +1946,14 @@ initial and final positions for the events.
-
-
+EventsFocusIn
+EventsFocusOut
This section describes the processing that occurs for the input focus events
FocusIn
and
FocusOut .
-
-
+FocusIn
+FocusOut
The X server can report
FocusIn
or
@@ -1982,9 +1982,9 @@ bit in the event-mask attribute of the window.
The structure for these event types contains:
-
-
-
+XFocusChangeEvent
+XFocusInEvent
+XFocusOutEvent
@@ -2643,8 +2643,8 @@ G to F.
-
-
+EventsKeymapNotify
+KeymapNotify
The X server can report
KeymapNotify
events to clients that want information about changes in their keyboard state.
@@ -2668,7 +2668,7 @@ The structure for this event type contains:
-
+XKeymapEvent
@@ -2726,8 +2726,8 @@ A more sophisticated client application redraws only the exposed region.
-
-
+EventsExpose
+Expose
The X server can report
Expose
events to clients wanting information about when the contents of window regions
@@ -2774,7 +2774,7 @@ The structure for this event type contains:
-
+XExposeEvent
@@ -2821,9 +2821,9 @@ on events with zero counts.
-
-
-
+EventsGraphicsExpose
+EventsNoExpose
+GraphicsExpose
The X server can report
GraphicsExpose
events to clients wanting information about when a destination region could not
@@ -2840,7 +2840,7 @@ drawable).
-
+NoExpose
The X server generates a
NoExpose
event whenever a graphics request that might
@@ -2874,7 +2874,7 @@ The structures for these event types contain:
-
+XGraphicsExposeEvent
@@ -2895,7 +2895,7 @@ typedef struct {
-
+XNoExposeEvent
@@ -3040,8 +3040,8 @@ events
-
-
+EventsCirculateNotify
+CirculateNotify
The X server can report
CirculateNotify
events to clients wanting information about when a window changes
@@ -3071,7 +3071,7 @@ The structure for this event type contains:
-
+XCirculateEvent
@@ -3117,8 +3117,8 @@ the window is now below all siblings.
-
-
+EventsConfigureNotify
+ConfigureNotify
The X server can report
ConfigureNotify
events to clients wanting information about actual changes to a window's
@@ -3191,7 +3191,7 @@ bit in the event-mask attribute of the parent window
The structure for this event type contains:
-
+XConfigureEvent
@@ -3260,8 +3260,8 @@ is
-
-
+EventsCreateNotify
+CreateNotify
The X server can report
CreateNotify
events to clients wanting information about creation of windows.
@@ -3286,7 +3286,7 @@ The structure for the event type contains:
-
+XCreateWindowEvent
@@ -3330,8 +3330,8 @@ if the override_redirect member is
-
-
+EventsDestroyNotify
+DestroyNotify
The X server can report
DestroyNotify
events to clients wanting information about which windows are destroyed.
@@ -3369,7 +3369,7 @@ The structure for this event type contains:
-
+XDestroyWindowEvent
@@ -3403,8 +3403,8 @@ The window member is set to the window that is destroyed.
-
-
+EventsGravityNotify
+GravityNotify
The X server can report
GravityNotify
events to clients wanting information about when a window is moved because of a
@@ -3434,7 +3434,7 @@ The structure for this event type contains:
-
+XGravityEvent
@@ -3473,8 +3473,8 @@ window.
-
-
+EventsMapNotify
+MapNotify
The X server can report
MapNotify
events to clients wanting information about which windows are mapped.
@@ -3503,7 +3503,7 @@ The structure for this event type contains:
-
+XMapEvent
@@ -3545,8 +3545,8 @@ which override structure control.
-
-
+EventsMappingNotify
+MappingNotify
The X server reports
MappingNotify
events to all clients.
@@ -3580,7 +3580,7 @@ The structure for this event type contains:
-
+XMappingEvent
@@ -3637,8 +3637,8 @@ you should call
-
-
+EventsReparentNotify
+ReparentNotify
The X server can report
ReparentNotify
events to clients wanting information about changing a window's parent.
@@ -3664,7 +3664,7 @@ The structure for this event type contains:
-
+XReparentEvent
@@ -3710,8 +3710,8 @@ if the override_redirect member is
-
-
+EventsUnmapNotify
+UnmapNotify
The X server can report
UnmapNotify
events to clients wanting information about which windows are unmapped.
@@ -3735,7 +3735,7 @@ The structure for this event type contains:
-
+XUnmapEvent
@@ -3776,8 +3776,8 @@ the window itself had a win_gravity of
-
-
+EventsVisibilityNotify
+VisibilityNotify
The X server can report
VisibilityNotify
events to clients wanting any change in the visibility of the specified window.
@@ -3831,7 +3831,7 @@ The structure for this event type contains:
-
+XVisibilityEvent
@@ -3937,8 +3937,8 @@ events
-
-
+EventsCirculateRequest
+CirculateRequest
The X server can report
CirculateRequest
events to clients wanting information about
@@ -3977,7 +3977,7 @@ The structure for this event type contains:
-
+XCirculateRequestEvent
@@ -4018,8 +4018,8 @@ the subwindow should be below all siblings.
-
-
+EventsConfigureRequest
+ConfigureRequest
The X server can report
ConfigureRequest
events to clients wanting information about when a different client initiates
@@ -4068,7 +4068,7 @@ The structure for this event type contains:
-
+XConfigureRequestEvent
@@ -4115,8 +4115,8 @@ respectively, if they are not given in the request.
-
-
+EventsMapRequest
+MapRequest
The X server can report
MapRequest
events to clients wanting information about a different client's desire
@@ -4164,7 +4164,7 @@ The structure for this event type contains:
-
+XMapRequestEvent
@@ -4193,8 +4193,8 @@ The window member is set to the window to be mapped.
-
-
+EventsResizeRequest
+ResizeRequest
The X server can report
ResizeRequest
events to clients wanting information about another client's attempts to change the
@@ -4221,7 +4221,7 @@ The structure for this event type contains:
-
+XResizeRequestEvent
@@ -4253,8 +4253,8 @@ excluding the border.
-
-
+EventsColormapNotify
+ColormapNotify
The X server can report
ColormapNotify
events to clients wanting information about when the colormap changes
@@ -4297,7 +4297,7 @@ The structure for this event type contains:
-
+XColormapEvent
@@ -4392,8 +4392,8 @@ events
-
-
+EventsClientMessage
+ClientMessage
The X server generates
ClientMessage
events only when a client calls the function
@@ -4405,7 +4405,7 @@ The structure for this event type contains:
-
+XClientMessageEvent
@@ -4448,8 +4448,8 @@ message_type, or data members.
-
-
+EventsPropertyNotify
+PropertyNotify
The X server can report
PropertyNotify
events to clients wanting information about property changes
@@ -4469,7 +4469,7 @@ The structure for this event type contains:
-
+XPropertyEvent
@@ -4527,8 +4527,8 @@ or, if the delete argument is
-
-
+EventsSelectionClear
+SelectionClear
The X server reports
SelectionClear
events to the client losing ownership of a selection.
@@ -4542,7 +4542,7 @@ The structure for this event type contains:
-
+XSelectionClearEvent
@@ -4577,8 +4577,8 @@ call.
-
-
+EventsSelectionRequest
+SelectionRequest
The X server reports
SelectionRequest
events to the owner of a selection.
@@ -4593,7 +4593,7 @@ The structure for this event type contains:
-
+XSelectionRequestEvent
@@ -4649,8 +4649,8 @@ standard Inter-Client Communication Conventions Manual
-
-
+EventsSelectionNotify
+SelectionNotify
This event is generated by the X server in response to a
ConvertSelection
protocol request when there is no owner for the selection.
@@ -4681,7 +4681,7 @@ The structure for this event type contains:
-
+XSelectionEvent
diff --git a/specs/libX11/CH11.xml b/specs/libX11/CH11.xml
index 5e2b0d6a..fdf0d7f3 100644
--- a/specs/libX11/CH11.xml
+++ b/specs/libX11/CH11.xml
@@ -40,7 +40,7 @@ and
XChangeWindowAttributes .
Another way is to use
XSelectInput .
-
+XSelectInput
@@ -97,7 +97,7 @@ Events are reported relative to a window.
If a window is not interested in a device event, it usually propagates to
the closest ancestor that is interested,
unless the do_not_propagate mask prohibits it.
-
+Eventpropagation
@@ -178,7 +178,7 @@ These functions differ in the additional tasks they might perform.
To flush the output buffer, use
XFlush .
-
+XFlush
@@ -213,9 +213,9 @@ buffer is automatically flushed as needed by calls to
XNextEvent ,
and
XWindowEvent .
-
-
-
+XPending
+XNextEvent
+XWindowEvent
Events generated by the server may be enqueued into the library's event queue.
@@ -224,7 +224,7 @@ Events generated by the server may be enqueued into the library's event queue.
To flush the output buffer and then wait until all requests have been processed,
use
XSync .
-
+XSync
@@ -307,7 +307,7 @@ in its network connection that is not yet read into the event queue.
To check the number of events in the event queue, use
XEventsQueued .
-
+XEventsQueued
@@ -393,7 +393,7 @@ function.
To return the number of events that are pending, use
XPending .
-
+XPending
@@ -467,7 +467,7 @@ predicate procedures that you provide
To get the next event and remove it from the queue, use
XNextEvent .
-
+XNextEvent
@@ -517,7 +517,7 @@ flushes the output buffer and blocks until an event is received.
To peek at the event queue, use
XPeekEvent .
-
+XPeekEvent
@@ -654,7 +654,7 @@ If it did not find a match, it must return
To check the event queue for a matching event
and, if found, remove the event from the queue, use
XIfEvent .
-
+XIfEvent
@@ -733,7 +733,7 @@ structure.
To check the event queue for a matching event without blocking, use
XCheckIfEvent .
-
+XCheckIfEvent
@@ -812,7 +812,7 @@ All earlier events stored in the queue are not discarded.
To check the event queue for a matching event
without removing the event from the queue, use
XPeekIfEvent .
-
+XPeekIfEvent
@@ -901,7 +901,7 @@ or event types, allowing you to process events out of order.
To remove the next event that matches both a window and an event mask, use
XWindowEvent .
-
+XWindowEvent
@@ -980,13 +980,13 @@ flushes the output buffer and blocks until one is received.
To remove the next event that matches both a window and an event mask (if any),
use
XCheckWindowEvent .
-
+XCheckWindowEvent
This function is similar to
XWindowEvent
except that it never blocks and it returns a
Bool
indicating if the event was returned.
-
+XCheckWindowEvent
@@ -1068,7 +1068,7 @@ and the output buffer will have been flushed.
To remove the next event that matches an event mask, use
XMaskEvent .
-
+XMaskEvent
@@ -1139,7 +1139,7 @@ This function is similar to
except that it never blocks and it returns a
Bool
indicating if the event was returned.
-
+XCheckMaskEvent
@@ -1208,7 +1208,7 @@ and the output buffer will have been flushed.
To return and remove the next event in the queue that matches an event type, use
XCheckTypedEvent .
-
+XCheckTypedEvent
@@ -1279,7 +1279,7 @@ and the output buffer will have been flushed.
To return and remove the next event in the queue that matches an event type
and a window, use
XCheckTypedWindowEvent .
-
+XCheckTypedWindowEvent
@@ -1367,7 +1367,7 @@ and the output buffer will have been flushed.
To push an event back into the event queue, use
XPutBackEvent .
-
+XPutBackEvent
@@ -1422,7 +1422,7 @@ There is no limit to the number of times in succession that you can call
To send an event to a specified window, use
XSendEvent .
-
+XSendEvent
This function is often used in selection processing.
For example, the owner of a selection should use
XSendEvent
@@ -1430,7 +1430,7 @@ to send a
SelectionNotify
event to a requestor when a selection has been converted
and stored as a property.
-
+XSendEvent
@@ -1628,7 +1628,7 @@ However, this historical information is highly excessive for most applications.
To determine the approximate maximum number of elements in the motion buffer,
use
XDisplayMotionBufferSize .
-
+XDisplayMotionBufferSize
@@ -1666,7 +1666,7 @@ function makes this history available.
To get the motion history for a specified window and time, use
XGetMotionEvents .
-
+XGetMotionEvents
@@ -1756,7 +1756,7 @@ The return type for this function is a structure defined as follows:
-
+XTimeCoord
@@ -1808,7 +1808,7 @@ so that errors are reported as they occur.
The following function lets you disable or enable synchronous behavior.
Note that graphics may occur 30 or more times more slowly when
synchronization is enabled.
-
+_Xdebug
On POSIX-conformant systems,
there is also a global variable
_Xdebug
@@ -1822,7 +1822,7 @@ all Xlib functions that generate protocol requests call what is known as
an after function.
XSetAfterFunction
sets which function is to be called.
-
+XSetAfterFunction
@@ -1866,8 +1866,8 @@ returns the previous after function.
To enable or disable synchronization, use
XSynchronize .
-
-
+Debuggingsynchronous mode
+XSynchronize
@@ -1925,8 +1925,8 @@ turns off synchronous behavior.
-
-
+Debuggingerror handlers
+Errorhandlers
There are two default error handlers in Xlib:
one to handle typically fatal conditions (for example,
the connection to a display server dying because a machine crashed)
@@ -1943,7 +1943,7 @@ message and exit.
To set the error handler, use
XSetErrorHandler .
-
+XSetErrorHandler
@@ -1997,11 +1997,11 @@ The previous error handler is returned.
The
XErrorEvent
structure contains:
-
+Debuggingerror event
-
+XErrorEvent
@@ -2018,7 +2018,7 @@ typedef struct {
-
+Serial Number
The serial member is the number of requests, starting from one,
sent over the network connection since it was opened.
It is the number that was the value of
@@ -2032,19 +2032,19 @@ chapter:
-
-
+Debuggingerror numbers
+Errorcodes
-
-
-
-
-
-
-
-
-
+BadAccess
+BadAlloc
+BadAtom
+BadColor
+BadCursor
+BadDrawable
+BadFont
+BadGC
+BadIDChoice
@@ -2199,14 +2199,14 @@ chapter:
-
-
-
-
-
-
-
-
+BadImplementation
+BadLength
+BadMatch
+BadName
+BadPixmap
+BadRequest
+BadValue
+BadWindow
@@ -2232,8 +2232,8 @@ fixed alternatives.
To obtain textual descriptions of the specified error code, use
XGetErrorText .
-
-
+XGetErrorText
+Debuggingerror message strings
@@ -2305,7 +2305,7 @@ and error strings.
To obtain error messages from the error database, use
XGetErrorDatabaseText .
-
+XGetErrorDatabaseText
@@ -2450,7 +2450,7 @@ the default_string is returned to the buffer argument.
To report an error to the user when the requested display does not exist, use
XDisplayName .
-
+XDisplayName
@@ -2493,7 +2493,7 @@ program attempted to open when the initial connection attempt failed.
To handle fatal I/O errors, use
XSetIOErrorHandler .
-
+XSetIOErrorHandler
diff --git a/specs/libX11/CH12.xml b/specs/libX11/CH12.xml
index 30449c9d..1c45fe1f 100644
--- a/specs/libX11/CH12.xml
+++ b/specs/libX11/CH12.xml
@@ -56,7 +56,7 @@ may lag the physical state if device event processing is frozen.
-
+Active grab
There are two kinds of grabs:
active and passive.
An active grab occurs when a single client grabs the keyboard and/or pointer
@@ -64,7 +64,7 @@ explicitly (see
XGrabPointer
and
XGrabKeyboard ).
-
+Passive grab
A passive grab occurs when clients grab a particular keyboard key
or pointer button in a window,
and the grab will activate when the key or button is actually pressed.
@@ -85,8 +85,8 @@ For many operations,
there are functions that take a time argument.
The X server includes a timestamp in various events.
One special time, called
-
-
+CurrentTime
+Time
CurrentTime ,
represents the current server time.
The X server maintains the time when the input focus was last changed,
@@ -152,9 +152,9 @@ and
To grab the pointer, use
XGrabPointer .
-
-
-
+Grabbingpointer
+Pointergrabbing
+XGrabPointer
@@ -418,9 +418,9 @@ errors.
To ungrab the pointer, use
XUngrabPointer .
-
-
-
+Ungrabbingpointer
+Pointerungrabbing
+XUngrabPointer
@@ -486,9 +486,9 @@ outside the boundaries of the root window.
To change an active pointer grab, use
XChangeActivePointerGrab .
-
-
-
+Pointergrabbing
+Changingpointer grab
+XChangeActivePointerGrab
@@ -574,9 +574,9 @@ errors.
To grab a pointer button, use
XGrabButton .
-
-
-
+Grabbingbuttons
+Buttongrabbing
+XGrabButton
@@ -818,9 +818,9 @@ errors.
To ungrab a pointer button, use
XUngrabButton .
-
-
-
+Ungrabbingbuttons
+Buttonungrabbing
+XUngrabButton
@@ -939,9 +939,9 @@ and
To grab the keyboard, use
XGrabKeyboard .
-
-
-
+Keyboardgrabbing
+Grabbingkeyboard
+XGrabKeyboard
@@ -1127,9 +1127,9 @@ errors.
To ungrab the keyboard, use
XUngrabKeyboard .
-
-
-
+Keyboardungrabbing
+Ungrabbingkeyboard
+XUngrabKeyboard
@@ -1194,9 +1194,9 @@ active keyboard grab becomes not viewable.
To passively grab a single key of the keyboard, use
XGrabKey .
-
-
-
+Keygrabbing
+Grabbingkeys
+XGrabKey
@@ -1398,9 +1398,9 @@ errors.
To ungrab a key, use
XUngrabKey .
-
-
-
+Keyungrabbing
+Ungrabbingkeys
+XUngrabKey
@@ -1501,7 +1501,7 @@ describes the mechanism for resuming event processing.
To allow further events to be processed when the device has been frozen, use
XAllowEvents .
-
+XAllowEvents
@@ -1756,7 +1756,7 @@ pointer to a new position under program control.
To move the pointer to an arbitrary point in a window, use
XWarpPointer .
-
+XWarpPointer
@@ -1930,7 +1930,7 @@ for input focus policy.
To set the input focus, use
XSetInputFocus .
-
+XSetInputFocus
@@ -2104,7 +2104,7 @@ errors.
To obtain the current input focus, use
XGetInputFocus .
-
+XGetInputFocus
@@ -2178,10 +2178,10 @@ and obtain a bit vector for the keyboard.
-
-
-
-
+Keyboardbell volume
+Keyboardkeyclick volume
+Keyboardbit vector
+Mouseprogramming
This section discusses
the user-preference options of bell, key click,
pointer behavior, and so on.
@@ -2319,7 +2319,7 @@ If an error is generated, a subset of the controls may have been altered.
-
+XChangeKeyboardControl
@@ -2388,7 +2388,7 @@ errors.
To obtain the current control values for the keyboard, use
XGetKeyboardControl .
-
+XGetKeyboardControl
@@ -2434,8 +2434,8 @@ structure.
-
-
+XGetKeyboardControl
+XKeyboardState
@@ -2472,7 +2472,7 @@ with the least significant bit in the byte representing key 8N.
To turn on keyboard auto-repeat, use
XAutoRepeatOn .
-
+XAutoRepeatOn
@@ -2506,7 +2506,7 @@ function turns on auto-repeat for the keyboard on the specified display.
To turn off keyboard auto-repeat, use
XAutoRepeatOff .
-
+XAutoRepeatOff
@@ -2540,7 +2540,7 @@ function turns off auto-repeat for the keyboard on the specified display.
To ring the bell, use
XBell .
-
+XBell
@@ -2624,7 +2624,7 @@ error.
To obtain a bit vector that describes the state of the keyboard, use
XQueryKeymap .
-
+XQueryKeymap
@@ -2680,7 +2680,7 @@ may lag the physical state if device event processing is frozen.
To set the mapping of the pointer buttons, use
XSetPointerMapping .
-
+XSetPointerMapping
@@ -2768,7 +2768,7 @@ error.
To get the pointer mapping, use
XGetPointerMapping .
-
+XGetPointerMapping
@@ -2831,7 +2831,7 @@ in map_return.
To control the pointer's interactive feel, use
XChangePointerControl .
-
+XChangePointerControl
@@ -2944,7 +2944,7 @@ error.
To get the current pointer parameters, use
XGetPointerControl .
-
+XGetPointerControl
@@ -3213,7 +3213,7 @@ Rather, it merely stores it for reading and writing by clients.
To obtain the legal KeyCodes for a display, use
XDisplayKeycodes .
-
+XDisplayKeycodes
@@ -3272,7 +3272,7 @@ Not all KeyCodes in this range are required to have corresponding keys.
To obtain the symbols for the specified KeyCodes, use
XGetKeyboardMapping .
-
+XGetKeyboardMapping
@@ -3397,7 +3397,7 @@ error.
To change the keyboard mapping, use
XChangeKeyboardMapping .
-
+XChangeKeyboardMapping
@@ -3551,7 +3551,7 @@ data structure, which contains:
-
+XModifierKeymap
@@ -3569,7 +3569,7 @@ To create an
XModifierKeymap
structure, use
XNewModifiermap .
-
+XNewModifiermap
@@ -3608,7 +3608,7 @@ To add a new entry to an
XModifierKeymap
structure, use
XInsertModifiermapEntry .
-
+XInsertModifiermapEntry
@@ -3671,7 +3671,7 @@ To delete an entry from an
XModifierKeymap
structure, use
XDeleteModifiermapEntry .
-
+XDeleteModifiermapEntry
@@ -3734,7 +3734,7 @@ To destroy an
XModifierKeymap
structure, use
XFreeModifiermap .
-
+XFreeModifiermap
@@ -3772,7 +3772,7 @@ structure.
To set the KeyCodes to be used as modifiers, use
XSetModifierMapping .
-
+XSetModifierMapping
@@ -3886,7 +3886,7 @@ errors.
To obtain the KeyCodes used as modifiers, use
XGetModifierMapping .
-
+XGetModifierMapping
diff --git a/specs/libX11/CH13.xml b/specs/libX11/CH13.xml
index eca66fdc..ce93fdf1 100644
--- a/specs/libX11/CH13.xml
+++ b/specs/libX11/CH13.xml
@@ -141,7 +141,7 @@ is selecting one of several styles of keyboard input method.
To configure Xlib locale modifiers for the current locale, use
XSetLocaleModifiers .
-
+XSetLocaleModifiers
@@ -540,7 +540,7 @@ A NULL identifies the end of a nested list.
To allocate a nested variable argument list dynamically, use
XVaCreateNestedList .
-
+XVaCreateNestedList
@@ -727,7 +727,7 @@ a broader, more generalized abstraction.
To open an output method, use
XOpenOM .
-
+XOpenOM
@@ -845,7 +845,7 @@ returns NULL if no output method could be opened.
To close an output method, use
XCloseOM .
-
+XCloseOM
@@ -879,7 +879,7 @@ function closes the specified output method.
To set output method attributes, use
XSetOMValues .
-
+XSetOMValues
@@ -932,7 +932,7 @@ No standard arguments are currently defined by Xlib.
To query an output method, use
XGetOMValues .
-
+XGetOMValues
@@ -980,7 +980,7 @@ it returns the name of the first argument that could not be obtained.
To obtain the display associated with an output method, use
XDisplayOfOM .
-
+XDisplayOfOM
@@ -1014,7 +1014,7 @@ function returns the display associated with the specified output method.
To get the locale associated with an output method, use
XLocaleOfOM .
-
+XLocaleOfOM
@@ -1136,7 +1136,7 @@ The value of the argument is a pointer to a structure of type
The
XOMCharSetList
structure is defined as follows:
-
+XOMCharSetList
@@ -1350,7 +1350,7 @@ is defined as an upward compatible type of
To create an output context, use
XCreateOC .
-
+XCreateOC
@@ -1436,7 +1436,7 @@ error.
To destroy an output context, use
XDestroyOC .
-
+XDestroyOC
@@ -1470,7 +1470,7 @@ function destroys the specified output context.
To get the output method associated with an output context, use
XOMOfOC .
-
+XOMOfOC
@@ -1517,7 +1517,7 @@ with a character string using the X Portable Character Set.
To set XOC values, use
XSetOCValues .
-
+XSetOCValues
@@ -1594,7 +1594,7 @@ error.
To obtain XOC values, use
XGetOCValues .
-
+XGetOCValues
@@ -2142,7 +2142,7 @@ so that the output context self indicates whether it was created by
XCreateOC
or
XCreateFontSet .
-
+XCreateFontSet
@@ -2472,7 +2472,7 @@ structures and full font names given an
XFontSet ,
use
XFontsOfFontSet .
-
+XFontsOfFontSet
@@ -2581,7 +2581,7 @@ To obtain the base font name list and the selected font name list given an
XFontSet ,
use
XBaseFontNameListOfFontSet .
-
+XBaseFontNameListOfFontSet
@@ -2643,7 +2643,7 @@ To obtain the locale name given an
XFontSet ,
use
XLocaleOfFontSet .
-
+XLocaleOfFontSet
@@ -2696,7 +2696,7 @@ also frees its associated
XOM
if the output context was created by
XCreateFontSet .
-
+XFreeFontSet
@@ -2800,7 +2800,7 @@ to obtain proper rendering.
To find out about direction-dependent rendering, use
XDirectionalDependentDrawing .
-
+XDirectionalDependentDrawing
@@ -2838,7 +2838,7 @@ otherwise, it returns
To find out about context-dependent rendering, use
XContextualDrawing .
-
+XContextualDrawing
@@ -2876,7 +2876,7 @@ otherwise, it returns
To find out about context-dependent or direction-dependent rendering, use
XContextDependentDrawing .
-
+XContextDependentDrawing
@@ -2925,7 +2925,7 @@ The maximum character extents for the fonts that are used by the text
drawing layers can be accessed by the
XFontSetExtents
structure:
-
+XFontSetExtents
@@ -2990,7 +2990,7 @@ To obtain the maximum extents structure given an
XFontSet ,
use
XExtentsOfFontSet .
-
+XExtentsOfFontSet
@@ -3042,8 +3042,8 @@ use
XmbTextEscapement
or
XwcTextEscapement .
-
-
+XmbTextEscapement
+XwcTextEscapement
@@ -3134,8 +3134,8 @@ use
XmbTextExtents
or
XwcTextExtents .
-
-
+XmbTextExtents
+XwcTextExtents
@@ -3294,8 +3294,8 @@ use
XmbTextPerCharExtents
or
XwcTextPerCharExtents .
-
-
+XmbTextPerCharExtents
+XwcTextPerCharExtents
@@ -3541,7 +3541,7 @@ use the following structures:
-
+XmbTextItem
@@ -3556,7 +3556,7 @@ typedef struct {
-
+XwcTextItem
@@ -3576,8 +3576,8 @@ To draw text using multiple font sets in a given drawable, use
XmbDrawText
or
XwcDrawText .
-
-
+XmbDrawText
+XwcDrawText
@@ -3727,8 +3727,8 @@ To draw text using a single font set in a given drawable, use
XmbDrawString
or
XwcDrawString .
-
-
+XmbDrawString
+XwcDrawString
@@ -3873,8 +3873,8 @@ To draw image text using a single font set in a given drawable, use
XmbDrawImageString
or
XwcDrawImageString .
-
-
+XmbDrawImageString
+XwcDrawImageString
@@ -5180,7 +5180,7 @@ IM value.
To open a connection, use
XOpenIM .
-
+XOpenIM
@@ -5301,7 +5301,7 @@ returns NULL if no input method could be opened.
To close a connection, use
XCloseIM .
-
+XCloseIM
@@ -5335,7 +5335,7 @@ function closes the specified input method.
To set input method attributes, use
XSetIMValues .
-
+XSetIMValues
@@ -5388,7 +5388,7 @@ correctly.
To query an input method, use
XGetIMValues .
-
+XGetIMValues
@@ -5451,7 +5451,7 @@ with the returned pointer.
To obtain the display associated with an input method, use
XDisplayOfIM .
-
+XDisplayOfIM
@@ -5485,7 +5485,7 @@ function returns the display associated with the specified input method.
To get the locale associated with an input method, use
XLocaleOfIM .
-
+XLocaleOfIM
@@ -5519,7 +5519,7 @@ function returns the locale associated with the specified input method.
To register an input method instantiate callback, use
XRegisterIMInstantiateCallback .
-
+XRegisterIMInstantiateCallback
@@ -5615,7 +5615,7 @@ The function returns
The generic prototype is as follows:
-
+IMInstantiateCallback
@@ -5664,7 +5664,7 @@ Not used for this callback and always passed as NULL.
To unregister an input method instantiation callback, use
XUnregisterIMInstantiateCallback .
-
+XUnregisterIMInstantiateCallback
@@ -5895,17 +5895,17 @@ structure is defined as follows:
-
-
-
-
-
-
-
-
-
-
-
+XIMStyle
+XIMPreeditArea
+XIMPreeditCallbacks
+XIMPreeditPosition
+XIMPreeditNothing
+XIMPreeditNone
+XIMStatusArea
+XIMStatusCallbacks
+XIMStatusNothing
+XIMStatusNone
+XIMStyles
typedef unsigned long XIMStyle;
@@ -5954,11 +5954,11 @@ Only these combinations are supported by the input method.
The preedit category defines what type of support is provided
by the input method for preedit information.
-
-
-
-
-
+XIMPreeditArea
+XIMPreeditPosition
+XIMPreeditCallbacks
+XIMPreeditNothing
+XIMPreeditNone
@@ -6013,10 +6013,10 @@ by the input method for preedit information.
The status category defines what type of support is provided
by the input method for status information.
-
-
-
-
+XIMStatusArea
+XIMStatusCallbacks
+XIMStatusNothing
+XIMStatusNone
@@ -6104,7 +6104,7 @@ or
The generic prototype of this callback function is as follows:
-
+DestroyCallback
@@ -6340,7 +6340,7 @@ they should be registered with the X Consortium.
To create an input context, use
XCreateIC .
-
+XCreateIC
@@ -6433,7 +6433,7 @@ errors.
To destroy an input context, use
XDestroyIC .
-
+XDestroyIC
@@ -6470,7 +6470,7 @@ use
XSetICFocus
and
XUnsetICFocus .
-
+XSetICFocus
@@ -6511,7 +6511,7 @@ does not affect the focus window value.
-
+XUnsetICFocus
@@ -6559,8 +6559,8 @@ To reset the state of an input context to its initial state, use
XmbResetIC
or
XwcResetIC .
-
-
+XmbResetIC
+XwcResetIC
@@ -6635,7 +6635,7 @@ The client should free the returned string by calling
To get the input method associated with an input context, use
XIMOfIC .
-
+XIMOfIC
@@ -6680,7 +6680,7 @@ with a character string using the X Portable Character Set.
To set XIC values, use
XSetICValues .
-
+XSetICValues
@@ -6763,7 +6763,7 @@ errors.
To obtain XIC values, use
XGetICValues .
-
+XGetICValues
@@ -7377,7 +7377,7 @@ and cannot be changed.
-
+XNClientWindow
The
XNClientWindow
argument specifies to the input method the client window in
@@ -7417,7 +7417,7 @@ error can be generated when this value is used by the input method.
-
+XNFocusWindow
The
XNFocusWindow
argument specifies the focus window.
@@ -7473,8 +7473,8 @@ the input method will use the client window as the default focus window.
-
-
+XNResourceName
+XNResourceClass
The
XNResourceName
and
@@ -7499,7 +7499,7 @@ set as resources.
-
+XNGeometryCallback
The
XNGeometryCallback
argument is a structure of type
@@ -7527,7 +7527,7 @@ events that it uses to initiate the change.
-
+XNFilterEvents
The
XNFilterEvents
argument returns the event mask that an input method needs
@@ -7711,8 +7711,8 @@ are as follows:
-
-
+XIMInitialState
+XINPreserveState
@@ -7920,8 +7920,8 @@ If not specified, the default is
-
-
+XNPreeditAttributes
+XNStatusAttributes
The
XNPreeditAttributes
and
@@ -7943,7 +7943,7 @@ The names to be used in these lists are described in the following sections.
-
+XNArea
The value of the
XNArea
argument must be a pointer to a structure of type
@@ -8005,7 +8005,7 @@ the results are undefined.
-
+XNAreaNeeded
When set, the
XNAreaNeeded
argument specifies the geometry suggested by the client for this area
@@ -8042,7 +8042,7 @@ and has no other effect on the input method
-
+XNSpotLocation
The
XNSpotLocation
argument specifies to the input method the coordinates of the spot
@@ -8083,7 +8083,7 @@ should use to allocate colors, a colormap ID, or a standard colormap name.
-
+XNColormap
The
XNColormap
argument is used to specify a colormap ID.
@@ -8095,7 +8095,7 @@ error when it is used by the input method.
-
+XNStdColormap
The
XNStdColormap
argument is used to indicate the name of the standard colormap
@@ -8121,8 +8121,8 @@ the client window colormap becomes the default.
-
-
+XNForeground
+XNBackground
The
XNForeground
and
@@ -8169,7 +8169,7 @@ the default is determined by the input method.
-
+XNFontSet
The
XNFontSet
argument specifies to the input method what font set is to be used.
@@ -8209,7 +8209,7 @@ the default is determined by the input method.
-
+XNCursor
The
XNCursor
argument specifies to the input method what cursor is to be used
@@ -8246,9 +8246,9 @@ are as follows:
-
-
-
+XIMPreeditUnknown
+XIMPreeditEnable
+XIMPreeditDisable
@@ -8316,7 +8316,7 @@ The value of the
argument is a pointer to a structure of type
XIMCallback .
The generic prototype is as follows:
-
+PreeditStateNotifyCallback
@@ -8369,7 +8369,7 @@ structure is defined as follows:
-
+XIMPreeditStateNotifyCallbackStruct
@@ -8404,10 +8404,10 @@ A client that wants to support the input style
must provide a set of preedit callbacks to the input method.
The set of preedit callbacks is as follows:
-
-
-
-
+XNPreeditStartCallback
+XNPreeditDoneCallback
+XNPreeditDrawCallback
+XNPreeditCaretCallback
@@ -8441,9 +8441,9 @@ must provide a set of status callbacks to the input method.
The set of status callbacks is as follows:
-
-
-
+XNStatusStartCallback
+XNStatusDoneCallback
+XNStatusDrawCallback
@@ -8469,8 +8469,8 @@ The set of status callbacks is as follows:
The value of any status or preedit argument is a pointer
to a structure of type
XIMCallback .
-
-
+XIMProc
+XIMCallback
@@ -8534,7 +8534,7 @@ terminate preedit, or update the status area.
All callback procedures follow the generic prototype:
-
+CallbackPrototype
@@ -8606,7 +8606,7 @@ and specific data structure associated with the different reasons.
The geometry callback is triggered by the input method
to indicate that it wants the client to negotiate geometry.
The generic prototype is as follows:
-
+GeometryCallback
@@ -8667,7 +8667,7 @@ The destroy callback is triggered by the input method
when it stops service for any reason.
After the callback is invoked, the input context will be freed by Xlib.
The generic prototype is as follows:
-
+DestroyCallback
@@ -8729,7 +8729,7 @@ to request the client to return the string to be converted. The
returned string may be either a multibyte or wide character string,
with an encoding matching the locale bound to the input context.
The callback prototype is as follows:
-
+StringConversionCallback
@@ -8803,7 +8803,7 @@ structure is defined as follows:
-
+XIMStringConversionCallbackStruct
@@ -8890,7 +8890,7 @@ or
PreeditDoneCallback
callback is triggered to let the toolkit do the setup
or the cleanup for the preedit region.
-
+PreeditStartCallback
@@ -8944,7 +8944,7 @@ will return the maximum size of the preedit string.
A positive number indicates the maximum number of bytes allowed
in the preedit string,
and a value of -1 indicates there is no limit.
-
+PreeditDoneCallback
@@ -9025,7 +9025,7 @@ That string is either a multibyte or wide character string,
whose encoding matches the locale bound to the input context.
The callback prototype
is as follows:
-
+PreeditDrawCallback
@@ -9087,7 +9087,7 @@ structure is defined as follows:
-
+XIMPreeditDrawCallbackStruct
@@ -9195,7 +9195,7 @@ the first and second character.
-
+XIMText
@@ -9333,15 +9333,15 @@ The valid mask names are as follows:
-
-
-
-
-
-
-
-
-
+XIMReverse
+XIMUnderline
+XIMHighlight
+XIMPrimary
+XIMSecondary
+XIMTertiary
+XIMVisibleToForward
+XIMVisibleToBackward
+XIMVisibleCenter
@@ -9411,7 +9411,7 @@ to move the text insertion point in the preedit area
Consequently, input method needs to indicate to the client that it
should move the text insertion point.
It then calls the PreeditCaretCallback.
-
+PreeditCaretCallback
@@ -9472,7 +9472,7 @@ and return, in field position, the new offset value from the initial position.
The
XIMPreeditCaretCallbackStruct
structure is defined as follows:
-
+XIMPreeditCaretCallbackStruct
@@ -9496,7 +9496,7 @@ structure is defined as follows:
-
+XIMCaretStyle
@@ -9514,7 +9514,7 @@ typedef enum {
The
XIMCaretDirection
structure is defined as follows:
-
+XIMCaretDirection
@@ -9538,12 +9538,12 @@ typedef enum {
These values are defined as follows:
-
-
-
-
-
-
+XIMForwardChar
+XIMBackwardChar
+XIMForwardWord
+XIMBackwardWord
+XIMCaretUp
+XIMCaretDown
@@ -9604,12 +9604,12 @@ These values are defined as follows:
-
-
-
-
-
-
+XIMNextLine
+XIMPreviousLine
+XIMLineStart
+XIMLineEnd
+XIMAbsolutePosition
+XIMDontChange
Status Callbacks
@@ -9627,7 +9627,7 @@ callbacks: StatusStartCallback, StatusDoneCallback, and StatusDrawCallback.
When the input context is created or gains focus,
the input method calls the StatusStartCallback callback.
-
+StatusStartCallback
@@ -9684,7 +9684,7 @@ it will not be called again before StatusDoneCallback has been called.
When an input context
is destroyed or when it loses focus, the input method calls StatusDoneCallback.
-
+StatusDoneCallback
@@ -9739,7 +9739,7 @@ The callback may release any data allocated on
When an input context status has to be updated, the input method calls
StatusDrawCallback.
-
+StatusDrawCallback
@@ -9796,8 +9796,8 @@ The
and
XIMStatusDrawCallbackStruct
structures are defined as follows:
-
-
+XIMStatusDataType
+XIMStatusDrawCallbackStruct
@@ -9877,7 +9877,7 @@ Clients should discard filtered events.
To filter an event, use
XFilterEvent .
-
+XFilterEvent
@@ -9960,8 +9960,8 @@ use
XmbLookupString
or
XwcLookupString .
-
-
+XmbLookupString
+XwcLookupString
diff --git a/specs/libX11/CH14.xml b/specs/libX11/CH14.xml
index 3d4a6925..02d3cbdf 100644
--- a/specs/libX11/CH14.xml
+++ b/specs/libX11/CH14.xml
@@ -254,7 +254,7 @@ to manipulate your application's subwindows.
To request that a top-level window be iconified, use
XIconifyWindow .
-
+XIconifyWindow
@@ -328,7 +328,7 @@ otherwise, it returns a zero status.
To request that a top-level window be withdrawn, use
XWithdrawWindow .
-
+XWithdrawWindow
@@ -402,7 +402,7 @@ error.
To request that a top-level window be reconfigured, use
XReconfigureWMWindow .
-
+XReconfigureWMWindow
@@ -518,7 +518,7 @@ as well as its value.
The
XTextProperty
structure contains:
-
+XTextProperty
@@ -575,8 +575,8 @@ structure, use
XmbTextListToTextProperty
or
XwcTextListToTextProperty .
-
-
+XmbTextListToTextProperty
+XwcTextListToTextProperty
@@ -737,8 +737,8 @@ structure, use
XmbTextPropertyToTextList
or
XwcTextPropertyToTextList .
-
-
+XmbTextPropertyToTextList
+XwcTextPropertyToTextList
@@ -896,7 +896,7 @@ use
To free the in-memory data associated with the specified
wide character string list, use
XwcFreeStringList .
-
+XwcFreeStringList
@@ -980,7 +980,7 @@ To set the specified list of strings in the STRING encoding to a
XTextProperty
structure, use
XStringListToTextProperty .
-
+XStringListToTextProperty
@@ -1055,7 +1055,7 @@ To obtain a list of strings from a specified
XTextProperty
structure in the STRING encoding, use
XTextPropertyToStringList .
-
+XTextPropertyToStringList
@@ -1128,7 +1128,7 @@ To free the storage for the list and its contents, use
To free the in-memory data associated with the specified string list, use
XFreeStringList .
-
+XFreeStringList
@@ -1185,7 +1185,7 @@ see sections 14.1.4, 14.1.5, 14.2.1, and 14.2.2, respectively.
To set one of a window's text properties, use
XSetTextProperty .
-
+XSetTextProperty
@@ -1273,7 +1273,7 @@ errors.
To read one of a window's text properties, use
XGetTextProperty .
-
+XGetTextProperty
@@ -1389,7 +1389,7 @@ the WM_NAME property for a given window.
To set a window's WM_NAME property with the supplied convenience function, use
XSetWMName .
-
+XSetWMName
@@ -1449,7 +1449,7 @@ to set the WM_NAME property.
To read a window's WM_NAME property with the supplied convenience function, use
XGetWMName .
-
+XGetWMName
@@ -1521,8 +1521,8 @@ for window names that are encoded as STRING properties.
To assign a name to a window, use
XStoreName .
-
-
+Windowname
+XStoreName
@@ -1595,7 +1595,7 @@ errors.
To get the name of a window, use
XFetchName .
-
+XFetchName
@@ -1683,7 +1683,7 @@ the WM_ICON_NAME property for a given window.
To set a window's WM_ICON_NAME property,
use
XSetWMIconName .
-
+XSetWMIconName
@@ -1744,7 +1744,7 @@ to set the WM_ICON_NAME property.
To read a window's WM_ICON_NAME property,
use
XGetWMIconName .
-
+XGetWMIconName
@@ -1817,8 +1817,8 @@ for window names that are encoded as STRING properties.
To set the name to be displayed in a window's icon, use
XSetIconName .
-
-
+Windowicon name
+XSetIconName
@@ -1880,7 +1880,7 @@ errors.
To get the name a window wants displayed in its icon, use
XGetIconName .
-
+XGetIconName
@@ -2115,7 +2115,7 @@ or the window to be withdrawn.
To set a window's WM_HINTS property, use
XSetWMHints .
-
+XSetWMHints
@@ -2184,7 +2184,7 @@ errors.
To read a window's WM_HINTS property, use