diff options
Diffstat (limited to 'specs/ch16.xml')
| -rw-r--r-- | specs/ch16.xml | 99 |
1 files changed, 55 insertions, 44 deletions
diff --git a/specs/ch16.xml b/specs/ch16.xml index aeaec30..643ebce 100644 --- a/specs/ch16.xml +++ b/specs/ch16.xml @@ -1215,7 +1215,7 @@ affectWhich</emphasis> <para> If any components are specified in a client’s event masks, the X server sends the client an appropriate event whenever any of those components change state. -Unless explicitly modified, all event detail masks are empty. <link linkend='events'>See Events</link> describes all XKB events +Unless explicitly modified, all event detail masks are empty. <link linkend='events'>Events</link> describes all XKB events and the conditions under which the server generates them. </para> @@ -1532,7 +1532,7 @@ effective modifiers minus any server internal modifiers. The <emphasis> grabMods</emphasis> return value reports the grab modifiers, which consist of the lookup modifiers minus any members of the ignore locks mask that are not either latched or -logically depressed. <link linkend='keyboard_state'>See Keyboard +logically depressed. <link linkend='keyboard_state'>Keyboard State</link> describes the lookup modifiers and grab modifiers in more detail. </para> @@ -1556,7 +1556,7 @@ compatGrabMods</emphasis> return values report the core protocol compatibility states that correspond to the XKB lookup and grab state. All of the compatibility states are computed by applying the group compatibility mapping to the corresponding XKB modifier and -group states, as described in <link linkend='group_compatibility_map'>See +group states, as described in <link linkend='group_compatibility_map'> Group Compatibility Map</link>. </para> @@ -1821,13 +1821,14 @@ The <emphasis> numGroups</emphasis> return value reports the current number of groups, and <emphasis> groupsWrap</emphasis> - reports the treatment of out-of-range groups, as described in <link linkend='key_symbol_map'>See Key Symbol Map</link>. The <emphasis> + reports the treatment of out-of-range groups, as described in <link linkend='key_symbol_map'>Key Symbol Map</link>. The <emphasis> internalMods</emphasis> and <emphasis> ignoreLockMods</emphasis> return values report the current values of the server internal and ignore -locks modifiers as described in <link linkend='keyboard_state'>See -Keyboard State</link>. Both are modifier definitions (<link linkend='modifier_definitions'>See Modifier Definitions</link>) which +locks modifiers as described in <link linkend='keyboard_state'> +Keyboard State</link>. Both are modifier definitions ( +<link linkend='modifier_definitions'>Modifier Definitions</link>) which report the real modifiers, virtual modifiers, and the resulting combination of real modifiers that are bound to the corresponding control. </para> @@ -1854,7 +1855,7 @@ mouseKeysMaxSpeed</emphasis> and <emphasis> mouseKeysCurve</emphasis> return values report the current acceleration applied to mouse keys, as -described in <link linkend='the_mousekeysaccel_control'>See The MouseKeysAccel +described in <link linkend='the_mousekeysaccel_control'>The MouseKeysAccel Control</link>. All times are reported in milliseconds. </para> @@ -2221,7 +2222,8 @@ If applied, <emphasis> repeatDelay</emphasis> and <emphasis> repeatInterval</emphasis> - change the autorepeat characteristics of the keyboard, as described in <link linkend='the_repeatkeys_control'>See The RepeatKeys Control</link>. If + change the autorepeat characteristics of the keyboard, as described in +<link linkend='the_repeatkeys_control'>The RepeatKeys Control</link>. If specified, <emphasis> repeatDelay</emphasis> and <emphasis> @@ -2237,7 +2239,7 @@ If applied, the <emphasis> slowKeysDelay</emphasis> field specifies a new delay for the <emphasis> SlowKeys</emphasis> - control, as defined in <link linkend='the_slowkeys_control'>See The + control, as defined in <link linkend='the_slowkeys_control'>The SlowKeys Control</link>. If specified, <emphasis> slowKeysDelay</emphasis> must be non-zero, or a <emphasis> @@ -2251,7 +2253,7 @@ If applied, the <emphasis> debounceDelay</emphasis> field specifies a new delay for the <emphasis> BounceKeys</emphasis> - control, as described in <link linkend='the_bouncekeys_control'>See The + control, as described in <link linkend='the_bouncekeys_control'>The BounceKeys Control</link>. If present, the <emphasis> debounceDelay</emphasis> must be non-zero or a <emphasis> @@ -2272,7 +2274,7 @@ SA_LockPtrBtn</emphasis> mouseKeysDfltBtn</emphasis> must specify a legal button for the core pointer device, or a <emphasis> Value</emphasis> - error results. <link linkend='key_actions'>See Key + error results. <link linkend='key_actions'>Key Actions</link> describes the <emphasis> SA_PtrBtn</emphasis> and <emphasis> @@ -2295,7 +2297,7 @@ mouseKeysCurve</emphasis> fields change the rate at which the pointer moves when a key which generates a <emphasis> SA_MovePtr</emphasis> - action is held down. <link linkend='the_mousekeysaccel_control'>See The + action is held down. <link linkend='the_mousekeysaccel_control'>The MouseKeysAccel Control</link> describes these <emphasis> MouseKeysAccel</emphasis> parameters in more detail. If defined, the <emphasis> @@ -2321,7 +2323,8 @@ Value</emphasis> <para> If applied, the <emphasis> accessXOptions</emphasis> - field sets the AccessX options, which are described in detail in <link linkend='the_accessxkeys_control'>See The AccessXKeys Control</link>. If + field sets the AccessX options, which are described in detail in +<link linkend='the_accessxkeys_control'>The AccessXKeys Control</link>. If either one of <emphasis> XkbStickyKeysMask</emphasis> and <emphasis> @@ -2355,7 +2358,7 @@ accessXTimeoutOptionsMask</emphasis> and <emphasis> accessXTimeoutOptionsValues</emphasis> fields change the behavior of the AccessX Timeout control, as described in -<link linkend='the_accessxtimeout_control'>See The AccessXTimeout +<link linkend='the_accessxtimeout_control'>The AccessXTimeout Control</link>. The <emphasis> accessXTimeout</emphasis> must be greater than zero, or a <emphasis> @@ -2383,7 +2386,7 @@ Match</emphasis> If present, the <emphasis> groupsWrap</emphasis> field specifies the treatment of out-of-range keyboard groups, as described in -<link linkend='key_symbol_map'>See Key Symbol Map</link>. If the +<link linkend='key_symbol_map'>Key Symbol Map</link>. If the <emphasis> groupsWrap</emphasis> field does not specify a legal treatment for out-of-range groups, a <emphasis> @@ -3323,7 +3326,7 @@ flags</emphasis> last key type specified by this request is the last element in the list. If the list of key types is shrunk, any existing key definitions that use key types that eliminated are automatically assigned key types from the list of canonical -key types as described in <link linkend='assigning_types_to_groups_of_symbols_for_a_key'>See +key types as described in <link linkend='assigning_types_to_groups_of_symbols_for_a_key'> Assigning Types To Groups of Symbols for a Key</link>. The list of key types bound to a keyboard must always include the four canonical types and cannot have more than <emphasis> @@ -3736,7 +3739,8 @@ XkbSetMapRecomputeActions</emphasis> bit is set in <emphasis> flags</emphasis> , the actions associated with any keys for which symbol or modifier bindings -were changed by this request are recomputed as described in <link linkend='assigning_actions_to_keys'>See Assigning Actions To Keys</link>. Note +were changed by this request are recomputed as described in +<link linkend='assigning_actions_to_keys'>Assigning Actions To Keys</link>. Note that actions are recomputed <emphasis> after </emphasis> any actions specified in this request are bound to keys, so the actions @@ -4082,7 +4086,7 @@ recomputeActions</emphasis> True</emphasis> , the server regenerates recalculates the actions bound to all keyboard keys by applying the new symbol interpretations to the entire key symbol map, as -described in <link linkend='assigning_actions_to_keys'>See Assigning Actions To +described in <link linkend='assigning_actions_to_keys'>Assigning Actions To Keys</link>. </para> @@ -4239,7 +4243,7 @@ XkbIndicatorStateNotify</emphasis> The <emphasis> maps</emphasis> return value reports the requested indicator maps. Indicator maps are -described in <link linkend='indicator_maps'>See Indicator Maps</link> +described in <link linkend='indicator_maps'>Indicator Maps</link> </para> @@ -4713,7 +4717,7 @@ If <emphasis> setMap </emphasis> is <emphasis> True</emphasis> -, XKB changes the map for the indicator (see <link linkend='indicator_maps'>See Indicator Maps</link>) to reflect the +, XKB changes the map for the indicator (see <link linkend='indicator_maps'>Indicator Maps</link>) to reflect the values specified in <emphasis> map</emphasis> . @@ -5522,7 +5526,7 @@ name</emphasis> is a valid atom other than <emphasis> None</emphasis> , the server returns the keyboard geometry description with that name in the -server database of keyboard components (see <link linkend='the_server_database_of_keyboard_components'>See The Server Database of Keyboard +server database of keyboard components (see <link linkend='the_server_database_of_keyboard_components'>The Server Database of Keyboard Components</link>) if one exists. If <emphasis> deviceSpec</emphasis> does not specify a valid keyboard device, a <emphasis> @@ -5562,7 +5566,7 @@ found</emphasis> True</emphasis> , the remaining fields of the reply describe the requested keyboard geometry. The interpretation of the components that make up a keyboard geometry is -described in detail in <link linkend='keyboard_geometry'>See Keyboard +described in detail in <link linkend='keyboard_geometry'>Keyboard Geometry</link> </para> @@ -5855,35 +5859,35 @@ per-client-flags are: <entry><emphasis> XkbPCF_DetectableAutorepeat</emphasis> </entry> - <entry><link linkend='detectable_autorepeat'>See Detectable + <entry><link linkend='detectable_autorepeat'>Detectable Autorepeat</link></entry> </row> <row rowsep='0'> <entry><emphasis> XkbPCF_GrabsUseXKBStateMask</emphasis> </entry> - <entry><link linkend='setting_a_passive_grab_for_an_xkb_state'>See Setting a Passive Grab + <entry><link linkend='setting_a_passive_grab_for_an_xkb_state'>Setting a Passive Grab for an XKB State</link></entry> </row> <row rowsep='0'> <entry><emphasis> XkbPCF_AutoResetControlsMask</emphasis> </entry> - <entry><link linkend='automatic_reset_of_boolean_controls'>See Automatic Reset of + <entry><link linkend='automatic_reset_of_boolean_controls'>Automatic Reset of Boolean Controls</link></entry> </row> <row rowsep='0'> <entry><emphasis> XkbPCF_LookupStateWhenGrabbed</emphasis> </entry> - <entry><link linkend='effects_of_xkb_on_core_protocol_events'>See Effects of XKB on Core + <entry><link linkend='effects_of_xkb_on_core_protocol_events'>Effects of XKB on Core Protocol Events</link></entry> </row> <row rowsep='0'> <entry><emphasis> XkbPCF_SendEventUsesXKBState</emphasis> </entry> - <entry><link linkend='sending_events_to_clients'>See Sending Events to + <entry><link linkend='sending_events_to_clients'>Sending Events to Clients</link></entry> </row> </tbody> @@ -6109,7 +6113,7 @@ components. <para> Each pattern uses the ISO Latin-1 encoding and should contain only parentheses, the wildcard characters "?" and "*" or characters that are permitted in a -component class or member name (see <link linkend='component_names'>See Component Names</link>). Illegal +component class or member name (see <link linkend='component_names'>Component Names</link>). Illegal characters in a pattern are simply ignored; no error results if a pattern contains illegal characters. </para> @@ -6153,14 +6157,14 @@ compatMaps</emphasis> symbols</emphasis> and <emphasis> geometries</emphasis> - return the hints (see <link linkend='component_hints'>See Component + return the hints (see <link linkend='component_hints'>Component Hints</link>) and names of any components from the server database that match the corresponding pattern. </para> <para> -<link linkend='the_server_database_of_keyboard_components'>See The Server Database of Keyboard +<link linkend='the_server_database_of_keyboard_components'>The Server Database of Keyboard Components</link> describes the X server database of keyboard components in more detail. </para> @@ -6300,7 +6304,7 @@ compatMapSpec</emphasis> symbolsSpec</emphasis> and <emphasis> geometrySpec</emphasis> - component expressions (see <link linkend='partial_components_and_combining_multiple_components'>See + component expressions (see <link linkend='partial_components_and_combining_multiple_components'> Partial Components and Combining Multiple Components</link>) specify the database components to be used to assemble the keyboard description. </para> @@ -6410,7 +6414,7 @@ If either field contains a GBN component that depends on some database component for which the request does not supply an expression, XKB automatically substitutes the special pattern "%" which copies the corresponding component from the current keyboard description, as described in -<link linkend='partial_components_and_combining_multiple_components'>See Partial Components and Combining +<link linkend='partial_components_and_combining_multiple_components'>Partial Components and Combining Multiple Components</link>. </para> @@ -6434,7 +6438,8 @@ If all necessary components are both specified and found, the new keyboard description is loaded. If the new keyboard description has a different geometry or keycode range than the previous keyboard description, XKB sends <emphasis> XkbNewKeyboardNotify</emphasis> - events to all interested clients. See <link linkend='replacing_the_keyboard_on_the_fly'>See Replacing the Keyboard + events to all interested clients. See +<link linkend='replacing_the_keyboard_on_the_fly'>Replacing the Keyboard "On-the-Fly"</link> for more information about the effects of replacing the keyboard description on the fly. </para> @@ -6885,7 +6890,9 @@ deviceID</emphasis> which values are being returned. The <emphasis> supported</emphasis> return value reports the set of optional XKB extension device features that -are supported by this implementation (see <link linkend='interactions_between_xkb_and_the_x_input_extension'>See Interactions Between XKB and the X Input +are supported by this implementation (see +<link linkend='interactions_between_xkb_and_the_x_input_extension'> +Interactions Between XKB and the X Input Extension</link>) for the specified device, and the unsupported return value reports any <emphasis> unsupported</emphasis> @@ -7532,7 +7539,7 @@ Once a client receives a new keyboard notify event which reports a new keycode range, the X server reports events from all keys in the new range to that client. Clients that do not request or receive new keyboard notify events receive events only from keys that fall in the last range for legal keys -reported to that client. See <link linkend='replacing_the_keyboard_on_the_fly'>See +reported to that client. See <link linkend='replacing_the_keyboard_on_the_fly'> Replacing the Keyboard "On-the-Fly"</link> for a more detailed explanation. </para> @@ -7898,9 +7905,9 @@ requestMajor, requestMinor: CARD8</entry> </informaltable> <para> -An <emphasis> -XkbStateNotify</emphasis> - event reports that some component of the XKB state (see <link linkend='keyboard_state'>See Keyboard State</link>) has changed. +An <emphasis>XkbStateNotify</emphasis> +event reports that some component of the XKB state (see +<link linkend='keyboard_state'>Keyboard State</link>) has changed. State notify events are usually caused by key or pointer activity, but they can also result from explicit state changes requested by the <emphasis> XkbLatchLockState</emphasis> @@ -7914,7 +7921,8 @@ deviceID</emphasis> field reports the keyboard on which some state component changed. The <emphasis> changed</emphasis> - field reports the XKB state components (see <link linkend='keyboard_state'>See Keyboard State</link>) that have changed + field reports the XKB state components (see +<link linkend='keyboard_state'>Keyboard State</link>) that have changed and contain any combination of: </para> @@ -8163,8 +8171,10 @@ requestMinor: CARD8</entry> An <emphasis> XkbControlsNotify</emphasis> event reports a change in one or more of the global keyboard controls (see -<link linkend='global_keyboard_controls'>See Global Keyboard Controls</link>) -or in the internal modifiers or ignore locks masks (see <link linkend='server_internal_modifiers_and_ignore_locks_behavior'>See Server Internal Modifiers and Ignore +<link linkend='global_keyboard_controls'>Global Keyboard Controls</link>) +or in the internal modifiers or ignore locks masks (see +<link linkend='server_internal_modifiers_and_ignore_locks_behavior'> +Server Internal Modifiers and Ignore Locks Behavior</link>). Controls notify events are usually caused by and <emphasis> XkbSetControls</emphasis> @@ -9167,8 +9177,9 @@ detail</emphasis> slowKeysDelay</emphasis> and <emphasis> debounceDelay</emphasis> - fields always reports the current slow keys acceptance delay (see <link linkend='the_slowkeys_control'>See The SlowKeys Control</link>) and -debounce delay (see <link linkend='the_bouncekeys_control'>See The BounceKeys + fields always reports the current slow keys acceptance delay (see +<link linkend='the_slowkeys_control'>The SlowKeys Control</link>) and +debounce delay (see <link linkend='the_bouncekeys_control'>The BounceKeys Control</link>) for the specified keyboard. </para> @@ -9333,7 +9344,7 @@ extension device feature that is not supported by the XKB implementation in the server for the specified device. The <emphasis> unsupported</emphasis> mask reports the requested features that are not available on the specified -device. See <link linkend='interactions_between_xkb_and_the_x_input_extension'>See Interactions Between +device. See <link linkend='interactions_between_xkb_and_the_x_input_extension'>Interactions Between XKB and the X Input Extension</link> for more information about possible XKB interactions with the X Input Extension. </para> |