diff --git a/specs/libX11/AppC.xml b/specs/libX11/AppC.xml index 2baee2cc..420d7f90 100644 --- a/specs/libX11/AppC.xml +++ b/specs/libX11/AppC.xml @@ -1427,7 +1427,7 @@ structure and so can be cast to a type larger than an 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*. +on a POSIX-compliant system, fp should be cast to type FILE*. XESetFlushGC @@ -3226,7 +3226,7 @@ Portability Considerations Many machine architectures, -including many of the more recent RISC architectures, +including many of the more recent RISC architectures, do not correctly access data at unaligned locations; their compilers pad out structures to preserve this characteristic. Many other machines capable of unaligned references pad inside of structures diff --git a/specs/libX11/AppD.xml b/specs/libX11/AppD.xml index d93c5cda..7d358f98 100644 --- a/specs/libX11/AppD.xml +++ b/specs/libX11/AppD.xml @@ -1145,7 +1145,7 @@ uses resources from the RESOURCE_MANAGER property on the root window of screen zero. If no such property exists, a resource file in the user's home directory is used. -On a POSIX-conformant system, +On a POSIX-conformant system, this file is "$HOME/.Xdefaults" . Files$HOME/.Xdefaults diff --git a/specs/libX11/CH01.xml b/specs/libX11/CH01.xml index cef9c210..ed69c793 100644 --- a/specs/libX11/CH01.xml +++ b/specs/libX11/CH01.xml @@ -735,13 +735,13 @@ Latin-1, plus tab and newline. -POSIX Portable Filename Character Set +POSIX Portable Filename Character Set The set of 65 characters, -which can be used in naming files on a POSIX-compliant host, +which can be used in naming files on a POSIX-compliant host, that are correctly processed in all locales. The set is: diff --git a/specs/libX11/CH02.xml b/specs/libX11/CH02.xml index acee8d70..6c0321f5 100644 --- a/specs/libX11/CH02.xml +++ b/specs/libX11/CH02.xml @@ -83,7 +83,7 @@ XAllPlanes 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, +On a POSIX-conformant system, if the display_name is NULL, it defaults to the value of the DISPLAY environment variable. EnvironmentDISPLAY @@ -97,7 +97,7 @@ The encoding and interpretation of the display name are implementation-dependent. Strings in the Host Portable Character Encoding are supported; support for other characters is implementation-dependent. -On POSIX-conformant systems, +On POSIX-conformant systems, the display name or DISPLAY environment variable can be a string in the format: @@ -141,7 +141,7 @@ You follow the hostname with either a single colon (:) or a double colon (::). 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. +A single CPU can have more than one display. Multiple displays are usually numbered starting with zero. Screen @@ -187,18 +187,18 @@ structure that serves as the connection to the X server and that contains all the information about that X server. XOpenDisplay -connects your application to the X server through TCP +connects your application to the X server through TCP or DECnet communications protocols, or through some local inter-process communication protocol. -ProtocolTCP +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, XOpenDisplay -connects using TCP streams. (If the protocol is specified as "inet", TCP over -IPv4 is used. If the protocol is specified as "inet6", TCP over IPv6 is used. -Otherwise, the implementation determines which IP version is used.) +connects using TCP streams. (If the protocol is specified as "inet", TCP over +IPv4 is used. If the protocol is specified as "inet6", TCP over IPv6 is used. +Otherwise, the implementation determines which IP version is used.) If the hostname and protocol are both not specified, Xlib uses whatever it believes is the fastest transport. If the hostname is a host machine name and a double colon (::) @@ -347,7 +347,7 @@ and can be used in implementing a monochrome application. These pixel values are for permanently allocated entries in the default colormap. -The actual RGB (red, green, and blue) values are settable on some screens +The actual RGB (red, green, and blue) values are settable on some screens and, in any case, may not actually be black or white. The names are intended to convey the expected relative intensity of the colors. @@ -471,7 +471,7 @@ Specifies the connection to the X server. ConnectionNumber XConnectionNumber Both return a connection number for the specified display. -On a POSIX-conformant system, +On a POSIX-conformant system, this is the file descriptor of the connection. @@ -1014,10 +1014,10 @@ Specifies the connection to the X server. Both return the string that was passed to XOpenDisplay when the current display was opened. -On POSIX-conformant systems, +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 +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 diff --git a/specs/libX11/CH03.xml b/specs/libX11/CH03.xml index 26405e30..83cbc35d 100644 --- a/specs/libX11/CH03.xml +++ b/specs/libX11/CH03.xml @@ -56,7 +56,7 @@ visual types clearer. The screen can be color or grayscale, can have a colormap that is writable or read-only, and can also have a colormap whose indices are decomposed into separate -RGB pieces, provided one is not on a grayscale screen. +RGB pieces, provided one is not on a grayscale screen. This leads to the following diagram: @@ -80,7 +80,7 @@ it goes through a look-up stage by indexing into a colormap. Colormaps can be manipulated arbitrarily on some hardware, in limited ways on other hardware, and not at all on other hardware. The visual types affect the colormap and -the RGB values in the following ways: +the RGB values in the following ways: @@ -91,7 +91,7 @@ the RGB values in the following ways: For PseudoColor , a pixel value indexes a colormap to produce -independent RGB values, and the RGB values can be changed dynamically. +independent RGB values, and the RGB values can be changed dynamically. @@ -108,9 +108,9 @@ same value for red, green, and blue in the colormaps. For DirectColor , -a pixel value is decomposed into separate RGB subfields, and each +a pixel value is decomposed into separate RGB subfields, and each subfield separately indexes the colormap for the corresponding value. -The RGB values can be changed dynamically. +The RGB values can be changed dynamically. @@ -118,8 +118,8 @@ The RGB values can be changed dynamically. TrueColor is treated the same way as DirectColor -except that the colormap has predefined, read-only RGB values. -These RGB values are server dependent but provide linear or near-linear +except that the colormap has predefined, read-only RGB values. +These RGB values are server dependent but provide linear or near-linear ramps in each primary. @@ -129,7 +129,7 @@ ramps in each primary. is treated the same way as PseudoColor except that the colormap has predefined, -read-only, server-dependent RGB values. +read-only, server-dependent RGB values. @@ -137,7 +137,7 @@ read-only, server-dependent RGB values. StaticGray is treated the same way as StaticColor -except that the RGB values are equal for any single pixel +except that the RGB values are equal for any single pixel value, thus resulting in shades of gray. StaticGray with a two-entry @@ -155,7 +155,7 @@ Each has one contiguous set of bits with no intersections. The bits_per_rgb member specifies the log base 2 of the number of distinct color values (individually) of red, green, and blue. -Actual RGB values are unsigned 16-bit numbers. +Actual RGB values are unsigned 16-bit numbers. The colormap_size member defines the number of available colormap entries in a newly created colormap. For diff --git a/specs/libX11/CH05.xml b/specs/libX11/CH05.xml index 5aa6cfaf..73b6c579 100644 --- a/specs/libX11/CH05.xml +++ b/specs/libX11/CH05.xml @@ -361,7 +361,7 @@ Specifies the glyph character for the mask. -Specifies the RGB values for the foreground of the source. +Specifies the RGB values for the foreground of the source. @@ -371,7 +371,7 @@ Specifies the RGB values for the foreground of the source. -Specifies the RGB values for the background of the source. +Specifies the RGB values for the background of the source. @@ -482,7 +482,7 @@ Specifies the cursor's source bits to be displayed or -Specifies the RGB values for the foreground of the source. +Specifies the RGB values for the foreground of the source. @@ -492,7 +492,7 @@ Specifies the RGB values for the foreground of the source. -Specifies the RGB values for the background of the source. +Specifies the RGB values for the background of the source. @@ -526,7 +526,7 @@ Specify the x and y coordinates(Xy. The XCreatePixmapCursor function creates a cursor and returns the cursor ID associated with it. -The foreground and background RGB values must be specified using +The foreground and background RGB values must be specified using foreground_color and background_color, even if the X server only has a StaticGray @@ -719,7 +719,7 @@ Specifies the cursor. -Specifies the RGB values for the foreground of the source. +Specifies the RGB values for the foreground of the source. @@ -729,7 +729,7 @@ Specifies the RGB values for the foreground of the source. -Specifies the RGB values for the background of the source. +Specifies the RGB values for the background of the source. @@ -745,7 +745,7 @@ if the cursor is being displayed on a screen, the change is visible immediately. The pixel members of the XColor -structures are ignored; only the RGB values are used. +structures are ignored; only the RGB values are used. diff --git a/specs/libX11/CH06.xml b/specs/libX11/CH06.xml index f61020fd..6464457f 100644 --- a/specs/libX11/CH06.xml +++ b/specs/libX11/CH06.xml @@ -16,15 +16,15 @@ Each X window always has an associated colormap that provides a level of indirection between pixel values and colors displayed on the screen. Xlib provides functions that you can use to manipulate a colormap. -The X protocol defines colors using values in the RGB color space. -The RGB color space is device dependent; -rendering an RGB value on differing output devices typically results +The X protocol defines colors using values in the RGB color space. +The RGB color space is device dependent; +rendering an RGB value on differing output devices typically results in different colors. Xlib also provides a means for clients to specify color using device-independent color spaces for consistent results across devices. -Xlib supports device-independent color spaces derivable from the CIE XYZ +Xlib supports device-independent color spaces derivable from the CIE XYZ color space. -This includes the CIE XYZ, xyY, L*u*v*, and L*a*b* color spaces as well as +This includes the CIE XYZ, xyY, L*u*v*, and L*a*b* color spaces as well as the TekHVC color space. @@ -90,12 +90,12 @@ there is a color cell in the colormap. For example, if a window is 4 bits deep, pixel values 0 through 15 are defined. A colormap is a collection of color cells. -A color cell consists of a triple of red, green, and blue (RGB) values. +A color cell consists of a triple of red, green, and blue (RGB) values. The hardware imposes limits on the number of significant bits in these values. As each pixel is read out of display memory, the pixel is looked up in a colormap. -The RGB value of the cell determines what color is displayed on the screen. +The RGB value of the cell determines what color is displayed on the screen. On a grayscale display with a black-and-white monitor, the values are combined to determine the brightness on the screen. @@ -106,11 +106,11 @@ to obtain the desired colors. The client can allocate read-only cells. In which case, the pixel values for these colors can be shared among multiple applications, -and the RGB value of the cell cannot be changed. +and the RGB value of the cell cannot be changed. If the client allocates read/write cells, they are exclusively owned by the client, and the color associated with the pixel value can be changed at will. -Cells must be allocated (and, if read/write, initialized with an RGB value) +Cells must be allocated (and, if read/write, initialized with an RGB value) by a client to obtain desired colors. The use of pixel value for an unallocated cell results in an undefined color. @@ -172,7 +172,7 @@ or -Functions that operate only on RGB color space values use an +Functions that operate only on RGB color space values use an XColor structure, which contains: @@ -430,7 +430,7 @@ The device-dependent formats provided allow color specification in: -RGB Intensity +RGB Intensity ( XcmsRGBi ) @@ -443,7 +443,7 @@ where 1.0 indicates full intensity, 0.5 half intensity, and so on. -RGB Device +RGB Device ( XcmsRGB ) @@ -461,14 +461,14 @@ structure. -It is important to note that RGB Intensity values are not gamma corrected +It is important to note that RGB Intensity values are not gamma corrected values. In contrast, -RGB Device values generated as a result of converting color specifications +RGB Device values generated as a result of converting color specifications are always gamma corrected, and -RGB Device values acquired as a result of querying a colormap +RGB Device values acquired as a result of querying a colormap or passed in by the client are assumed by Xlib to be gamma corrected. -The term RGB value in this manual always refers to an RGB Device value. +The term RGB value in this manual always refers to an RGB Device value. @@ -561,13 +561,13 @@ The syntax and semantics of numerical specifications are given for each standard color space in the following sections. -RGB Device String Specification +<acronym>RGB</acronym> Device String Specification - + -An RGB Device specification is identified by +An RGB Device specification is identified by the prefix ``rgb:'' and conforms to the following syntax: @@ -597,7 +597,7 @@ are also allowed. -For backward compatibility, an older syntax for RGB Device is +For backward compatibility, an older syntax for RGB Device is supported, but its continued use is not encouraged. The syntax is an initial sharp sign character followed by a numeric specification, in one of the following formats: @@ -625,13 +625,13 @@ For example, the string ``#3a7'' is the same as ``#3000a0007000''. -RGB Intensity String Specification +<acronym>RGB</acronym> Intensity String Specification -An RGB intensity specification is identified +An RGB intensity specification is identified by the prefix ``rgbi:'' and conforms to the following syntax: @@ -1104,7 +1104,7 @@ error. -To map a color name to an RGB value, use +To map a color name to an RGB value, use XLookupColor . Colornaming XLookupColor @@ -1158,7 +1158,7 @@ definition structure you want returned. -Returns the exact RGB values. +Returns the exact RGB values. @@ -1168,7 +1168,7 @@ Returns the exact RGB values. -Returns the closest RGB values provided by the hardware. +Returns the closest RGB values provided by the hardware. @@ -1201,7 +1201,7 @@ error. -To map a color name to the exact RGB value, use +To map a color name to the exact RGB value, use XParseColor . Colornaming @@ -1425,7 +1425,7 @@ 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. +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. @@ -1445,7 +1445,7 @@ times, the server counts each such allocation, not just the first one. -To allocate a read-only color cell with an RGB value, use +To allocate a read-only color cell with an RGB value, use XAllocColor . Allocationread-only colormap cells @@ -1501,11 +1501,11 @@ Specifies and returns the values actually used in the colormap. The XAllocColor function allocates a read-only colormap entry corresponding to the closest -RGB value supported by the hardware. +RGB value supported by the hardware. XAllocColor returns the pixel value of the color closest to the specified -RGB elements supported by the hardware -and returns the RGB value actually used. +RGB elements supported by the hardware +and returns the RGB value actually used. The corresponding colormap cell is read-only. In addition, XAllocColor @@ -1514,7 +1514,7 @@ returns nonzero if it succeeded or zero if it failed. Colorallocation Allocationcolormap read-only colormap cells -Multiple clients that request the same effective RGB value can be assigned +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. XAllocColor @@ -1611,12 +1611,12 @@ function ultimately calls to allocate a read-only color cell (colormap entry) with the specified color. XcmsAllocColor first converts the color specified -to an RGB value and then passes this to +to an RGB value and then passes this to XAllocColor . XcmsAllocColor returns the pixel value of the color cell and the color specification actually allocated. -This returned color specification is the result of converting the RGB value +This returned color specification is the result of converting the RGB value returned by XAllocColor into the format specified with the result_format argument. @@ -1639,7 +1639,7 @@ error. To allocate a read-only color cell using a color name and return the closest -color supported by the hardware in RGB format, use +color supported by the hardware in RGB format, use XAllocNamedColor . Allocationread-only colormap cells @@ -1696,7 +1696,7 @@ definition structure you want returned. -Returns the closest RGB values provided by the hardware. +Returns the closest RGB values provided by the hardware. @@ -1706,7 +1706,7 @@ Returns the closest RGB values provided by the hardware. -Returns the exact RGB values. +Returns the exact RGB values. @@ -1860,7 +1860,7 @@ The color string is parsed into an structure (see XcmsLookupColor ), converted -to an RGB value, and finally passed to +to an RGB value, and finally passed to XAllocColor . If the color name is not in the Host Portable Character Encoding, the result is implementation-dependent. @@ -1871,7 +1871,7 @@ Use of uppercase or lowercase does not matter. This function returns both the color specification as a result of parsing (exact specification) and the actual color specification stored (screen specification). -This screen specification is the result of converting the RGB value +This screen specification is the result of converting the RGB value returned by XAllocColor into the format specified in result_format. @@ -2031,7 +2031,7 @@ or and three contiguous sets of bits set to 1 (one within each pixel subfield) for DirectColor . -The RGB values of the allocated +The RGB values of the allocated entries are undefined. XAllocColorCells returns nonzero if it succeeded or zero if it failed. @@ -2393,7 +2393,7 @@ errors. -To store an RGB value in a single colormap cell, use +To store an RGB value in a single colormap cell, use XStoreColor . Colorstoring @@ -2435,7 +2435,7 @@ Specifies the colormap. -Specifies the pixel and RGB values. +Specifies the pixel and RGB values. @@ -2485,7 +2485,7 @@ errors. -To store multiple RGB values in multiple colormap cells, use +To store multiple RGB values in multiple colormap cells, use XStoreColors . Colorstoring @@ -2649,8 +2649,8 @@ The XcmsStoreColor function converts the color specified in the XcmsColor -structure into RGB values. -It then uses this RGB specification in an +structure into RGB values. +It then uses this RGB specification in an XColor structure, whose three flags ( DoRed , @@ -2680,7 +2680,7 @@ Note that has no return value; therefore, an XcmsSuccess return value from this function indicates that the conversion -to RGB succeeded and the call to +to RGB succeeded and the call to XStoreColor was made. To obtain the actual color stored, use @@ -2792,7 +2792,7 @@ The XcmsStoreColors function converts the colors specified in the array of XcmsColor -structures into RGB values and then uses these RGB specifications in +structures into RGB values and then uses these RGB specifications in XColor structures, whose three flags ( DoRed , @@ -2824,7 +2824,7 @@ Note that has no return value; therefore, an XcmsSuccess return value from this function indicates that conversions -to RGB succeeded and the call to +to RGB succeeded and the call to XStoreColors was made. To obtain the actual colors stored, use @@ -2962,7 +2962,7 @@ and XQueryColors functions take pixel values in the pixel member of XColor -structures and store in the structures the RGB values for those +structures and store in the structures the RGB values for those pixels from the specified colormap. The values returned for an unallocated entry are undefined. These functions also set the flags member in the @@ -2977,7 +2977,7 @@ the one that gets reported is arbitrary. -To query the RGB value of a single colormap cell, use +To query the RGB value of a single colormap cell, use XQueryColor . Colorquerying @@ -3019,7 +3019,7 @@ Specifies the colormap. -Specifies and returns the RGB values for the pixel specified in the structure. +Specifies and returns the RGB values for the pixel specified in the structure. @@ -3030,7 +3030,7 @@ Specifies and returns the RGB values for the pixel specified in the structure. The XQueryColor -function returns the current RGB value for the pixel in the +function returns the current RGB value for the pixel in the XColor structure and sets the DoRed , @@ -3051,7 +3051,7 @@ errors. -To query the RGB values of multiple colormap cells, use +To query the RGB values of multiple colormap cells, use XQueryColors . Colorquerying @@ -3119,7 +3119,7 @@ structures in the color definition array. The XQueryColors -function returns the RGB value for each pixel in each +function returns the RGB value for each pixel in each XColor structure and sets the DoRed , @@ -3208,7 +3208,7 @@ Specifies the color format for the returned color specification. The XcmsQueryColor -function obtains the RGB value +function obtains the RGB value for the pixel value in the pixel member of the specified XcmsColor structure and then @@ -3310,7 +3310,7 @@ Specifies the color format for the returned color specification. The XcmsQueryColors -function obtains the RGB values +function obtains the RGB values for pixel values in the pixel members of XcmsColor structures and then @@ -4270,13 +4270,13 @@ the contents of the color specification array are left unchanged. The array may contain a mixture of color specification formats -(for example, 3 CIE XYZ, 2 CIE Luv, and so on). +(for example, 3 CIE XYZ, 2 CIE Luv, and so on). When the array contains both device-independent and device-dependent color specifications and the target_format argument specifies a device-dependent format (for example, XcmsRGBiFormat , XcmsRGBFormat ), -all specifications are converted to CIE XYZ format and then to the target +all specifications are converted to CIE XYZ format and then to the target device-dependent format. @@ -4501,12 +4501,12 @@ The gamut compression callback procedures provided by Xlib are as follows: This brings the encountered out-of-gamut color specification into the -screen's color gamut by reducing or increasing CIE metric lightness (L*) -in the CIE L*a*b* color space until the color is within the gamut. +screen's color gamut by reducing or increasing CIE metric lightness (L*) +in the CIE L*a*b* color space until the color is within the gamut. If the Psychometric Chroma of the color specification is beyond maximum for the Psychometric Hue Angle, then while maintaining the same Psychometric Hue Angle, -the color will be clipped to the CIE L*a*b* coordinates of maximum +the color will be clipped to the CIE L*a*b* coordinates of maximum Psychometric Chroma. See XcmsCIELabQueryMaxC . @@ -4535,7 +4535,7 @@ No client data is necessary. This brings the encountered out-of-gamut color specification into the -screen's color gamut by replacing it with CIE L*a*b* coordinates +screen's color gamut by replacing it with CIE L*a*b* coordinates that fall within the color gamut while maintaining the original Psychometric Hue Angle and whose vector to the original coordinates is the shortest attainable. @@ -4550,12 +4550,12 @@ No client data is necessary. This brings the encountered out-of-gamut color specification into the -screen's color gamut by reducing or increasing CIE metric lightness (L*) -in the CIE L*u*v* color space until the color is within the gamut. +screen's color gamut by reducing or increasing CIE metric lightness (L*) +in the CIE L*u*v* color space until the color is within the gamut. If the Psychometric Chroma of the color specification is beyond maximum for the Psychometric Hue Angle, then, while maintaining the same Psychometric Hue Angle, -the color will be clipped to the CIE L*u*v* coordinates of maximum +the color will be clipped to the CIE L*u*v* coordinates of maximum Psychometric Chroma. See XcmsCIELuvQueryMaxC . @@ -4584,7 +4584,7 @@ No client data is necessary. This brings the encountered out-of-gamut color specification into the -screen's color gamut by replacing it with CIE L*u*v* coordinates +screen's color gamut by replacing it with CIE L*u*v* coordinates that fall within the color gamut while maintaining the original Psychometric Hue Angle and whose vector to the original coordinates is the shortest attainable. @@ -4764,7 +4764,7 @@ White point adjustment procedures provided by Xlib are as follows: -This uses the CIE L*a*b* color space for adjusting the chromatic character +This uses the CIE L*a*b* color space for adjusting the chromatic character of colors to compensate for the chromatic differences between the source and destination white points. This procedure simply converts the color specifications to @@ -4781,7 +4781,7 @@ No client data is necessary. -This uses the CIE L*u*v* color space for adjusting the chromatic character +This uses the CIE L*u*v* color space for adjusting the chromatic character of colors to compensate for the chromatic differences between the source and destination white points. This procedure simply converts the color specifications to @@ -4816,7 +4816,7 @@ No client data is necessary. From an implementation point of view, these white point adjustment procedures convert the color specifications to a device-independent but white-point-dependent color space -(for example, CIE L*u*v*, CIE L*a*b*, TekHVC) using one white point +(for example, CIE L*u*v*, CIE L*a*b*, TekHVC) using one white point and then converting those specifications to the target color space using another white point. In other words, @@ -4824,8 +4824,8 @@ the specification goes in the color space with one white point but comes out with another white point, resulting in a chromatic shift based on the chromatic displacement between the initial white point and target white point. -The CIE color spaces that are assumed to be white-point-independent -are CIE u'v'Y, CIE XYZ, and CIE xyY. +The CIE color spaces that are assumed to be white-point-independent +are CIE u'v'Y, CIE XYZ, and CIE xyY. When developing a custom white point adjustment procedure that uses a device-independent color space not initially accessible for use in the color management system, use @@ -4893,7 +4893,7 @@ From XcmsCIEuvY to XcmsCIEXYZ -(CIE u'v'Y and XYZ are white-point-independent color spaces) +(CIE u'v'Y and XYZ are white-point-independent color spaces) @@ -4915,9 +4915,9 @@ to -The resulting RGB specification is passed to +The resulting RGB specification is passed to XAllocColor , -and the RGB +and the RGB specification returned by XAllocColor is converted back to @@ -4935,7 +4935,7 @@ by reversing the color conversion sequence. 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*, +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 @@ -5348,7 +5348,7 @@ delim %% Psychometric Hue Angle -CIE metric lightness +CIE metric lightness Psychometric Chroma Psychometric Chromamaximum @@ -5357,8 +5357,8 @@ delim %% %CIELab~Psychometric~Hue ~=~ tan sup -1 left [ b_star over a_star right ]% -To obtain the CIE L*a*b* coordinates of maximum Psychometric Chroma -for a given Psychometric Hue Angle and CIE metric lightness (L*), use +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 @@ -5416,7 +5416,7 @@ Specifies the lightness (L*) at which to find (Ls. -Returns the CIE L*a*b* coordinates of (Lc +Returns the CIE L*a*b* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -5433,18 +5433,18 @@ The XcmsCIELabQueryMaxC function, given a hue angle and lightness, finds the point of maximum chroma displayable by the screen. -It returns this point in CIE L*a*b* coordinates. +It returns this point in CIE L*a*b* coordinates. -To obtain the CIE L*a*b* coordinates of maximum CIE metric lightness (L*) +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 +CIE metric lightness +CIE metric lightnessmaximum XcmsCIELabQueryMaxL @@ -5500,7 +5500,7 @@ Specifies the chroma at which to find (Ch. -Returns the CIE L*a*b* coordinates of (Lc +Returns the CIE L*a*b* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -5516,9 +5516,9 @@ The value returned in the pixel member is undefined. The XcmsCIELabQueryMaxL function, given a hue angle and chroma, -finds the point in CIE L*a*b* color space of maximum +finds the point in CIE L*a*b* color space of maximum lightness (L*) displayable by the screen. -It returns this point in CIE L*a*b* coordinates. +It returns this point in CIE L*a*b* coordinates. An XcmsFailure return value usually indicates that the given chroma @@ -5527,15 +5527,15 @@ is beyond maximum for the given hue angle. -To obtain the CIE L*a*b* coordinates of maximum Psychometric Chroma +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 +CIE metric lightness Psychometric Chromamaximum -CIE metric lightnessmaximum +CIE metric lightnessmaximum XcmsCIELabQueryMaxLC @@ -5579,7 +5579,7 @@ Specifies the hue angle (in degrees) at which to find (Ha. -Returns the CIE L*a*b* coordinates of (Lc +Returns the CIE L*a*b* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -5596,18 +5596,18 @@ The XcmsCIELabQueryMaxLC function, given a hue angle, finds the point of maximum chroma displayable by the screen. -It returns this point in CIE L*a*b* coordinates. +It returns this point in CIE L*a*b* coordinates. -To obtain the CIE L*a*b* coordinates of minimum CIE metric lightness (L*) +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 +CIE metric lightness +CIE metric lightnessminimum XcmsCIELabQueryMinL @@ -5663,7 +5663,7 @@ Specifies the chroma at which to find (Ch. -Returns the CIE L*a*b* coordinates of (Lc +Returns the CIE L*a*b* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -5680,7 +5680,7 @@ The XcmsCIELabQueryMinL function, given a hue angle and chroma, finds the point of minimum lightness (L*) displayable by the screen. -It returns this point in CIE L*a*b* coordinates. +It returns this point in CIE L*a*b* coordinates. An XcmsFailure return value usually indicates that the given chroma @@ -5702,7 +5702,7 @@ delim %% Psychometric Hue Angle -CIE metric lightness +CIE metric lightness Psychometric Chroma Psychometric Chromamaximum @@ -5714,8 +5714,8 @@ delim %% -To obtain the CIE L*u*v* coordinates of maximum Psychometric Chroma -for a given Psychometric Hue Angle and CIE metric lightness (L*), use +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 @@ -5773,7 +5773,7 @@ Specifies the lightness (L*) at which to find (Ls. -Returns the CIE L*u*v* coordinates of (Lc +Returns the CIE L*u*v* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -5790,18 +5790,18 @@ The XcmsCIELuvQueryMaxC function, given a hue angle and lightness, finds the point of maximum chroma displayable by the screen. -It returns this point in CIE L*u*v* coordinates. +It returns this point in CIE L*u*v* coordinates. -To obtain the CIE L*u*v* coordinates of maximum CIE metric lightness (L*) +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 +CIE metric lightness +CIE metric lightnessmaximum XcmsCIELuvQueryMaxL @@ -5857,7 +5857,7 @@ Specifies the lightness (L*) at which to find (Ls. -Returns the CIE L*u*v* coordinates of (Lc +Returns the CIE L*u*v* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -5873,9 +5873,9 @@ The value returned in the pixel member is undefined. The XcmsCIELuvQueryMaxL function, given a hue angle and chroma, -finds the point in CIE L*u*v* color space of maximum +finds the point in CIE L*u*v* color space of maximum lightness (L*) displayable by the screen. -It returns this point in CIE L*u*v* coordinates. +It returns this point in CIE L*u*v* coordinates. An XcmsFailure return value usually indicates that the given chroma @@ -5884,15 +5884,15 @@ is beyond maximum for the given hue angle. -To obtain the CIE L*u*v* coordinates of maximum Psychometric Chroma +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 +CIE metric lightness Psychometric Chromamaximum -CIE metric lightnessmaximum +CIE metric lightnessmaximum XcmsCIELuvQueryMaxLC @@ -5936,7 +5936,7 @@ Specifies the hue angle (in degrees) at which to find (Ha. -Returns the CIE L*u*v* coordinates of (Lc +Returns the CIE L*u*v* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -5953,18 +5953,18 @@ The XcmsCIELuvQueryMaxLC function, given a hue angle, finds the point of maximum chroma displayable by the screen. -It returns this point in CIE L*u*v* coordinates. +It returns this point in CIE L*u*v* coordinates. -To obtain the CIE L*u*v* coordinates of minimum CIE metric lightness (L*) +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 +CIE metric lightness +CIE metric lightnessminimum XcmsCIELuvQueryMinL @@ -6020,7 +6020,7 @@ Specifies the chroma at which to find (Ch. -Returns the CIE L*u*v* coordinates of (Lc +Returns the CIE L*u*v* coordinates of (Lc displayable by the screen for the given (lC. The white point associated with the returned color specification is the Screen White Point. @@ -6037,7 +6037,7 @@ The XcmsCIELuvQueryMinL function, given a hue angle and chroma, finds the point of minimum lightness (L*) displayable by the screen. -It returns this point in CIE L*u*v* coordinates. +It returns this point in CIE L*u*v* coordinates. An XcmsFailure return value usually indicates that the given chroma @@ -6479,7 +6479,7 @@ Device-Independent Color Spaces -Device-independent color spaces that are derivable to CIE XYZ +Device-independent color spaces that are derivable to CIE XYZ space can be added using the XcmsAddColorSpace function. @@ -6494,7 +6494,7 @@ Color Characterization Function Set A Color Characterization Function Set consists of device-dependent color spaces and their functions that -convert between these color spaces and the CIE XYZ +convert between these color spaces and the CIE XYZ color space, bundled together for a specific class of output devices. A function set can be added using the XcmsAddFunctionSet @@ -6509,17 +6509,17 @@ function. -The CIE XYZ color space serves as the hub for all +The CIE XYZ color space serves as the hub for all conversions between device-independent and device-dependent color spaces. Therefore, the knowledge to convert an XcmsColor -structure to and from CIE XYZ format is associated with each color space. -For example, conversion from CIE L*u*v* to RGB requires the knowledge -to convert from CIE L*u*v* to CIE XYZ and from CIE XYZ to RGB. +structure to and from CIE XYZ format is associated with each color space. +For example, conversion from CIE L*u*v* to RGB requires the knowledge +to convert from CIE L*u*v* to CIE XYZ and from CIE XYZ to RGB. This knowledge is stored as an array of functions that, when applied in series, will convert the XcmsColor -structure to or from CIE XYZ format. +structure to or from CIE XYZ format. This color specification conversion mechanism facilitates the addition of color spaces. @@ -6528,9 +6528,9 @@ the addition of color spaces. Of course, when converting between only device-independent color spaces or only device-dependent color spaces, shortcuts are taken whenever possible. -For example, conversion from TekHVC to CIE L*u*v* is performed -by intermediate conversion to CIE u*v*Y and then to CIE L*u*v*, -thus bypassing conversion between CIE u*v*Y and CIE XYZ. +For example, conversion from TekHVC to CIE L*u*v* is performed +by intermediate conversion to CIE u*v*Y and then to CIE L*u*v*, +thus bypassing conversion between CIE u*v*Y and CIE XYZ. @@ -6745,8 +6745,8 @@ typedef struct _XcmsColorSpace { The prefix member specifies the prefix that indicates a color string is in this color space's string format. -For example, the strings ``ciexyz'' or ``CIEXYZ'' for CIE XYZ, -and ``rgb'' or ``RGB'' for RGB. +For example, the strings ``ciexyz'' or ``CIEXYZ'' for CIE XYZ, +and ``rgb'' or ``RGB'' for RGB. The prefix is case insensitive. The format member specifies the color specification format. Formats for unregistered color spaces are assigned at run time. @@ -6761,7 +6761,7 @@ each to a NULL terminated list of function pointers. When the list of functions is executed in series, it will convert the color specified in an XcmsColor -structure from/to the current color space format to/from the CIE XYZ format. +structure from/to the current color space format to/from the CIE XYZ format. Each function returns an integer (int): nonzero if it succeeded and zero otherwise. The white point to be associated with the colors is specified @@ -6782,7 +6782,7 @@ for each i, such that 0 <= i < n This allows Xlib to use the shortest conversion path, -thus bypassing CIE XYZ if possible (for example, TekHVC to CIE L*u*v*). +thus bypassing CIE XYZ if possible (for example, TekHVC to CIE L*u*v*). @@ -7084,13 +7084,13 @@ The conversion functions provided by Xlib are: Functions to convert between device-dependent color spaces -and CIE XYZ may differ for different classes of output devices +and CIE XYZ may differ for different classes of output devices (for example, color versus gray monitors). Therefore, the notion of a Color Characterization Function Set has been developed. A function set consists of device-dependent color spaces and the functions that convert color specifications -between these device-dependent color spaces and the CIE XYZ color space +between these device-dependent color spaces and the CIE XYZ color space appropriate for a particular class of output devices. The function set also contains a function that reads color characterization data off root window properties. @@ -7215,7 +7215,7 @@ structures are allowed for a device-dependent color space; however, a function set can reference only one of them. These XcmsColorSpace -structures will differ in the functions to convert to and from CIE XYZ, +structures will differ in the functions to convert to and from CIE XYZ, thus tailored for the specific function set. diff --git a/specs/libX11/CH09.xml b/specs/libX11/CH09.xml index 296ff68f..2f2d1e35 100644 --- a/specs/libX11/CH09.xml +++ b/specs/libX11/CH09.xml @@ -1404,7 +1404,7 @@ The host the window system is running on. -On POSIX-conformant systems, each host listed in the +On POSIX-conformant systems, each host listed in the /etc/X?.hosts file. The ? indicates the number of the @@ -1463,7 +1463,7 @@ typedef struct { The family member specifies which protocol address family to use -(for example, TCP/IP or DECnet) and can be +(for example, TCP/IP or DECnet) and can be FamilyInternet , FamilyInternet6 , FamilyServerInterpreted , @@ -1475,9 +1475,9 @@ The address member specifies a pointer to the address. -For TCP/IP, the address should be in network byte order. -For IP version 4 addresses, the family should be FamilyInternet -and the length should be 4 bytes. For IP version 6 addresses, the +For TCP/IP, the address should be in network byte order. +For IP version 4 addresses, the family should be FamilyInternet +and the length should be 4 bytes. For IP version 6 addresses, the family should be FamilyInternet6 and the length should be 16 bytes. diff --git a/specs/libX11/CH11.xml b/specs/libX11/CH11.xml index fdf0d7f3..9ab88c4f 100644 --- a/specs/libX11/CH11.xml +++ b/specs/libX11/CH11.xml @@ -1809,7 +1809,7 @@ 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, +On POSIX-conformant systems, there is also a global variable _Xdebug that, if set to nonzero before starting a program under a debugger, will force diff --git a/specs/libX11/CH12.xml b/specs/libX11/CH12.xml index 1c45fe1f..961f2e40 100644 --- a/specs/libX11/CH12.xml +++ b/specs/libX11/CH12.xml @@ -2261,7 +2261,7 @@ error. If both the led_mode and led members are specified, -the state of that LED is changed, if possible. +the state of that LED is changed, if possible. The led_mode member can be set to LedModeOn or @@ -2454,8 +2454,8 @@ typedef struct { For the LEDs, -the least significant bit of led_mask corresponds to LED one, -and each bit set to 1 in led_mask indicates an LED that is lit. +the least significant bit of led_mask corresponds to LED one, +and each bit set to 1 in led_mask indicates an LED that is lit. The global_auto_repeat member can be set to AutoRepeatModeOn or diff --git a/specs/libX11/CH13.xml b/specs/libX11/CH13.xml index ce93fdf1..4c6fc408 100644 --- a/specs/libX11/CH13.xml +++ b/specs/libX11/CH13.xml @@ -9,8 +9,8 @@ internationalization is to permit localization without program source modificat tion. -As one of the localization mechanisms, Xlib provides an X Input Method (XIM) functional inter- -face for internationalized text input and an X Output Method (XOM) functional interface for +As one of the localization mechanisms, Xlib provides an X Input Method (XIM) functional inter- +face for internationalized text input and an X Output Method (XOM) functional interface for internationalized text output. @@ -175,11 +175,11 @@ having zero or more concatenated ``@category=category is a category name and value is the (possibly empty) setting for that category. The values are encoded in the current locale. -Category names are restricted to the POSIX Portable Filename Character Set. +Category names are restricted to the POSIX Portable Filename Character Set. -The local host X locale modifiers announcer (on POSIX-compliant systems, +The local host X locale modifiers announcer (on POSIX-compliant systems, the XMODIFIERS environment variable) is appended to the modifier_list to provide default values on the local host. If a given category appears more than once in the list, @@ -377,22 +377,22 @@ the following table describes the locale (and modifiers) dependency: setlocale XOpenIM - XIM input method selection + XIM input method selection XRegisterIMInstantiateCallback - XIM selection + XIM selection XUnregisterIMInstantiateCallback - XIM selection + XIM selection XIM XCreateIC - XIC input method configuration + XIC input method configuration @@ -419,7 +419,7 @@ the following table describes the locale (and modifiers) dependency: setlocale XOpenOM - XOM output method selection + XOM output method selection @@ -429,7 +429,7 @@ the following table describes the locale (and modifiers) dependency: XOM XCreateOC - XOC output method configuration + XOC output method configuration @@ -598,7 +598,7 @@ when it is no longer needed. This section provides discussions of the following X Output Method -(XOM) topics: +(XOM) topics: @@ -896,7 +896,7 @@ To set output method attributes, use Specifies the output method. - + @@ -1051,10 +1051,10 @@ returns the locale associated with the specified output method. -The following table describes how XOM values are interpreted by an +The following table describes how XOM values are interpreted by an output method. -The first column lists the XOM values. The second column indicates -how each of the XOM values are treated by a particular output style. +The first column lists the XOM values. The second column indicates +how each of the XOM values are treated by a particular output style. @@ -1089,7 +1089,7 @@ The following key applies to this table. - XOM Value + XOM Value Key @@ -1323,9 +1323,9 @@ to display that data. There can be multiple output contexts for one output method. The programming interfaces for creating, reading, or modifying an output context use a variable argument list. -The name elements of the argument lists are referred to as XOC values. -It is intended that output methods be controlled by these XOC values. -As new XOC values are created, +The name elements of the argument lists are referred to as XOC values. +It is intended that output methods be controlled by these XOC values. +As new XOC values are created, they should be registered with the X Consortium. An XOC @@ -1367,7 +1367,7 @@ To create an output context, use Specifies the output method. - + @@ -1509,13 +1509,13 @@ respectively, and XGetOCValues . Both functions have a variable-length argument list. -In that argument list, any XOC value's name must be denoted +In that argument list, any XOC value's name must be denoted with a character string using the X Portable Character Set. -To set XOC values, use +To set XOC values, use XSetOCValues . XSetOCValues @@ -1534,7 +1534,7 @@ To set XOC values, use Specifies the output context. - + @@ -1592,7 +1592,7 @@ error. -To obtain XOC values, use +To obtain XOC values, use XGetOCValues . XGetOCValues @@ -1662,12 +1662,12 @@ following a name must point to a location where the value is to be stored. -The following table describes how XOC values are interpreted +The following table describes how XOC values are interpreted by an output method. -The first column lists the XOC values. +The first column lists the XOC values. The second column indicates the alternative interfaces that function identically and are provided for compatibility with previous releases. -The third column indicates how each of the XOC values is treated. +The third column indicates how each of the XOC values is treated. @@ -1713,7 +1713,7 @@ The following keys apply to this table. - XOC Value + XOC Value Alternative Interface Key @@ -1784,25 +1784,25 @@ White space immediately on either side of a separating comma is ignored. -Use of XLFD font names permits Xlib to obtain the fonts needed for a +Use of XLFD font names permits Xlib to obtain the fonts needed for a variety of locales from a single locale-independent base font name. The single base font name should name a family of fonts whose members are encoded in the various charsets needed by the locales of interest. -An XLFD base font name can explicitly name a charset needed for the locale. +An XLFD base font name can explicitly name a charset needed for the locale. This allows the user to specify an exact font for use with a charset required by a locale, fully controlling the font selection. -If a base font name is not an XLFD name, -Xlib will attempt to obtain an XLFD name from the font properties +If a base font name is not an XLFD name, +Xlib will attempt to obtain an XLFD name from the font properties for the font. If Xlib is successful, the XGetOCValues -function will return this XLFD name instead of the client-supplied name. +function will return this XLFD name instead of the client-supplied name. @@ -1818,7 +1818,7 @@ returns NULL. When querying for the XNBaseFontName -XOC value, +XOC value, XGetOCValues returns a null-terminated string identifying the base font names that Xlib used to load the fonts needed for the locale. @@ -1973,7 +1973,7 @@ the resources will not be fully specified. -It is not intended that values that can be set as XOM values be +It is not intended that values that can be set as XOM values be set as resources. @@ -1982,7 +1982,7 @@ When querying for the XNResourceName or XNResourceClass -XOC value, +XOC value, XGetOCValues returns a null-terminated string. This string is owned by Xlib and should not be modified or freed by @@ -2232,25 +2232,25 @@ White space immediately on either side of a separating comma is ignored. -Use of XLFD font names permits Xlib to obtain the fonts needed for a +Use of XLFD font names permits Xlib to obtain the fonts needed for a variety of locales from a single locale-independent base font name. The single base font name should name a family of fonts whose members are encoded in the various charsets needed by the locales of interest. -An XLFD base font name can explicitly name a charset needed for the locale. +An XLFD base font name can explicitly name a charset needed for the locale. This allows the user to specify an exact font for use with a charset required by a locale, fully controlling the font selection. -If a base font name is not an XLFD name, -Xlib will attempt to obtain an XLFD name from the font properties +If a base font name is not an XLFD name, +Xlib will attempt to obtain an XLFD name from the font properties for the font. -If this action is successful in obtaining an XLFD name, the +If this action is successful in obtaining an XLFD name, the XBaseFontNameListOfFontSet -function will return this XLFD name instead of the client-supplied name. +function will return this XLFD name instead of the client-supplied name. @@ -2267,7 +2267,7 @@ of the following cases that names a set of fonts that exist at the server: -The first XLFD-conforming base font name that specifies the required +The first XLFD-conforming base font name that specifies the required charset or a superset of the required charset in its CharSetRegistry and @@ -2280,7 +2280,7 @@ an ISO8859-1 font for an ASCII charset. -The first set of one or more XLFD-conforming base font names +The first set of one or more XLFD-conforming base font names that specify one or more charsets that can be remapped to support the required charset. The Xlib implementation may recognize various mappings @@ -2294,13 +2294,13 @@ if a JIS Roman font is not available. -The first XLFD-conforming font name or the first non-XLFD font name -for which an XLFD font name can be obtained, combined with the +The first XLFD-conforming font name or the first non-XLFD font name +for which an XLFD font name can be obtained, combined with the required charset (replacing the CharSetRegistry and CharSetEncoding -fields in the XLFD font name). +fields in the XLFD font name). As in case 1, the implementation may use a charset that is a superset of the required charset. @@ -2361,7 +2361,7 @@ For example: Alternatively, the user could simply supply a single base font name that allows Xlib to select from all available fonts -that meet certain minimum XLFD property requirements. +that meet certain minimum XLFD property requirements. For example: @@ -2621,10 +2621,10 @@ White space may appear immediately on either side of separating commas. If XCreateFontSet -obtained an XLFD name from the font properties for the font specified -by a non-XLFD base name, the +obtained an XLFD name from the font properties for the font specified +by a non-XLFD base name, the XBaseFontNameListOfFontSet -function will return the XLFD name instead of the non-XLFD base name. +function will return the XLFD name instead of the non-XLFD base name. @@ -4032,7 +4032,7 @@ The behavior for an invalid codepoint is undefined. This section provides discussions of the following X Input Method -(XIM) topics: +(XIM) topics: @@ -4640,7 +4640,7 @@ Otherwise, it will set one of the values. -The client will get the XIC value +The client will get the XIC value XNAreaNeeded . The input method will return its suggested size in this value. The input method should pay attention to any constraints suggested @@ -4649,7 +4649,7 @@ by the client. -The client sets the XIC value +The client sets the XIC value XNArea to inform the input method of the geometry of its window. The client should try to honor the geometry requested by the input method. @@ -4660,7 +4660,7 @@ The input method must accept this geometry. Clients doing geometry management must be aware that setting other -XIC values may affect the geometry desired by an input method. +XIC values may affect the geometry desired by an input method. For example, XNFontSet and @@ -4669,7 +4669,7 @@ may change the geometry desired by the input method. -The table of XIC values (see section 13.5.6) +The table of XIC values (see section 13.5.6) indicates the values that can cause the desired geometry to change when they are set. It is the responsibility of the client to renegotiate the geometry @@ -4728,7 +4728,7 @@ to translations such as those the X Toolkit Intrinsics library provides. -Clients are expected to get the XIC value +Clients are expected to get the XIC value XNFilterEvents and augment the event mask for the client window with that event mask. This mask may be zero. @@ -4821,7 +4821,7 @@ This provides the basics for input methods. In addition to preediting based on key events, a general framework is provided to give a client that desires it more advanced preediting based on the text within the client. This framework is called -string conversion and is provided using XIC values. +string conversion and is provided using XIC values. The fundamental concept of string conversion is to allow the input method to manipulate the client's text independent of any user preediting operation. @@ -4922,10 +4922,10 @@ String conversion support is dependent on the availability of the XNStringConversion or XNStringConversionCallback -XIC values. +XIC values. Because the input method may not support string conversions, clients have to query the availability of string conversion -operations by checking the supported XIC values list by calling +operations by checking the supported XIC values list by calling XGetIMValues with the XNQueryICValuesList @@ -4937,7 +4937,7 @@ The difference between these two values is whether the conversion is invoked by the client or the input method. The XNStringConversion -XIC value is used by clients to request +XIC value is used by clients to request a string conversion from the input method. The client is responsible for determining which events are used to trigger the string conversion and whether the string to be @@ -4953,7 +4953,7 @@ only set one of these values. The XNStringConversionCallback -XIC value is used by the client to notify the input method that +XIC value is used by the client to notify the input method that it will accept requests from the input method for string conversion. If this value is set, it is the input method's responsibility to determine which @@ -5049,7 +5049,7 @@ functions are provided: XSetIMValue, XSetICValue - These functions use the XIM and XIC values, + These functions use the XIM and XIC values, XNDestroyCallback , to allow a client to register a callback procedure to be called when Xlib detects that @@ -5112,7 +5112,7 @@ The HotKey mechanism allows clients to specify a set of keys for this purpose. However, the input method might not allow clients to specify hot keys. Therefore, clients have to query support of hot keys by checking the -supported XIC values list by calling +supported XIC values list by calling XGetIMValues with the XNQueryICValuesList @@ -5143,14 +5143,14 @@ One method is to query the state by calling XGetICValues with the XNPreeditState -XIC value. +XIC value. Another method is to receive notification whenever the preedit state is changed. To receive such notification, an application needs to register a callback by calling XSetICValues with the XNPreeditStateNotifyCallback -XIC value. +XIC value. In order to change the preedit state programmatically, an application needs to call XSetICValues @@ -5163,7 +5163,7 @@ Availability of the preedit state is input method dependent. The input method may not provide the ability to set the state or to retrieve the state programmatically. Therefore, clients have to query availability of preedit state operations by checking the -supported XIC values list by calling +supported XIC values list by calling XGetIMValues with the XNQueryICValuesList @@ -5352,7 +5352,7 @@ To set input method attributes, use Specifies the input method. - + @@ -5434,9 +5434,9 @@ it returns the name of the first argument that could not be obtained. -Each XIM value argument (following a name) must point to -a location where the XIM value is to be stored. -That is, if the XIM value is of type T, +Each XIM value argument (following a name) must point to +a location where the XIM value is to be stored. +That is, if the XIM value is of type T, the argument must be of type T*. If T itself is a pointer type, then @@ -5761,10 +5761,10 @@ if it succeeds; otherwise, it returns -The following table describes how XIM values are interpreted +The following table describes how XIM values are interpreted by an input method. -The first column lists the XIM values. -The second column indicates how each of the XIM values +The first column lists the XIM values. +The second column indicates how each of the XIM values are treated by that input style. @@ -5811,7 +5811,7 @@ The following keys apply to this table. - XIM Value + XIM Value Key @@ -5969,7 +5969,7 @@ by the input method for preedit information. If chosen, the input method would require the client to provide some area values for it to do its preediting. - Refer to XIC values + Refer to XIC values XNArea and XNAreaNeeded . @@ -5978,7 +5978,7 @@ by the input method for preedit information. XIMPreeditPosition If chosen, the input method would require the client to provide positional values. - Refer to XIC values + Refer to XIC values XNSpotLocation and XNFocusWindow . @@ -5987,7 +5987,7 @@ by the input method for preedit information. XIMPreeditCallbacks If chosen, the input method would require the client to define the set of preedit callbacks. - Refer to XIC values + Refer to XIC values XNPreeditStartCallback , XNPreeditDoneCallback , XNPreeditDrawCallback , @@ -6074,7 +6074,7 @@ the resources will not be fully specified. -It is not intended that values that can be set as XIM values be +It is not intended that values that can be set as XIM values be set as resources. @@ -6167,7 +6167,7 @@ A DestroyCallback is always called with a NULL call_data argument. XNQueryIMValuesList and XNQueryICValuesList -are used to query about XIM and XIC values supported by the input method. +are used to query about XIM and XIC values supported by the input method. @@ -6231,7 +6231,7 @@ otherwise, the input method does not use the masks. -Because this XIM value is optional, a client should call +Because this XIM value is optional, a client should call XGetIMValues with argument XNQueryIMValues @@ -6301,7 +6301,7 @@ must be set to -Because this XIM value is optional, a client should call +Because this XIM value is optional, a client should call XGetIMValues with argument XNQueryIMValues @@ -6330,9 +6330,9 @@ to display that data. There may be multiple input contexts for one input method. The programming interfaces for creating, reading, or modifying an input context use a variable argument list. -The name elements of the argument lists are referred to as XIC values. -It is intended that input methods be controlled by these XIC values. -As new XIC values are created, +The name elements of the argument lists are referred to as XIC values. +It is intended that input methods be controlled by these XIC values. +As new XIC values are created, they should be registered with the X Consortium. @@ -6357,7 +6357,7 @@ To create an input context, use Specifies the input method. - + @@ -6667,18 +6667,18 @@ function returns the input method associated with the specified input context. -Xlib provides two functions for setting and reading XIC values, respectively, +Xlib provides two functions for setting and reading XIC values, respectively, XSetICValues and XGetICValues . Both functions have a variable-length argument list. -In that argument list, any XIC value's name must be denoted +In that argument list, any XIC value's name must be denoted with a character string using the X Portable Character Set. -To set XIC values, use +To set XIC values, use XSetICValues . XSetICValues @@ -6697,7 +6697,7 @@ To set XIC values, use Specifies the input context. - + @@ -6761,7 +6761,7 @@ errors. -To obtain XIC values, use +To obtain XIC values, use XGetICValues . XGetICValues @@ -6846,18 +6846,18 @@ applies to each element of the nested list. -The following tables describe how XIC values are interpreted +The following tables describe how XIC values are interpreted by an input method depending on the input style chosen by the user. -The first column lists the XIC values. +The first column lists the XIC values. The second column indicates which values are involved in affecting, negotiating, and setting the geometry of the input method windows. The subentries under the third column indicate the different input styles that are supported. -Each of these columns indicates how each of the XIC values +Each of these columns indicates how each of the XIC values are treated by that input style. @@ -6937,7 +6937,7 @@ The following keys apply to these tables. - XIC Value + XIC Value Geometry Mangement Preedit Callback Preedit Position @@ -7197,7 +7197,7 @@ The following keys apply to these tables. - XIC Value + XIC Value Geomentry Management Status Callback Status Area @@ -7462,7 +7462,7 @@ error can be generated when this value is used by the input method. -When this XIC value is left unspecified, +When this XIC value is left unspecified, the input method will use the client window as the default focus window. @@ -7488,7 +7488,7 @@ the resources will not be fully specified. -It is not intended that values that can be set as XIC values be +It is not intended that values that can be set as XIC values be set as resources. @@ -7598,7 +7598,7 @@ will filter any events that it uses to initiate the conversion. -Because this XIC value is optional, a client should call +Because this XIC value is optional, a client should call XGetIMValues with argument XNQueryICValuesList @@ -7638,7 +7638,7 @@ reconversion, or transliteration conversion on it. -Because this XIC value is optional, a client should call +Because this XIC value is optional, a client should call XGetIMValues with argument XNQueryICValuesList @@ -7697,7 +7697,7 @@ or -The XIC state may be set to its initial state, as specified by the +The XIC state may be set to its initial state, as specified by the XNPreeditState value when XCreateIC @@ -7734,7 +7734,7 @@ and XwcResetIC will return to the initial XNPreeditState -state of the XIC. +state of the XIC. @@ -7744,7 +7744,7 @@ is set, then XmbResetIC and XwcResetIC -will preserve the current state of the XIC. +will preserve the current state of the XIC. @@ -7761,7 +7761,7 @@ values other than those specified above will default to -Because this XIC value is optional, a client should call +Because this XIC value is optional, a client should call XGetIMValues with argument XNQueryICValuesList @@ -7780,7 +7780,7 @@ before using this argument. The XNHotKey -argument specifies the hot key list to the XIC. +argument specifies the hot key list to the XIC. The hot key list is a pointer to the structure of type XIMHotKeyTriggers , which specifies the key events that must be received @@ -7793,7 +7793,7 @@ to -Because this XIC value is optional, a client should call +Because this XIC value is optional, a client should call XGetIMValues with argument XNQueryICValuesList @@ -8052,7 +8052,7 @@ set to XIMPreeditPosition . When specified to any input method other than XIMPreeditPosition , -this XIC value is ignored. +this XIC value is ignored. @@ -8295,7 +8295,7 @@ and -Because this XIC value is optional, a client should call +Because this XIC value is optional, a client should call XGetIMValues with argument XNQueryICValuesList @@ -8385,7 +8385,7 @@ typedef struct _XIMPreeditStateNotifyCallbackStruct { -Because this XIC value is optional, a client should call +Because this XIC value is optional, a client should call XGetIMValues with argument XNQueryICValuesList @@ -8510,7 +8510,7 @@ may cause unexpected results. -XIM callbacks are procedures defined by clients or text drawing packages +XIM callbacks are procedures defined by clients or text drawing packages that are to be called from the input method when selected events occur. Most clients will use a text editing package or a toolkit and, hence, will not need to define such callbacks. @@ -9173,7 +9173,7 @@ says to replace 3 characters beginning at character position 1 with the string in the XIMText structure. -Hence, BCD would be replaced by the value in the structure. +Hence, BCD would be replaced by the value in the structure. @@ -9503,8 +9503,8 @@ structure is defined as follows: typedef enum { XIMIsInvisible, /* Disable caret feedback */ - XIMIsPrimary, /* UI defined caret feedback */ - XIMIsSecondary, /* UI defined caret feedback */ + XIMIsPrimary, /* UI defined caret feedback */ + XIMIsSecondary, /* UI defined caret feedback */ } XIMCaretStyle; diff --git a/specs/libX11/CH14.xml b/specs/libX11/CH14.xml index 02d3cbdf..04e88a09 100644 --- a/specs/libX11/CH14.xml +++ b/specs/libX11/CH14.xml @@ -1,14 +1,14 @@ Inter-Client Communication Functions -The Inter-Client Communication Conventions Manual, hereafter referred to as the ICCCM, +The Inter-Client Communication Conventions Manual, hereafter referred to as the ICCCM, details the X Consortium approved conventions that govern inter-client communications. These conventions ensure peer-to-peer client cooperation in the use of selections, cut buffers, and shared resources as well as client cooperation with window and session managers. For further informa- tion, see the Inter-Client Communication Conventions Manual. -Xlib provides a number of standard properties and programming interfaces that are ICCCM com- +Xlib provides a number of standard properties and programming interfaces that are ICCCM com- pliant. The predefined atoms for some of these properties are defined in the <X11/Xatom.h> header file, where to avoid name conflicts with user symbols their #define name has an XA_ pre- fix. For further information about atoms and properties, see section 4.3. @@ -2259,7 +2259,7 @@ header file. The size of the XSizeHints structure may grow in future releases, as new components are -added to support new ICCCM features. +added to support new ICCCM features. Passing statically allocated instances of this structure into Xlib may result in memory corruption when running against a future release of the library. @@ -2511,7 +2511,7 @@ The function returns the size hints stored in the WM_NORMAL_HINTS property on the specified window. If the property is of type WM_SIZE_HINTS, is of format 32, -and is long enough to contain either an old (pre-ICCCM) +and is long enough to contain either an old (pre-ICCCM) or new size hints structure, XGetWMNormalHints sets the various fields of the @@ -2525,7 +2525,7 @@ Otherwise, it returns a zero status. If XGetWMNormalHints -returns successfully and a pre-ICCCM size hints property is read, +returns successfully and a pre-ICCCM size hints property is read, the supplied_return argument will contain the following bits: @@ -2724,7 +2724,7 @@ The function returns the size hints stored in the specified property on the named window. If the property is of type WM_SIZE_HINTS, is of format 32, -and is long enough to contain either an old (pre-ICCCM) +and is long enough to contain either an old (pre-ICCCM) or new size hints structure, XGetWMSizeHints sets the various fields of the @@ -2743,7 +2743,7 @@ function. If XGetWMSizeHints -returns successfully and a pre-ICCCM size hints property is read, +returns successfully and a pre-ICCCM size hints property is read, the supplied_return argument will contain the following bits: @@ -3953,7 +3953,7 @@ is substituted for res_name. It is assumed that the supplied class_hints.res_name and argv, the RESOURCE_NAME environment variable, and the hostname of the machine are in the encoding of the locale announced for the LC_CTYPE category -(on POSIX-compliant systems, the LC_CTYPE, else LANG environment variable). +(on POSIX-compliant systems, the LC_CTYPE, else LANG environment variable). The corresponding WM_CLASS, WM_COMMAND, and WM_CLIENT_MACHINE properties are typed according to the local host locale announcer. No encoding conversion is performed prior to storage in the properties. @@ -4519,12 +4519,12 @@ to draw a smoothly shaded sphere. At each pixel in the image of the sphere, the program computes the intensity and color of light reflected back to the viewer. -The result of each computation is a triple of red, green, and blue (RGB) +The result of each computation is a triple of red, green, and blue (RGB) coefficients in the range 0.0 to 1.0. To draw the sphere, the program needs a colormap that provides a large range of uniformly distributed colors. The colormap should be arranged so that the program can -convert its RGB triples into pixel values very quickly, +convert its RGB triples into pixel values very quickly, because drawing the entire sphere requires many such conversions. @@ -4788,11 +4788,11 @@ This atom names a property. The value of the property is an array of XStandardColormap structures. -Each entry in the array describes an RGB subset of the default color +Each entry in the array describes an RGB subset of the default color map for the Visual specified by visual_id. -Some applications only need a few RGB colors and +Some applications only need a few RGB colors and may be able to allocate them from the system default colormap. This is the ideal situation because the fewer colormaps that are active in the system the more applications are displayed @@ -4816,7 +4816,7 @@ This atom names a property. The value of the property is an XStandardColormap . -The property defines the best RGB colormap available on +The property defines the best RGB colormap available on the screen. (Of course, this is a subjective evaluation.) Many image processing and three-dimensional applications need to @@ -4974,14 +4974,14 @@ Specifies the property name. The XSetRGBColormaps -function replaces the RGB colormap definition in the specified property +function replaces the RGB colormap definition in the specified property on the named window. If the property does not already exist, XSetRGBColormaps -sets the RGB colormap definition in the specified property +sets the RGB colormap definition in the specified property on the named window. The property is stored with a type of RGB_COLOR_MAP and a format of 32. -Note that it is the caller's responsibility to honor the ICCCM +Note that it is the caller's responsibility to honor the ICCCM restriction that only RGB_DEFAULT_MAP contain more than one definition. @@ -5154,7 +5154,7 @@ Specifies the property name. The XGetRGBColormaps -function returns the RGB colormap definitions stored +function returns the RGB colormap definitions stored in the specified property on the named window. If the property exists, is of type RGB_COLOR_MAP, is of format 32, and is long enough to contain a colormap definition, @@ -5171,7 +5171,7 @@ Otherwise, none of the fields are set, and XGetRGBColormaps returns a zero status. -Note that it is the caller's responsibility to honor the ICCCM +Note that it is the caller's responsibility to honor the ICCCM restriction that only RGB_DEFAULT_MAP contain more than one definition. diff --git a/specs/libX11/credits.xml b/specs/libX11/credits.xml index 506bf822..4f7c4c12 100644 --- a/specs/libX11/credits.xml +++ b/specs/libX11/credits.xml @@ -99,7 +99,7 @@ Release 4 Our thanks go to Jim Fulton (MIT X Consortium) for designing and specifying the new Xlib functions for Inter-Client Communication -Conventions (ICCCM) support. +Conventions (ICCCM) support. We also thank Al Mento of Digital for his continued effort in diff --git a/specs/libX11/glossary.xml b/specs/libX11/glossary.xml index f6684931..c912737f 100644 --- a/specs/libX11/glossary.xml +++ b/specs/libX11/glossary.xml @@ -87,13 +87,13 @@ The CharSetRegistry and CharSetEncoding -fields of an XLFD name identify the charset of the font. -A base font name may be a full XLFD name, with all fourteen '-' delimiters, -or an abbreviated XLFD name containing only the first 12 fields of an XLFD name, +fields of an XLFD name identify the charset of the font. +A base font name may be a full XLFD name, with all fourteen '-' delimiters, +or an abbreviated XLFD name containing only the first 12 fields of an XLFD name, up to but not including CharSetRegistry , -with or without the thirteenth '-', or a non-XLFD name. -Any XLFD fields may contain wild cards. +with or without the thirteenth '-', or a non-XLFD name. +Any XLFD fields may contain wild cards. When creating an @@ -279,11 +279,11 @@ windows for further information about valid window types. Client An application program connects to the window system server by some -interprocess communication (IPC) path, such as a TCP connection or a +interprocess communication (IPC) path, such as a TCP connection or a shared memory buffer. This program is referred to as a client of the window system server. More precisely, -the client is the IPC path itself. +the client is the IPC path itself. A program with multiple paths open to the server is viewed as multiple clients by the protocol. Resource lifetimes are controlled by @@ -347,7 +347,7 @@ The coded representation of a single character in a coded character set. A colormap consists of a set of entries defining color values. The colormap associated with a window is used to display the contents of -the window; each pixel value indexes the colormap to produce an RGB value +the window; each pixel value indexes the colormap to produce an RGB value that drives the guns of a monitor. Depending on hardware limitations, one or more colormaps can be installed at one time so @@ -361,7 +361,7 @@ that windows associated with those maps display with true colors. Connection -The IPC path between the server and client program is known as a connection. +The IPC path between the server and client program is known as a connection. A client program typically (but not necessarily) has one connection to the server over which requests and events are sent. @@ -450,7 +450,7 @@ separate subfields for indexing. The first subfield indexes an array to produce red intensity values. The second subfield indexes a second array to produce blue intensity values. The third subfield indexes a third array to produce green intensity values. -The RGB (red, green, and blue) values in the colormap entry can be +The RGB (red, green, and blue) values in the colormap entry can be changed dynamically. @@ -508,7 +508,7 @@ which appears as: the CharSetRegistry and CharSetEncoding -components of an XLFD +components of an XLFD name; the name of a charset of the locale for which a font could not be found; or an atom which identifies the encoding of a text property or which names an encoding for a text selection target type. @@ -1220,9 +1220,9 @@ which tracks whatever pointing device is attached as the pointer. - POSIX + POSIX -POSIX +POSIX Portable Operating System Interface, ISO/IEC 9945-1 (IEEE Std 1003.1). @@ -1230,11 +1230,11 @@ Portable Operating System Interface, ISO/IEC 9945-1 (IEEE Std 1003.1). - POSIX Portable Filename Character Set + POSIX Portable Filename Character Set -POSIX Portable Filename Character Set +POSIX Portable Filename Character Set -The set of 65 characters which can be used in naming files on a POSIX-compliant +The set of 65 characters which can be used in naming files on a POSIX-compliant host that are correctly processed in all locales. The set is: @@ -1279,9 +1279,9 @@ been defined for the window. PseudoColor is a class of colormap in which a pixel value indexes the colormap entry to -produce an independent RGB value; -that is, the colormap is viewed as an array of triples (RGB values). -The RGB values can be changed dynamically. +produce an independent RGB value; +that is, the colormap is viewed as an array of triples (RGB values). +The RGB values can be changed dynamically. @@ -1358,11 +1358,11 @@ connection over which the resource was created. - RGB values + RGB values -RGB values +RGB values -RGB values are the red, green, and blue intensity values that are used +RGB values are the red, green, and blue intensity values that are used to define a color. These values are always represented as 16-bit, unsigned numbers, with 0 the minimum intensity and 65535 the maximum intensity. @@ -1496,7 +1496,7 @@ The protocol does not constrain the semantics. The server, which is also referred to as the X server, provides the basic windowing mechanism. -It handles IPC connections from clients, +It handles IPC connections from clients, multiplexes graphics requests onto the screens, and demultiplexes input back to the appropriate clients. @@ -1589,7 +1589,7 @@ this means use of at most single shifts, not locking shifts. StaticColor can be viewed as a degenerate case of PseudoColor -in which the RGB values are predefined and read-only. +in which the RGB values are predefined and read-only. @@ -1698,9 +1698,9 @@ This value is reserved for use in requests to represent the current server time. TrueColor can be viewed as a degenerate case of DirectColor -in which the subfields in the pixel value directly encode the corresponding RGB +in which the subfields in the pixel value directly encode the corresponding RGB values. -That is, the colormap has predefined read-only RGB values. +That is, the colormap has predefined read-only RGB values. The values are typically linear or near-linear increasing ramps. @@ -1819,9 +1819,9 @@ see the Host Portable Character Encoding. - XLFD + XLFD -XLFD +XLFD The X Logical Font Description Conventions that define a standard syntax for structured font names. @@ -1876,7 +1876,7 @@ character sets - Part 1: Latin alphabet No. 1. -POSIX: Information Technology - Portable Operating System Interface (POSIX) - +<acronym>POSIX</acronym>: Information Technology - Portable Operating System Interface (<acronym>POSIX</acronym>) - Part 1: System Application Program Interface (API) [C Language], ISO/IEC 9945-1.