This describes the naming conventions that have to be 
used in order ot define new keyboard layouts or 
keyboard mappings or key translators classes
Thomas Breitfeld, Peppercon AG
======================================================

Kbd-Layout
----------
- primary entity, everything else is based on that
- has to be named with the following scheme:
	KbdLayout_<kbd-layout-name>
- for exmple:
	KbdLayout_102pc

Kbd-Mapping
-----------
- based on one or multiple kbd-layouts
- Mapping for a particular layout should be named as follows:
	KbdMapping-<kbd-layout-name>_<ISO-id>
- for example:
	KbdMapping-102pc_en_US
- generic Mapping should be named as follows:
	KbdMapping_<ISO-id>
- for example:
	KbdMapping_en_US

Key-Translator
--------------
- based on one or multiple kbd-layouts
- Translator for a particular layout should be named as follows:
        KeyTranslator-<kbd-layout-name>_<ISO-id>
- for example:
        KeyTranslator-102pc_en_US
- generic Translator should be named as follows:
        KbdMapping_<ISO-id>
- for example:
        KeyTranslator_en_US         

Kbd-Mapping and Key-Translator search scheme
--------------------------------------------
- search goes always from conrete to generic
- default is stored in a file without any extensions 

ISO-ID
------
- defines language and country settings 
- see files iso639.txt and ISO_3166.html in this folder

