Re: C-<char> doesn't respect current keyboard layout, OS X Carbon

[YAMAMOTO Mitsuharu]

>>>>> On Tue, 24 Apr 2007 10:29:38 +0200, Aidan Kehoe <address@hidden> said:

>> Can you replace `action=' at line 722 with `output=' and try again?

> There’s no action= at line 722--you’re talking about
> ExtendedIrishAidan.keylayout, available in the same directory.

Oops, sorry.  Yes, what I downloaded was ExtendedIrishAidan.keylayout.
I reached it by following a link in
http://www.parhasard.net/keyboard/, because I couldn't find
http://www.parhasard.net/keyboard/ExtendedAidan.layout.

Does the modified ExtendedIrishAidan.keylayout have the same problem?

> I don’t get any error messages in console.log when I log in with
> ExtendedAidan.keylayout .

Neither do I.  But I couldn't reproduce the problem with US keyboard.

>>>>> On Mon, 23 Apr 2007 21:24:10 +0200, Aidan Kehoe <address@hidden> said:

> Interestingly, it seems to be a difference between custom layouts
> and the layouts that shipped with the system. If I switch to the
> British or US layout, the problem goes away; that is, the control
> key behaves as expected, given the selected key layout.

All the shipped XML keylayouts are for Unicode keyboards (group="126"
and id="[some negative number]"), but ExtendedAidan.keylayout is for
Roman (group="0").  If the modified ExtendedIrishAidan.keylayout
doesn't have the same problem, then I'd suspect a bug in
UCKeyTranslate() with the combination of XML non-Unicode keylayout and
non-US keyboard.

                                     YAMAMOTO Mitsuharu
                                address@hidden