From ced07197443503272bc7b717e2b87c54c82e9a27 Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Tue, 18 Nov 2014 06:00:22 +0100 Subject: include statement MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- doc/info/mds.texinfo | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) (limited to 'doc/info/mds.texinfo') diff --git a/doc/info/mds.texinfo b/doc/info/mds.texinfo index 0ad9cdc..291c86e 100644 --- a/doc/info/mds.texinfo +++ b/doc/info/mds.texinfo @@ -5173,6 +5173,7 @@ line feeds for new lines. * Sequence Mapping:: Implementing dead keys and compositions. * Keyboard Layout Identification:: Specifing the layout language, country and variant. * Layout Assumptions:: Making assumption about the keyboard layout. +* Include Statement:: Including base files. @end menu @@ -5523,6 +5524,30 @@ end assumption +@node Include Statement +@subsection Include Statement + +Writing layout files from scratch is probably something +you want to avoid. For instance you would we need to +create mappings for `A' to `Z' and `0' to `9' (assuming +its a latin-based language), and map up all specific key, +like modifiers, space, arrow keys, and the keypad. And +you would have to make sure do only that the keys are +mapped but that they are mapped to the text the should +product and that they word correcly with the modifiers. +These are things most keyboards have in common with many +other layouts. + +For instance @file{layout/sv/qwerty} has two include +statements to implement its basics: + +@example +include "../common/qwerty" +include "../common/base" +@end example + + + @node Discussion @chapter Discussion -- cgit v1.2.3-70-g09d2