Re: Input Method Always Supersede Keyboard Layouts
Re: Input Method Always Supersede Keyboard Layouts
- Subject: Re: Input Method Always Supersede Keyboard Layouts
- From: Eric Schlegel <email@hidden>
- Date: Sun, 4 Nov 2007 21:54:22 -0800
On Nov 4, 2007, at 12:16 PM, Maurice Volaski wrote:
At one point, I wrote
3528513 : Input Method Always Supersede Keyboard Layouts
Input methods are treated by the OS as being equivalent to a
keyboard
layout. That is, you can either choose a keyboard layout OR an
input method.
There is no way to have an input method act on the roman script
system and
permit the user to still be able to choose one of its keyboard
layouts.
And you wrote:
According to comments in the bug, this requires new API to work
properly, and the API will be introduced in Leopard.
I was just wondering what API this is. So far as I can tell, it
works at
least by default the same way. Also, this bug was marked as a
duplicate of
3595597, but there's no way for me to see its status.
From 3595597 (which is fixed in Leopard), it looks like the API
(available in Leopard) are:
TISSetInputMethodKeyboardLayoutOverride()
TISCopyInputMethodKeyboardLayoutOverride()
Some other comments from the bug:
This has been resolved, but for any given input method, what the
originator wants depends on the input method using new API in
Leopard. An input method needs to provide its own UI to let the
user choose a Unicode keyboard layout to be used in conjunction with
it.
So this isn't a built-in feature that you, as an end-user, can apply
to any input method; the input method needs to explicitly support it.
-eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Accessibility-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden