summaryrefslogtreecommitdiff
path: root/specs/ch05.xml
diff options
context:
space:
mode:
authorMatt Dew <marcoz@osource.org>2011-03-15 23:30:15 -0600
committerMatt Dew <marcoz@osource.org>2011-03-21 23:01:15 -0600
commitb82c9b3f752c89d3328c0257d8a386024c9023ee (patch)
tree74abec1e9ef8ed01edc717599e8a6b3047b66290 /specs/ch05.xml
parentc336374f3bf34ce875b29001548470f8d824141e (diff)
Remove duplicate 'See see' text in docs - take 2
Diffstat (limited to 'specs/ch05.xml')
-rw-r--r--specs/ch05.xml16
1 files changed, 10 insertions, 6 deletions
diff --git a/specs/ch05.xml b/specs/ch05.xml
index e712d56..fc9a185 100644
--- a/specs/ch05.xml
+++ b/specs/ch05.xml
@@ -19,7 +19,8 @@ elapsed while the <emphasis>
RepeatKeys</emphasis>
control can cause multiple X events from a single physical key press if the
key is held down for an extended period. The global keyboard controls affect
-all of the keys on the keyboard and are described in <link linkend='global_keyboard_controls'>See Global Keyboard Controls</link>.
+all of the keys on the keyboard and are described in
+<link linkend='global_keyboard_controls'>Global Keyboard Controls</link>.
</para>
</listitem>
<listitem>
@@ -29,7 +30,8 @@ keyboard overlays, in which a key generates an alternate keycode under certain
circumstances, can be implemented using per-key behavior. Every key has a
single behavior, so the effect of key behavior does not depend on keyboard
modifier or group state, though it might depend on global keyboard controls.
-Per-key behaviors are described in detail in <link linkend='key_behavior'>See Key Behavior</link>.
+Per-key behaviors are described in detail in
+<link linkend='key_behavior'>Key Behavior</link>.
</para>
</listitem>
<listitem>
@@ -37,7 +39,7 @@ Per-key behaviors are described in detail in <link linkend='key_behavior'>See Ke
keyboard has some action associated with it. The key action tells the server
what to do when an event which yields the corresponding keysym is generated.
Key actions might change or suppress the event, generate some other event, or
-change some aspect of the server. Key actions are described in <link linkend='key_actions'>See Key Actions</link>.
+change some aspect of the server. Key actions are described in <link linkend='key_actions'>Key Actions</link>.
</para>
</listitem>
</orderedlist>
@@ -50,13 +52,13 @@ event, the client which receives the event processes it in several steps.
<orderedlist>
<listitem>
<para>First the client extracts the effective keyboard group and a set of
-modifiers from the state field of the event. See <link linkend='computing_a_state_field_from_an_xkb_state'>See Computing A State Field from an XKB
+modifiers from the state field of the event. See <link linkend='computing_a_state_field_from_an_xkb_state'>Computing A State Field from an XKB
State</link> for details.
</para>
</listitem>
<listitem>
<para>Using the modifiers and effective keyboard group, the client selects a
-symbol from the list of keysyms bound to the key. <link linkend='determining_the_keysym_associated_with_a_key_event'>See Determining the KeySym Associated with a
+symbol from the list of keysyms bound to the key. <link linkend='determining_the_keysym_associated_with_a_key_event'>Determining the KeySym Associated with a
Key Event</link> discusses symbol selection.
</para>
</listitem>
@@ -66,7 +68,9 @@ using any modifiers that are "left over" from the process of looking up a
symbol. For example, if the <emphasis>
Lock</emphasis>
modifier is left over, the resulting keysym is capitalized according to the
-capitalization rules specified by the system. See <link linkend='transforming_the_keysym_associated_with_a_key_event'>See Transforming the KeySym Associated with a
+capitalization rules specified by the system. See
+<link linkend='transforming_the_keysym_associated_with_a_key_event'>
+Transforming the KeySym Associated with a
Key Event</link> for a more detailed discussion of the transformations defined
by XKB.
</para>