diff options
Diffstat (limited to 'specs/ch12.xml')
| -rw-r--r-- | specs/ch12.xml | 54 |
1 files changed, 27 insertions, 27 deletions
diff --git a/specs/ch12.xml b/specs/ch12.xml index d30a213..f37caf1 100644 --- a/specs/ch12.xml +++ b/specs/ch12.xml @@ -1,5 +1,5 @@ -<chapter id='interactions_between_xkb_and_the_core_protocol'> +<chapter id='Interactions_Between_XKB_and_the_Core_Protocol'> <title>Interactions Between XKB and the Core Protocol</title> <para> @@ -49,11 +49,11 @@ This section describes the differences between the core X protocol’s notion of a keyboard mapping and XKB and explains the ways they can interact. </para> -<sect1 id='group_compatibility_map'> +<sect1 id='Group_Compatibility_Map'> <title>Group Compatibility Map</title> <para> -As described in <link linkend='keyboard_state'>Keyboard +As described in <link linkend='Keyboard_State'>Keyboard State</link>, the current keyboard group is reported to XKB-aware clients in bits 13-14 of the state field of many core protocol events. XKB-unaware clients cannot interpret those bits, but they might use a keyboard modifier to @@ -139,7 +139,7 @@ Group4</emphasis> </para> -<sect2 id='setting_a_passive_grab_for_an_xkb_state'> +<sect2 id='Setting_a_Passive_Grab_for_an_XKB_State'> <title>Setting a Passive Grab for an XKB State</title> <para> @@ -192,7 +192,7 @@ or for grabs that are set by some other client. </sect2> </sect1> -<sect1 id='changing_the_keyboard_mapping_using_the_core_protocol'> +<sect1 id='Changing_the_Keyboard_Mapping_Using_the_Core_Protocol'> <title>Changing the Keyboard Mapping Using the Core Protocol</title> <para> @@ -215,7 +215,7 @@ cannot be described using this mapping should use XKB functions directly. </para> -<sect2 id='explicit_keyboard_mapping_components'> +<sect2 id='Explicit_Keyboard_Mapping_Components'> <title>Explicit Keyboard Mapping Components</title> <para> @@ -243,40 +243,40 @@ field for a key can contain any combination of the following values: <entry>ExplicitKeyType1</entry> <entry>Automatic determination of the key type associated with <emphasis> Group1</emphasis> - (see <link linkend='assigning_types_to_groups_of_symbols_for_a_key'>Assigning Types To Groups of + (see <link linkend='Assigning_Types_To_Groups_of_Symbols_for_a_Key'>Assigning Types To Groups of Symbols for a Key</link>)</entry> </row> <row rowsep='0'> <entry>ExplicitKeyType2</entry> <entry>Automatic determination of the key type associated with <emphasis> Group2 </emphasis> -(see <link linkend='assigning_types_to_groups_of_symbols_for_a_key'>Assigning Types To Groups of +(see <link linkend='Assigning_Types_To_Groups_of_Symbols_for_a_Key'>Assigning Types To Groups of Symbols for a Key</link>)</entry> </row> <row rowsep='0'> <entry>ExplicitKeyType3</entry> <entry>Automatic determination of the key type associated with <emphasis> Group3 </emphasis> -(see <link linkend='assigning_types_to_groups_of_symbols_for_a_key'>Assigning Types To Groups of +(see <link linkend='Assigning_Types_To_Groups_of_Symbols_for_a_Key'>Assigning Types To Groups of Symbols for a Key</link>).</entry> </row> <row rowsep='0'> <entry>ExplicitKeyType4</entry> <entry>Automatic determination of the key type associated with <emphasis> Group4 </emphasis> -(see <link linkend='assigning_types_to_groups_of_symbols_for_a_key'>Assigning Types To Groups of +(see <link linkend='Assigning_Types_To_Groups_of_Symbols_for_a_Key'>Assigning Types To Groups of Symbols for a Key</link>).</entry> </row> <row rowsep='0'> <entry>ExplicitInterpret</entry> <entry>Application of any of the fields of a symbol interpretation to the -key in question (see <link linkend='assigning_actions_to_keys'>Assigning +key in question (see <link linkend='Assigning_Actions_To_Keys'>Assigning Actions To Keys</link>).</entry> </row> <row rowsep='0'> <entry>ExplicitAutoRepeat</entry> <entry>Automatic determination of autorepeat status for the key, as -specified in a symbol interpretation (see <link linkend='assigning_actions_to_keys'>Assigning Actions To +specified in a symbol interpretation (see <link linkend='Assigning_Actions_To_Keys'>Assigning Actions To Keys</link>).</entry> </row> <row rowsep='0'> @@ -285,14 +285,14 @@ Keys</link>).</entry> KB_Lock</emphasis> behavior to the key, if the <emphasis> LockingKey</emphasis> - flag is set in a symbol interpretation (see <link linkend='assigning_actions_to_keys'>Assigning Actions To + flag is set in a symbol interpretation (see <link linkend='Assigning_Actions_To_Keys'>Assigning Actions To Keys</link>).</entry> </row> <row rowsep='0'> <entry>ExplicitVModMap</entry> <entry>Automatic determination of the virtual modifier map for the key based on the actions assigned to the key and the symbol interpretations which -match the key (see <link linkend='assigning_actions_to_keys'>Assigning +match the key (see <link linkend='Assigning_Actions_To_Keys'>Assigning Actions To Keys</link>).</entry> </row> </tbody> @@ -300,7 +300,7 @@ Actions To Keys</link>).</entry> </informaltable> </sect2> -<sect2 id='assigning_symbols_to_groups'> +<sect2 id='Assigning_Symbols_To_Groups'> <title>Assigning Symbols To Groups</title> <para> @@ -310,7 +310,7 @@ ChangeKeyboardMapping</emphasis> groups that are defined for the key and the width of each group. The XKB extension does not change key types in response to core protocol <emphasis> SetModifierMapping</emphasis> - requests, but it does choose key actions as described in <link linkend='assigning_actions_to_keys'>Assigning Actions To Keys</link>. + requests, but it does choose key actions as described in <link linkend='Assigning_Actions_To_Keys'>Assigning Actions To Keys</link>. </para> @@ -364,7 +364,7 @@ little more complicated. </para> -<sect3 id="assigning_symbols_to_groups_one_and_two_with_explicitly_defined_key_types"> +<sect3 id='Assigning_Symbols_to_Groups_One_and_Two_with_Explicitly_Defined_Key_Types'> <title>Assigning Symbols to Groups One and Two with Explicitly Defined Key Types</title> <para> @@ -423,7 +423,7 @@ with the core protocol. </sect3> </sect2> -<sect2 id='assigning_types_to_groups_of_symbols_for_a_key'> +<sect2 id='Assigning_Types_To_Groups_of_Symbols_for_a_Key'> <title>Assigning Types To Groups of Symbols for a Key</title> <para> @@ -487,7 +487,7 @@ ALPHABETIC</emphasis> <entry>Describes alphabetic keys that have exactly two symbols per group. The default definition of the <emphasis> ALPHABETIC</emphasis> - type provides shift-cancels-caps behavior as described in <link linkend='key_types'>Key Types</link>. Index <emphasis> + type provides shift-cancels-caps behavior as described in <link linkend='Key_Types'>Key Types</link>. Index <emphasis> 2</emphasis> in any key symbol map specifies key type <emphasis> ALPHABETIC</emphasis> @@ -592,7 +592,7 @@ Group2</emphasis> </sect2> -<sect2 id='assigning_actions_to_keys'> +<sect2 id='Assigning_Actions_To_Keys'> <title>Assigning Actions To Keys</title> <para> @@ -733,7 +733,7 @@ locking key</emphasis> field is set in the symbol interpretation, the behavior of the key is changed to <emphasis> KB_Lock</emphasis> - (see <link linkend='key_behavior'>Key Behavior</link>). The + (see <link linkend='Key_Behavior'>Key Behavior</link>). The <emphasis> ExplicitBehavior</emphasis> component prevents this change. @@ -766,7 +766,7 @@ XkbSetCompatMap</emphasis> </sect2> -<sect2 id='updating_everything_else'> +<sect2 id='Updating_Everything_Else'> <title>Updating Everything Else</title> <para> @@ -780,14 +780,14 @@ indicator maps, internal modifiers or ignore locks modifiers. </sect2> </sect1> -<sect1 id='effects_of_xkb_on_core_protocol_events'> +<sect1 id='Effects_of_XKB_on_Core_Protocol_Events'> <title>Effects of XKB on Core Protocol Events</title> <para> After applying server actions which modify the base, latched or locked modifier or group state of the keyboard, the X server recomputes the effective group and state. Several components of the keyboard state are reported to XKB-aware -clients depending on context (see <link linkend='keyboard_state'> +clients depending on context (see <link linkend='Keyboard_State'> Keyboard State</link> for a detailed description of each of the keyboard state components): </para> @@ -871,7 +871,7 @@ GrabsUseXKBState</emphasis> </sect1> -<sect1 id='effect_of_xkb_on_core_protocol_requests'> +<sect1 id='Effect_of_XKB_on_Core_Protocol_Requests'> <title>Effect of XKB on Core Protocol Requests</title> <para> @@ -963,7 +963,7 @@ by all of the actions associated with the key plus all of the modifiers associated with any virtual modifiers bound to the key by the virtual modifier mapping. If any of the actions associated with a key affect any component of the keyboard group, any modifiers specified in any entry of the group -compatibility map (see <link linkend='group_compatibility_map'>Group +compatibility map (see <link linkend='Group_Compatibility_Map'>Group Compatibility Map</link>) are reported in the modifier mask. The <emphasis> SA_ISOLock</emphasis> action can theoretically affect any modifier, but the modifier map of an @@ -988,7 +988,7 @@ MappingNotify</emphasis> </sect1> -<sect1 id='sending_events_to_clients'> +<sect1 id='Sending_Events_to_Clients'> <title>Sending Events to Clients</title> <para> |