Mercurial > kinput2.yaz
comparison cmd/Kinput2.ad @ 1:31f1de16683a
imported patch 01_Kinput2.ad.patch
| author | Yoshiki Yazawa <yaz@honeyplanet.jp> |
|---|---|
| date | Mon, 08 Mar 2010 20:07:05 +0900 |
| parents | 92745d501b9a |
| children | 7280b0ea4b46 5a32b68b627d |
comparison
equal
deleted
inserted
replaced
| 0:92745d501b9a | 1:31f1de16683a |
|---|---|
| 30 *KanjiFont: -misc-fixed-medium-r-normal--14-*-*-*-c-*-jisx0208.1983-0 | 30 *KanjiFont: -misc-fixed-medium-r-normal--14-*-*-*-c-*-jisx0208.1983-0 |
| 31 *KanaFont: -*-fixed-medium-r-normal--14-*-*-*-c-*-jisx0201.1976-0 | 31 *KanaFont: -*-fixed-medium-r-normal--14-*-*-*-c-*-jisx0201.1976-0 |
| 32 !! | 32 !! |
| 33 !! Wnn setup | 33 !! Wnn setup |
| 34 !! | 34 !! |
| 35 !*CcWnn.Jserver: "primary-jserver-host" | 35 *CcWnn.Jserver: unix |
| 36 !*CcWnn.jserver2nd: "secondary-jserver-host-if-any" | 36 !*CcWnn.jserver2nd: localhost |
| 37 *CcWnn.ccdef: ccdef.kinput2 | 37 *CcWnn.ccdef: ccdef.kinput2.egg |
| 38 *CcWnn.wnnEnvrc: /etc/FreeWnn/ja/wnnenvrc | |
| 38 !*CcWnn.wnnEnvrc4: "wnenvrc-file-for-Wnn4" | 39 !*CcWnn.wnnEnvrc4: "wnenvrc-file-for-Wnn4" |
| 39 !*CcWnn.wnnEnvrc6: "wnenvrc-file-for-Wnn6" | 40 !*CcWnn.wnnEnvrc6: "wnenvrc-file-for-Wnn6" |
| 40 !! | 41 !! |
| 41 !! Canna setup for version 2.x, 3.x | 42 !! Canna setup for version 2.x, 3.x |
| 42 !! | 43 !! |
| 43 !*Canna.Cannahost: "canna-host" | 44 *Canna.Cannahost: localhost |
| 44 !*Canna.Cannafile: "canna-initialization-file" | 45 !*Canna.Cannafile: "canna-initialization-file" |
| 45 !! | 46 !! |
| 46 !! Sj3 setup | 47 !! Sj3 setup |
| 47 !*Sj3.sj3serv: "primary-sj3serv-host" | 48 !*Sj3.sj3serv: "primary-sj3serv-host" |
| 48 !*Sj3.sj3serv2: "secondary-sj3serv-host-if-any" | 49 !*Sj3.sj3serv2: "secondary-sj3serv-host-if-any" |
| 90 !! | 91 !! |
| 91 !! conversion protocol dependent resources | 92 !! conversion protocol dependent resources |
| 92 !! | 93 !! |
| 93 ! KinputProtocol | 94 ! KinputProtocol |
| 94 *KinputProtocol.BackwardCompatible: true | 95 *KinputProtocol.BackwardCompatible: true |
| 95 *KinputProtocol.XlcConversionStartKey: Shift<Key>space | 96 !*KinputProtocol.XlcConversionStartKey: Shift<Key>space |
| 96 ! XimpProtocol | 97 ! XimpProtocol |
| 97 *XimpProtocol.ForceDefaultServer: true | 98 *XimpProtocol.ForceDefaultServer: true |
| 98 ! X Input Method Protocol | 99 ! X Input Method Protocol |
| 99 *IMProtocol.locales: ja_JP.SJIS, ja_JP.EUC, ja_JP, japanese, japan, ja | 100 *IMProtocol.locales: ja_JP.SJIS, ja_JP.EUC, ja_JP.UTF-8, ja_JP, japanese, japan, ja, en_US.UTF-8 |
| 100 ! common to XimpProtocol and IMProtocol | 101 ! common to XimpProtocol and IMProtocol |
| 101 *defaultFontList: -misc-fixed-medium-r-normal--14-*-*-*-c-* | 102 *defaultFontList: -misc-fixed-medium-r-normal--14-*-*-*-c-* |
| 102 *ConversionStartKeys: \ | 103 *ConversionStartKeys: Shift<Key>space |
| 103 Shift<Key>space \n\ | 104 ! Shift<Key>space \n\ |
| 104 Ctrl<Key>Kanji | 105 ! Ctrl<Key>Kanji |
| 105 !! | 106 !! |
| 106 !! sending back unused keypress events | 107 !! sending back unused keypress events |
| 107 !! | 108 !! |
| 108 *sendbackKeyPress: True | 109 *sendbackKeyPress: True |
| 109 !! | 110 !! |
| 116 ! If you encounter a strange phenomenon where kinput2's mode display | 117 ! If you encounter a strange phenomenon where kinput2's mode display |
| 117 ! window is flickering and you cannot type in any text, try enabling | 118 ! window is flickering and you cannot type in any text, try enabling |
| 118 ! the following resource. This phenomenon is caused by the incorrent | 119 ! the following resource. This phenomenon is caused by the incorrent |
| 119 ! focus management of your window manager, and this resource avoids | 120 ! focus management of your window manager, and this resource avoids |
| 120 ! it by making the window manager totally ignore the mode window. | 121 ! it by making the window manager totally ignore the mode window. |
| 121 !*OverTheSpotConversion.UseOverrideShellForMode: True | 122 *OverTheSpotConversion.UseOverrideShellForMode: True |
| 123 !! | |
| 124 !! Don't give input focus to the windows of kinput2, they don't need input focus | |
| 125 !! it just causes problems if they get input focus. | |
| 126 !! | |
| 127 !! For example, if you use kinput2 with Canna and open the 'auxShell' window | |
| 128 !! by pressing the 'insert' key a window pops up where special symbols | |
| 129 !! can be selected. If this window gets focus, the selected symbol will not | |
| 130 !! appear in the application until the application gets focus again. This is | |
| 131 !! quite confusing. | |
| 132 !! And there are even some applications where the selected symbol will never appear, | |
| 133 !! not even when the application gets focus again, Gvim currently behaves | |
| 134 !! like that and XIM in Gvim may even become completely unusable after one of | |
| 135 !! the kinput2 windows got focus, making it necessary to restart Gvim to be able | |
| 136 !! to use XIM again. | |
| 137 !! | |
| 138 !! I found no reason why one of kinput2's windows should need input focus. | |
| 139 !! | |
| 140 *SeparateConversion.input: false | |
| 141 *selectionShell.input: false | |
| 142 *auxShell.input: false | |
| 143 |
