Seigneur_Folken

Q: Did kotoeri changed with Maverick?

I installed Maverick this morning, and what was my surprise when I tried to use Kotoeri on my french keyboad (then Azerty)...

 

Until Mountain Lion, when i was using french language source, my keyboard was on the Azerty mode, and when using Kotoeri, my keyboard was converting to a JIS Keyboard (Japanese Qwerty).
But now, Kotoeri is using the Azerty mode, even when I use a JIS Blutooth Apple Keyboard.

 

The only trick to use the Qwerty mode for Kotoeri is to drag a US keyboard in the language source, then alternate between french language source for french, then US keyboard=>Kotoeri to use the Qwerty mode in japanese...

 

To be clear:
Until Mountain Lion:

 

French language source= Azerty
Kotoeri Japanese language source= Qwerty

 

With Maverick:
French language source= Azerty
Kotoeri Japanese language source= The same language source as the previously used.

 

So, the question is: Why did you do that?
It's just a **** to use this! All the people using japanese language I know are naturelly using the Qwerty mode for Kotoeri, and some japanese characters are not included in the Azerty mode (such as "~").

Posted on Oct 23, 2013 3:08 AM

Close

Q: Did kotoeri changed with Maverick?

  • All replies
  • Helpful answers

first Previous Page 4 of 5 last Next
  • by Tom Gewecke,

    Tom Gewecke Tom Gewecke Nov 1, 2013 8:09 PM in response to Arnaud Nanta
    Level 9 (79,195 points)
    Nov 1, 2013 8:09 PM in response to Arnaud Nanta

    Arnaud Nanta wrote:

     

       I think that kind of solution would be too harsh for the common user.

     

     

    In practice it normally amounts to copy/pasting a command into Terminal.app, which I think a lot of users would be willing to do.  I'm not so optimistic about a rapid fix from Apple.

  • by FabienV,

    FabienV FabienV Nov 3, 2013 5:11 AM in response to phiw13.2
    Level 1 (5 points)
    Nov 3, 2013 5:11 AM in response to phiw13.2

    I suffer from the same troubles (French Keyboard switch to Kotoeri keeps the AZERTY layout) which is super annoying especially on a Japanese Mac. I really hope Apple considers this as a bug and not a "feature" as the support note wording is ambiguous. Even the preference panel is lying.

    For the moment, my only option is to insert an QUERTY keyboard in between.

    Capture d’écran 2013-11-03 à 13.53.07.png

  • by FabienV,Helpful

    FabienV FabienV Nov 3, 2013 9:31 AM in response to Seigneur_Folken
    Level 1 (5 points)
    Nov 3, 2013 9:31 AM in response to Seigneur_Folken

    Sorry for the double post but searching japanese users forum, I found a better workaround for this mapping problem. Google provides an alternate IME for Japanese here : http://www.google.co.jp/intl/ja/ime/

     

    After installing it, you need to go to the preferences and check "Always use Ja keyboard layout for Japanese Input" under the Advanced tab (else it will use Kotoeri as a base and runs into the same problem).

     

    I've yet to test it extensively but seems to do the trick. I'll appreciate any feedback.

  • by Arnaud Nanta,

    Arnaud Nanta Arnaud Nanta Nov 3, 2013 3:48 PM in response to FabienV
    Level 1 (0 points)
    Nov 3, 2013 3:48 PM in response to FabienV

       I just installed this Google IME.

     

       It seems to work pretty well. Thank you. And according to the video demonstration, the recognition seems to be pretty developed.

     

       By the way, there is the option to install and use Atok instead of Kotoeri too, but it is not free…

  • by Seigneur_Folken,

    Seigneur_Folken Seigneur_Folken Nov 16, 2013 9:19 AM in response to FabienV
    Level 1 (0 points)
    Nov 16, 2013 9:19 AM in response to FabienV

    It seems to work fine, I've just installed it, but already love it ^^.

     

    Thanks a lot for this very good advice.

  • by conscell,

    conscell conscell Nov 22, 2013 12:13 AM in response to Seigneur_Folken
    Level 1 (0 points)
    Nov 22, 2013 12:13 AM in response to Seigneur_Folken

    Same problem here when switching from French to Japanese.

    Sent them bugreport.

  • by Miharin,

    Miharin Miharin Nov 24, 2013 4:42 AM in response to Seigneur_Folken
    Level 1 (0 points)
    Nov 24, 2013 4:42 AM in response to Seigneur_Folken

    Apple has broken both Japanese and Chinese! I can no longer type either Japanese or Chinese punctuation marks. I use Finnish Extended, Hiragana and Pinyin input and it uses the Finnish keyboard layout for everything except letters.

  • by Tom Gewecke,

    Tom Gewecke Tom Gewecke Nov 24, 2013 4:58 AM in response to Miharin
    Level 9 (79,195 points)
    Nov 24, 2013 4:58 AM in response to Miharin

    Miharin wrote:

     

    Apple has broken both Japanese and Chinese!

     

    I think it is normal behavior for Chinese pinyin input to use the layout of the last Latin keyboard, at least for some time now.  At one point in the past it could only use US qwerty.  I would be curious what characters you cannot make.  Are you using a JIS keyboard for Chinese?

     

    Can you fix the problem by activating the US layout and switching to that before doing pinyin?

  • by Miharin,

    Miharin Miharin Nov 24, 2013 5:19 AM in response to Tom Gewecke
    Level 1 (0 points)
    Nov 24, 2013 5:19 AM in response to Tom Gewecke

    I can't type for example the character ~ (full width version) or any of the symbols that are supposed to be between P, L and enter because they just give me the Finnish letters öäå. I can't find some of the punctuation marks that are supposed to be there, I've tried every possible key combination already. Some can be found from different places than usual.

     

    Switching to US English first is a "fix" but pretty cumbersome if you ask me. It looks to me like an oversight and not a feature, but who knows what Apple was thinking with this. I will have to download both Google Pinyin and Japanese to go back to normal.

  • by Tom Gewecke,

    Tom Gewecke Tom Gewecke Nov 24, 2013 5:47 AM in response to Miharin
    Level 9 (79,195 points)
    Nov 24, 2013 5:47 AM in response to Miharin

    Miharin wrote:

     

    I can't type for example the character ~ (full width version) or any of the symbols that are supposed to be between P, L and enter because they just give me the Finnish letters öäå.

     

    What OS version did you have before Mavericks?  In 10.7 I always have to switch to US before pinyin to get those characters if I am using another layout, so it does not seem to have changed.

  • by Miharin,

    Miharin Miharin Nov 24, 2013 8:55 AM in response to Tom Gewecke
    Level 1 (0 points)
    Nov 24, 2013 8:55 AM in response to Tom Gewecke

    I used 10.8 but I cannot actually remember if I faced this certain issue with pinyin because I haven't used Chinese very much, unlike Japanese which worked fine before. But if what you say is true, then this issue has been here for a few years and now it's a new great "feature" that has been applied to Japanese as well, disabling non-US users from typing certain Japanese characters...

     

    So it fell to Google to fix this. I downloaded Google Japanese input and it works great.

  • by 77Shu77,

    77Shu77 77Shu77 Dec 3, 2013 6:22 PM in response to Seigneur_Folken
    Level 1 (0 points)
    Dec 3, 2013 6:22 PM in response to Seigneur_Folken

    +1 Broken still

  • by ethereality,

    ethereality ethereality Dec 3, 2013 8:42 PM in response to 77Shu77
    Level 1 (38 points)
    Notebooks
    Dec 3, 2013 8:42 PM in response to 77Shu77

    Tom answered this question, ~ third reply. I think OP should mark this thread as question answered.

  • by Tom Gewecke,

    Tom Gewecke Tom Gewecke Dec 17, 2013 10:35 AM in response to ethereality
    Level 9 (79,195 points)
    Dec 17, 2013 10:35 AM in response to ethereality

    10.9.1 has

     

    • Addresses an issue that may cause Japanese keyboards to retain a previously used language
  • by CamilloL,

    CamilloL CamilloL Dec 18, 2013 12:00 AM in response to Tom Gewecke
    Level 1 (0 points)
    Dec 18, 2013 12:00 AM in response to Tom Gewecke

    I can confirm that 10.9.1 fixes this issue.

first Previous Page 4 of 5 last Next