Closed GoogleCodeExporter closed 9 years ago
In OSX:
watasiwaJohn
desu. = わたしわジョんです。
Take note of:
- the capital J
- the newline keypress
That is the desired functionality I would like to see in QIMSYS.
More Info
---------
Also, I thought on the n900:
shift 2x = caps lock
function 2x = function lock
However, I couldn't replicate this just now. Maybe it is useful.
Perhaps there could be another kind of lock:
caps lock + function lock = multi lock.
The point of this is that every kind of lock gives you an extra keyboard of
characters available for direct input.
NOTE: AFAIK, OSX does not make use of caps lock or num lock or other locks with
"input character" Hiragana and "input style" Romaji.
Original comment by j3va...@gmail.com
on 2 Feb 2011 at 9:34
I agree that there should be a direct way to toggle JPN and ENG input on the VK.
Original comment by taike.n...@gmail.com
on 3 Feb 2011 at 3:22
As for Katakana input, is there any difference between DeSu and DESU?
Could you open another issue for lock? I don't want to mix them here.
Original comment by stas...@gmail.com
on 3 Feb 2011 at 5:39
Original comment by stas...@gmail.com
on 3 Feb 2011 at 6:00
Fixed in the commit
http://gitorious.org/qimsys/qimsys/commit/6b12f37fb3f22df47ad2390ffb5ca71dab9294
71
Not tested on N900 though.
Feel free to re-open this issue if you found any problem.
Original comment by stas...@gmail.com
on 4 Feb 2011 at 4:56
On OSX:
desu = です
Desu = デす
dEsu = デす
DEsu = デす
deSu = でス
DeSu = デス
dESu = デス
DESu = デス
desU = でス
DesU = デス
dEsU = デス
DEsU = デス
deSU = でス
DeSU = デス
dESU = デス
DESU = デス
So basically on OSX if ANY part of the romanized kana character is uppercase
the corresponding kana character changes to katakana.
NOTE: OSX acts like caps lock is always off in hiragana entry mode (even if the
led is on).
On the n900 I am not sure what implementation would require less keystrokes or
be easier to type.
Otherwise maybe control shift or another hot key could cycle through:
1. Romaji
2. Hiragana/Kanji
3. Katakana
Original comment by j3va...@gmail.com
on 4 Feb 2011 at 9:55
Thanks for letting me know. I decided to change characters to Katakana when its
first character is uppercase for some performance reason. Let's see if that is
acceptable.
Original comment by stas...@gmail.com
on 5 Feb 2011 at 7:07
Original comment by stas...@gmail.com
on 6 Feb 2011 at 5:22
Original comment by stas...@gmail.com
on 6 Feb 2011 at 5:39
0.2.0
Original comment by stas...@gmail.com
on 24 Feb 2011 at 11:48
Original issue reported on code.google.com by
stas...@gmail.com
on 1 Feb 2011 at 1:13