3 ms·

Typing in hiragana directly in theory would allow to double the typing speed because one hiragana character is equivalent to 2-3 latin charcters.

Blikkentrekker 5y ago
They would have to be moved further apart so that doesn't matter. I would even argue that having to have a larger keyboard and moving the hands more would greatly offset that.
- otagekki 5y ago
  The thing is you don't even need to have a bigger keyboard: there is currently an input method that maps every key to a given kana. Not sure why it isn't more widespread though
  - Blikkentrekker 5y ago
    There aren't enough keys for that, especially with the many digraphs that exist. It's simply far more convenient to say type <kya> and receive <きゃ> than some method to enter the small <や>. The standard method of entering <ん> with either <n> or <nn> depending on context is silly, however, and I simply have it on the otherwise unused <l>.
    - jogu 5y ago
      Why is <n> vs <nn> depending on context silly? Context is required to disambiguate ん vs an initial consonant of the な行. There's not really another choice unless you want to make <n> exclusively used for one or the other, which also isn't great. <l> is also not unused, it's a prefix for the smaller version of characters e.g. <le> => ぇ or <ltu> => っ
      - Blikkentrekker 5y ago
        > Why is <n> vs <nn> depending on context silly? Because the Japanese character does not depend on context, it is always <ん> and that one has to enter it differently depending on what follows it is annoying, especially when this can even be another word due to the lack of spaces. It is really counter intuitive to in that scheme to, say, type “一時間歩いた”. > Context is required to disambiguate ん vs an initial consonant of the な行. There's not really another choice unless you want to make <n> exclusively used for one or the other, which also isn't great. My other choice is simple; use <l> to input <ん> at all times since <l> isn't used in Japanese. > <l> is also not unused, it's a prefix for the smaller version of characters e.g. <le> => ぇ or <ltu> => っ That can also be done with <x>, which is the more popular version.

Blikkentrekker 5y ago

They would have to be moved further apart so that doesn't matter. I would even argue that having to have a larger keyboard and moving the hands more would greatly offset that.

otagekki 5y ago
The thing is you don't even need to have a bigger keyboard: there is currently an input method that maps every key to a given kana. Not sure why it isn't more widespread though
- Blikkentrekker 5y ago
  There aren't enough keys for that, especially with the many digraphs that exist. It's simply far more convenient to say type <kya> and receive <きゃ> than some method to enter the small <や>. The standard method of entering <ん> with either <n> or <nn> depending on context is silly, however, and I simply have it on the otherwise unused <l>.
  - jogu 5y ago
    Why is <n> vs <nn> depending on context silly? Context is required to disambiguate ん vs an initial consonant of the な行. There's not really another choice unless you want to make <n> exclusively used for one or the other, which also isn't great. <l> is also not unused, it's a prefix for the smaller version of characters e.g. <le> => ぇ or <ltu> => っ
    - Blikkentrekker 5y ago
      > Why is <n> vs <nn> depending on context silly? Because the Japanese character does not depend on context, it is always <ん> and that one has to enter it differently depending on what follows it is annoying, especially when this can even be another word due to the lack of spaces. It is really counter intuitive to in that scheme to, say, type “一時間歩いた”. > Context is required to disambiguate ん vs an initial consonant of the な行. There's not really another choice unless you want to make <n> exclusively used for one or the other, which also isn't great. My other choice is simple; use <l> to input <ん> at all times since <l> isn't used in Japanese. > <l> is also not unused, it's a prefix for the smaller version of characters e.g. <le> => ぇ or <ltu> => っ That can also be done with <x>, which is the more popular version.