All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Problem with i18n (input)
Date: Mon, 30 Jun 2008 17:02:25 -0300	[thread overview]
Message-ID: <87zlp2elny.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <1214853946.21138.8.camel@lenovo.internal.reciva.com> (Phil Blundell's message of "Mon\, 30 Jun 2008 20\:25\:46 +0100")

Phil Blundell <pb@reciva.com> writes:

> On Mon, 2008-06-30 at 15:36 -0300, Otavio Salvador wrote:
>> I've been in trouble to get proper support for input in OE. We're
>> having problem to support input of international charsets on X. We've
>> include locale packages and we have the system properly translated,
>> however the input of latin1 chars (e.g. éçóã...) doesn't work.
>
> Can you be any more specific about what exactly goes wrong?  Are you
> basically saying that the compose key doesn't work, or are you talking
> about something different?  If compose, does it not work at all (i.e.
> just enters "e'" as separate keystrokes, as if you hadn't pressed
> compose in the first place) or does it swallow the two keystrokes and
> then give you nothing, or garbage, out?  If the former, have you
> verified (e.g. with xev) that the compose key itself is correctly mapped
> and generating events with the right keysym?

When I press "'e" it gives me nothing. When I run it inside xev it
gives me:

KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x3a, subw 0x0, time 3675299458, (149,171), root:(572,473),
    state 0x0, keycode 34 (keysym 0xfe51, dead_acute), same_screen YES,
    XLookupString gives 1 bytes: (b4) "�"
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x3a, subw 0x0, time 3675299519, (149,171), root:(572,473),
    state 0x0, keycode 34 (keysym 0xfe51, dead_acute), same_screen YES,
    XLookupString gives 1 bytes: (b4) "�"
    XFilterEvent returns: False

KeyPress event, serial 30, synthetic NO, window 0x1400001,
    root 0x3a, subw 0x0, time 3675302404, (149,171), root:(572,473),
    state 0x0, keycode 26 (keysym 0x65, e), same_screen YES,
    XLookupString gives 1 bytes: (65) "e"
    XFilterEvent returns: False

KeyRelease event, serial 30, synthetic NO, window 0x1400001,
    root 0x3a, subw 0x0, time 3675302404, (149,171), root:(572,473),
    state 0x0, keycode 26 (keysym 0x65, e), same_screen YES,
    XLookupString gives 1 bytes: (65) "e"
    XFilterEvent returns: False

> Also, what applications are you trying to input these characters into?
> This is an area that is not terribly well standardised in X and
> different toolkits have different behaviour.

We used xfce4-terminal for testing. It uses GTK and works fine in my
Debian system but fails in OE.

> Also also, what build of libx11 do you have?  Is it a "diet" version or
> the full thing?

I'm using the full thing:

libx11-6_1:1.1.3-r3_i586.ipk
libx11-locale_1:1.1.3-r3_i586.ipk

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
 you the whole house."



  reply	other threads:[~2008-06-30 20:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-30 18:36 Problem with i18n (input) Otavio Salvador
2008-06-30 19:25 ` Phil Blundell
2008-06-30 20:02   ` Otavio Salvador [this message]
2008-06-30 20:46     ` Phil Blundell
2008-06-30 20:54       ` Otavio Salvador
2008-06-30 21:26         ` Phil Blundell
2008-06-30 21:42           ` Otavio Salvador
2008-06-30 21:50             ` Phil Blundell
2008-07-01 18:19               ` Otavio Salvador
2008-07-01 18:38                 ` Phil Blundell
2008-07-01 19:06                   ` Otavio Salvador
2008-07-02  0:33                     ` Otavio Salvador
2008-07-02 11:01                       ` Stefano Regno

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zlp2elny.fsf@neumann.lab.ossystems.com.br \
    --to=otavio@debian.org \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.