From: William Kendrick <wkendrick@us...> - 2007-04-26 23:24:24
Update of /cvsroot/tuxpaint/tuxpaint/docs
In directory sc8-pr-cvs10.sourceforge.net:/tmp/cvs-serv29396
Briefly documented alternative input methods (IM character map files) in "Extending..."
RCS file: /cvsroot/tuxpaint/tuxpaint/docs/CHANGES.txt,v
retrieving revision 1.394
retrieving revision 1.395
diff -u -d -r1.394 -r1.395
--- CHANGES.txt 26 Apr 2007 23:07:29 -0000 1.394
+++ CHANGES.txt 26 Apr 2007 23:24:17 -0000 1.395
@@ -66,6 +66,9 @@
* Example tuxpaint.conf has been updated to include newer options.
* Briefly documented translation (gettext PO catalogs) in "Extending..."
+ * Briefly documented alternative input methods (IM character map files)
+ in "Extending..."
* Bug Fixes:
RCS file: /cvsroot/tuxpaint/tuxpaint/docs/EXTENDING.txt,v
retrieving revision 1.9
retrieving revision 1.10
diff -u -d -r1.9 -r1.10
--- EXTENDING.txt 26 Apr 2007 23:07:29 -0000 1.9
+++ EXTENDING.txt 26 Apr 2007 23:24:17 -0000 1.10
@@ -571,3 +571,52 @@
request to be added to the "tuxpaint" project and receive write-access
to the CVS source code repository so that you may commit your changes
+Alternative Input Methods
+ As of version 0.9.17, Tux Paint's "Text" tool can provide alternative
+ input methods for some languages. For example, when Tux Paint is running
+ with a Japanese locale, the right [Alt] can be pressed to change between
+ Latin, Romanized Hiragana and Katakana modes. This allows native
+ characters to be entered into the "Text" tool by typing one or more keys
+ on a keyboard with Latin characters (e.g., a US QWERTY keyboard).
+ To create an input method for a new locale, create a text file with a
+ name based on the locale (e.g., "ja" for Japanese), with ".im" as the
+ extension (e.g., "ja.im").
+ The ".im" file can have multiple character mapping sections for
+ different character mapping modes. For example, on a Japanese typing
+ system, typing [K] [A] in Hiragana mode generates a different Unicode
+ character than typing [K] [A] in Katakana mode.
+ Start each character mapping section with the word "section", the follow
+ it with the mappings, one per line. Each line should contain (separated
+ by whitespace):
+ * the Unicode value of the character, in hexadecimal
+ * the keycode sequence (the ASCII characters that must be entered to
+ generate the Unicode character)
+ * a flag (or "-")
+ # Hiragana
+ 304B ka -
+ 304C ga -
+ 304D ki -
+ 304E gi -
+ # Katakana
+ 30AB ka -
+ 30AC ga -
+ 30AD ki -
+ 30AE gi -
+ Note: Blank lines will be ignored, as will any text following a "#"
+ (pound/hash) character -- they can be used to denote comments, as seen
+ in the example above.
+ Note: Flags need to be explained here.