Version: unspecified (using KDE 4.5.1) OS: Linux First, I'd like to thank you for typographic characters! I've just found them and find them very useful. But there is one caveat. I use both Alt keys for special Polish characters like ą or ń. When I enabled typographic characters I could not use diacritic ones. There should be switch for typo characters. Even toggle option (special sequence for enabling them - type them - toggle and back to normal state). Could you repair it? Thanks for advance! Reproducible: Always OS: Linux (i686) release 2.6.35-999-generic Compiler: cc
If I got the report right the problem is key to symbol mapping, you'll have to file a bug against xkeyboard-config project on freedesktop.org Though you probably will need better description of the problem if you do. :)
So, typographic characters are treated like a keyboard layout? Actually I don't know how to fill in a good report for xkeyboard-config. :( Which other information should I mention?
One more thing. Couldn't it just use some modifier for typographic character like it is did for compose key? I figured out that typographic characters is just normal layout plus just these characters in second level (ALT key). So we should have had configurable modifier for this level or shift it to third or fourth level. I know you guys have skills to do that. :D
Hm, there's no feedback since my last posts. I really don't think changing modifier from ALT (now) to predefined ones (like Meta) is upstream issue. As I mentioned above there is option for compose key (my current replacement for typographic characters) to choose from various modifiers like left or right Meta. Wouldn't it possible to do the same with typographic characters instead using one trigger (ALT)?
Created attachment 51866 [details] simple mock up Typographic characters is an additional keyboard layout. There should be a trigger key to enable it.
(In reply to comment #4) > Hm, there's no feedback since my last posts. Well as far as I know keyboard-config maintainer does not have newborn kids (as i do) so you most probably will get faster answer from him :)
(In reply to comment #6) > Well as far as I know keyboard-config maintainer does not have newborn kids (as > i do) so you most probably will get faster answer from him :) Congratulation then :D but you did not refer to my mock up. I still don't know if my reasoning is correct. :)
^ Sorry Andriy but you have not replied me. :(
Well, here's the thing Wojciech — I am trying to close bugs that don't belong to KDE keyboard module so that I can concentrate on the ones I can help with or fix. We can keep this one open though something tells me that during those two months since this issue was reported it could have been solved by now at xkeyboard-config bug system. :) Maintainer of xkeyboard-config is quite a nice guy so there's no reason to avoid him :)
OK, thanks for your patience and understanding. I've filled this bug report there: https://bugs.freedesktop.org/show_bug.cgi?id=31623 so let's see how it'll go. :)
Looks like it's really a problem with xkeyboard-config (with no obvious resultion). Wojciech, shall we mark this one RESOLVED/UPSTREAM?
(In reply to comment #11) > Looks like it's really a problem with xkeyboard-config (with no obvious > resultion). Wojciech, shall we mark this one RESOLVED/UPSTREAM? Yeah, you definitely should in this case. :)
Thanks, marking as RESOLVED/UPSTREAM.