On Thu, 30 May 2013 07:59:11 -0300 José Romildo Malaquias <j.romi...@gmail.com>
said:

> On Mon, May 27, 2013 at 08:49:38AM +0900, Carsten Haitzler wrote:
> > On Sun, 26 May 2013 09:51:05 -0300 José Romildo Malaquias
> > <j.romi...@gmail.com> said:
> > 
> > > On Sun, May 26, 2013 at 01:53:49PM +0800, P Purkayastha wrote:
> > > > On 05/25/2013 10:31 AM, José Romildo Malaquias wrote:
> > > > > Hello.
> > > > >
> > > > > How can I set a notebook keyboard to US INTL (English with dead keys)
> > > > > with enlightenment-0.17.3 (on ~amd64 gentoo)?
> > > > >
> > > > > In the "Keyboard Settings" dialog I had a "us (default, basic)"
> > > > > configuration with the "Generic 105-key (intl) PC (pc105)" model, but
> > > > > dead keys are not working.
> > > > >
> > > > > Any clues?
> > > > >
> > > > > Romildo
> > > > 
> > > > Is that a variant of the "us (default)"? In that case, this keyboard 
> > > > setting has been broken for nearly a year. Variants don't work.
> > > 
> > > Yes, it is a variant of the "us (default)" layout.
> > > 
> > > For other desktop environments/window managers, I have the following in
> > > /etc/X11/xorg.conf.d/10-keyboard.conf:
> > > 
> > > 
> > >   Section "InputClass"
> > >           MatchIsKeyboard "on"
> > >           Identifier      "system-setup-keyboard"
> > >           Option          "XkbModel"      "pc105,abnt2,microsoftmult"
> > >           Option          "XkbLayout"     "us,br,br"
> > >           Option          "XkbVariant"    "intl,,"
> > >           Option          "XkbOptions"    
> > > "grp:shift_caps_toggle,grp_led:scroll"
> > >           #Option         "XkbOptions"    "terminate:ctrl_alt_bksp,"
> > >   EndSection
> > > 
> > > 
> > > Is there an entry in the bug tracker for this bug?
> > > 
> > > Is there any hope it is fixed soon?
> > 
> > i have used this for years - under options (in the kbd settings) under
> > "compose key position" i selected "caps lock" (since i find caps utterly
> > useless 99.9999% of the time and have better things for it to do).. so now
> > i can use it as a dead key. the kbds i do have are us qwerty (thus re-use
> > caps for this) or are jp or kr layouts, and with jp/kr choosing the right
> > layout works fine (the input mode modifier keys produces the right
> > keysym)... so as best i see - it's al there and works.
> 
> That is not exactly what I want.
> 
> I am looking for a way to get the same keyboard setup I have been using
> for years independently of the window manager used: us intl. It is the
> combination of "pc105" model, "us" layout, and "intl" variant. I do not
> want to use one compose key together with two more keys every time I
> need an accented letter. With the us intl keyboard, the accents are dead
> keys themselves. To get an "á" for instance, I just type "'" followed by
> "a". The language I most use is Portuguese, which uses accented letters
> a lot. Typing them with an individual compose key may be much less
> productive than with the us intl configuration.
> 
> This us intl setup used to just work with enlightenment, but now it does
> not work anymore. It would be nice if someone could take a look at it
> and maybe fix it.

i have no kbds with such dead keys... so i know i'm not able to test... i know
the variant/option is there (us intl)... and i am pretty sure it passes it of
to xkb's config tool... last i checked.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ras...@rasterman.com


------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to