https://bugzilla.novell.com/show_bug.cgi?id=367801
User jbohac@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=367801#c31
--- Comment #31 from Jiri Bohac 2008-09-23 10:01:42 MDT ---
This is my, possibly wrong (!!) idea to determine the screen map for individual
languages:
The screen map should correspond to the encoding that loadkeys loads the
keyboard map in. For Czech, iso-8859-2 is specified in the keymap (sing the
charset keyword), which instructs loadkeys to convert the symbolic names (e.g.
ecaron) to the correct KT_LATIN keycode with the 8859-2 value (instead for
example the cp1250 code which would be used if the keymap was set to cp1250).
So, if there is a "charset" keyword in the keyboard map we use by default for
the language, it will almost definitely be what we need the screen map to be.
Some maps needn't use the charset "keyword", however, because loadkeys will
automatically use the code from the charset that it finds first in its list of
charsets (see ksymtocode() in src/ksyms.c) - for these maps, it should probably
work to simply find a couple of the non-latin1 symbols defined in the map and
look up which table they are first defined in in ksyms.c.
Some maps may be written entirely in unicode, either specifying "charset
unicode" or by specifying the codes directly with the U+xxxx notation(e.g.
bg_bds-utf8.map.gz) These should be OK with the trivial screen map I *think*
;-)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.