On Sun, 21 Oct 2001 17:32:43 -0200, [EMAIL PROTECTED] writes:
> If the application is using only XLookupString to get keyboard input, then
>it will not get properly composed characters (unless there is some hack in
>Xlib). Implementing support for 8 bit input characters is easy, and normally
>can be done with a simple wrap for XLookupString, with some initialization,
>and then calling XmbLookupString.
i'm not talking about composed characters: on german keyboards
the right alt key, labelled 'alt_gr', acts as an extra modifier mod3,
which adds some extra bindings (eg. q -> @, + -> ~,...).
furthermore my problems are not 8bit related, @ for sure is within
ascii.
i thought that processing the keypress event filtering out unwanted
stuff and then asking XLookupString for a potential string was
the right way to do it...at least some packages out there do
it that way (for example gtk).
regards
az
--
+ Alexander Zangerl + [EMAIL PROTECTED] + DSA 42BD645D + (RSA 5B586291)
Backup not found: A)bort, R)etry, M)assive heart failure?
signature.ng
