summaryrefslogtreecommitdiff
authorhash <hash>2002-08-12 08:16:25 (UTC)
committer hash <hash>2002-08-12 08:16:25 (UTC)
commita187321047c4b0328dedcfa46eb6ea88d2b50578 (patch) (unidiff)
treee2f9ab5754ff1d28270e8670ade9b6cd23a6a46f
parent1e045c5b7b5278b4a5925ba878cbdbdea9d03e1d (diff)
downloadopie-a187321047c4b0328dedcfa46eb6ea88d2b50578.zip
opie-a187321047c4b0328dedcfa46eb6ea88d2b50578.tar.gz
opie-a187321047c4b0328dedcfa46eb6ea88d2b50578.tar.bz2
how to make keymaps
Diffstat (more/less context) (ignore whitespace changes)
-rw-r--r--share/multikey/README37
1 files changed, 37 insertions, 0 deletions
diff --git a/share/multikey/README b/share/multikey/README
new file mode 100644
index 0000000..4c6bd23
--- a/dev/null
+++ b/share/multikey/README
@@ -0,0 +1,37 @@
1+---- how to make your own keymap file. ----+
2
3first of all, later on you will be able to choose the keymap, but right now it
4selects the keymap according to your language setting. for example, if your
5language is "ko", it will select $OPIE_DIR/share/multikey/ko.keymap for the
6keymap. so if you want to make a german keymap, copy the en.keymap file to
7de.keymap, and edit it.
8
9your best friend is xmbfed. open the unicode font that is in
10$QT_DIR/lib/fonts/unifont.bdf and search for the characters you want to input.
11in the keymap file, the columns are...
12
13+--- row number (there are 5 rows)
14| +- qcode (used for special chars like enter, escape, etc...)
15| |
16v v
171 0 0x36 2
18 ^ ^
19 | |
20 | +---- width of key (default key should be 2)
21 +--- the unicode value (the one you see in xmbded)
22
23so, lets say you want to edit the 5th key on the 2nd row. find the 5th line
24that starts with 2, and replace the 3rd column with the code you found in
25xmbdfed. save the file and test it out by restarting opie. it worked, right?
26if all you see is a square in it's place, that means your default font doesn't
27have that char. go to appearance and change the font to one that has that char.
28
29and if you want, you can have an image as the label instead of the char itself.
30just draw the xpm image in gimp or something, save it, open it in your text
31editor, cut off all the surrounding stuff and leave only the stuff between the
32" chars. place that after your key definition. not too hard, right?
33
34if you have problems, suggestions, or just want to tell me something, you can
35contact me at jake at asdfnews.org
36
37jake richardson