From cb49f95af605bd5019e194eeb656d8789d57756a Mon Sep 17 00:00:00 2001 From: Matt Dew Date: Mon, 3 Oct 2011 18:06:16 -0600 Subject: 1 - fix the capitolization of the ID attriutes to match either the or <funcdef> string it goes with. 2 - fix any <linkend>'s that were affected by 1. 3 - any <function> in the docs that has an actual funcdef, will become an olink. Signed-off-by: Matt Dew <marcoz@osource.org> --- specs/ch03.xml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) (limited to 'specs/ch03.xml') diff --git a/specs/ch03.xml b/specs/ch03.xml index e9ac99c..d71f353 100644 --- a/specs/ch03.xml +++ b/specs/ch03.xml @@ -1,4 +1,4 @@ -<chapter id='virtual_modifiers'> +<chapter id='Virtual_Modifiers'> <title>Virtual Modifiers The core protocol specifies that @@ -80,7 +80,7 @@ XKB puts most aspects of the keyboard under user or program control, so it is even more important to clearly and uniformly refer to modifiers by function. - + Modifier Definitions Use an @@ -156,7 +156,7 @@ Meta. - + Inactive Modifier Definitions Some XKB structures ignore modifier @@ -182,7 +182,7 @@ virtual modifiers are bound. - + Virtual Modifier Mapping XKB maintains a @@ -212,7 +212,7 @@ NumLock The virtual modifier mapping is normally updated automatically whenever actions -are assigned to keys (see Changing +are assigned to keys (see Changing the Keyboard Mapping Using the Core Protocol for details) and few applications should need to change the virtual modifier mapping explicitly. -- cgit v1.2.3