Using Shift as a Hiragana to Katakana Modifier.

[GoogleCodeExporter]

What version of the product are you using? On what operating system?
qimsys 2011-02-06 on maemo 5

What steps will reproduce the problem?
1. Choose "Input Character: Hiragana" in the preference pane.
2. Choose "Input Style: Romaji" in the preference pane.
3. type "kA"

What is the expected output?
カ

What do you see instead?
か

Additional Info:

OSX is:
ka = か
Ka = カ
kA = カ
KA = カ

NOT:
ka = か
Ka = カ
kA = か
KA = カ

My reasoning for this as a better implementation:
1. If you are trying to press shift when in "Input Character: Hiragana" and 
"Input Style: Romaji" you are most likely trying to make the output character 
into something besides Hiragana.

2. This would make the general rule that if any part of the romanized character 
is capitalized it will be changed to Katakana.

Original issue reported on code.google.com by j3va...@gmail.com on 7 Feb 2011 at 1:17

[GoogleCodeExporter]

Can the current rule be a general rule?

From the performance point of view, checking all characters costs a lot. If you 
really need it, I'll implement it as an option disabled by default on N900.

Original comment by stas...@gmail.com on 7 Feb 2011 at 8:29

• Added labels: Type-Suggestion, OpSys-Maemo, Component-Language
• Removed labels: Type-Bug

[GoogleCodeExporter]

You are right. My #2 isn't really a reason. The general rule can be whatever 
you want. I am just mostly familiar with OSX's implementation. 

More Info:

For the n900 though if performance is an issue I would suggest just having the 
language hotkey (currently control space) just switch through the following 
input modes in order:
romaji
hiragana/kanji
katakana

Instead of just:
english
hiragana/kanji

Perhaps that is easier to implement, and pressing control space 2x isn't really 
any harder that pressing it 1x.

Original comment by j3va...@gmail.com on 7 Feb 2011 at 10:42

[GoogleCodeExporter]

I'm also most familiar with the OS X implementation of Japanese input (Kotoeri) 
so I second #2's comment. It would be nice to have Ctrl+Space cycle through 
Hiragana and Katakana. It would also make sense for in the future (?) when 
qimsys supports more languages, so cycle between all available input modes, 
instead of just turning it on and off and having to pick the input mode with 
the touchscreen.

Original comment by franz%dr...@gtempaccount.com on 7 Feb 2011 at 4:27

[GoogleCodeExporter]

I'm sure just toggling on(Hiragana) and off(Alphabet) is the best way for 
Japanese people. 
* To input only Hiragana and Katakana text is rare case.
* They usually need to convert Hiragana to Kanji (and Katakana!).
* They don't change language so often.

Other shortcut keys might be used to change language or script.

Original comment by stas...@gmail.com on 8 Feb 2011 at 3:04

[GoogleCodeExporter]

In order to make [Shift] more effective as a Hiragana to Katakana modifier it 
is important that QIMSYS does not break [Sticky Key Functionality] on the n900 
hardware keyboard because:
- Single finger [Shift] functionality is possible only with sticky keys.
- Virtual Keyboard behavior and hardware keyboard behavior could then be 
consistent.

Original comment by j3va...@gmail.com on 13 Feb 2011 at 11:36

[GoogleCodeExporter]

I just noticed that you can already use shift or arrow keys to some extent 
under the current implementation.

At the end of entering a Hiragana string just do:
space space
and select the katakana string by either:
1. using space and shift space
2. using the arrow keys.
then to confirm your selection press:
enter

Where "-" is involved you only need:
space

Original comment by j3va...@gmail.com on 14 Feb 2011 at 10:20

[GoogleCodeExporter]

Original comment by stas...@gmail.com on 18 Feb 2011 at 8:11

• Added labels: Milestone-0.3.0