Comment 12 for bug 1691115

I'll have a look at keysym_rule(s) and see if I can use them.

Meanwhile, I think we can use the existing layout.

2017-05-18 10:48 GMT+02:00 marmuta <email address hidden>:

> >>There not going to be removed, though.
> s/There/They're/
> >if this approach is deprecated, probably we'd better use the
> >suggested, current approach. Which is what?
> I had dynamic generation of labels in mind when I wrote that. That's what
> is already happening for most keycode keys across all of Onboard's layouts.
> Whenever the Xkb keymap changes, the labels change and that is what I think
> should happen for input methods too. I mentioned getting them from
> libhangul before.
>
> However, what I should have remembered are keysym rules (tag
> "keysym_rule"). These rules can replace arbitrary attributes, including the
> label, wherever the given keysym would be generated. Keysyms are one step
> up in the translation from keycodes ("keycode" key) to printable characters
> ("char" key) and that translation has all modifiers already applied, no
> need to explicitly target individual modifiers with shift_label, etc.
> The existing keysym_rules in key_defs.xml switch labels of the number pads
> when NumLock is active - without having to specify the NumLock modifier.
>
> Actually, in your case, a keysym rule should work for the Won symbol
> ("₩") too. That would take the shift modifier into account. You should
> be able to find the keysym to target by typing into xev.
>
> The currency keys in trunk have to stay "char", because they are not
> part of the system keymap and have no keycode to translate from.
>
> However, as I wrote before, we're not going to remove the
> <modifier>_label attributes.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1691115
>
> Title:
> Hangul (Korean) support
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/onboard/+bug/1691115/+subscriptions
>

--
--
Alessandro Bottoni