Compose sequences with multicharacter result don't work
Clash Royale CLAN TAG#URR8PPP up vote
0
down vote
favorite
I'm using Ubuntu 16.04 LTS.
I set compose key on CapsLock.
It seems some specific compose key combinations don't work at all. For example, typing Compose+'+j does totally nothing. This combination should be easy to reproduce on most keyboards, corresponding string from the Compose file:
<Multi_key> <apostrophe> <j> : "jÃŒÂ" # LATIN SMALL LETTER J U006A with COMBINING ACUTE ACCENT U0301
Note that this combination results in two characters, unlike most other combinations which seem to work fine. I'm not sure whether it's X bug or Unity bug.
unity keyboard shortcut-keys keyboard-layout compose-key
asked Feb 13 at 9:59
Ivan G.
385
add a comment |Â
up vote
0
down vote
favorite
I'm using Ubuntu 16.04 LTS.
I set compose key on CapsLock.
It seems some specific compose key combinations don't work at all. For example, typing Compose+'+j does totally nothing. This combination should be easy to reproduce on most keyboards, corresponding string from the Compose file:
<Multi_key> <apostrophe> <j> : "jÃŒÂ" # LATIN SMALL LETTER J U006A with COMBINING ACUTE ACCENT U0301
Note that this combination results in two characters, unlike most other combinations which seem to work fine. I'm not sure whether it's X bug or Unity bug.
unity keyboard shortcut-keys keyboard-layout compose-key
asked Feb 13 at 9:59
Ivan G.
385
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm using Ubuntu 16.04 LTS.
I set compose key on CapsLock.
It seems some specific compose key combinations don't work at all. For example, typing Compose+'+j does totally nothing. This combination should be easy to reproduce on most keyboards, corresponding string from the Compose file:
<Multi_key> <apostrophe> <j> : "jÃŒÂ" # LATIN SMALL LETTER J U006A with COMBINING ACUTE ACCENT U0301
Note that this combination results in two characters, unlike most other combinations which seem to work fine. I'm not sure whether it's X bug or Unity bug.
unity keyboard shortcut-keys keyboard-layout compose-key
asked Feb 13 at 9:59
Ivan G.
385
I'm using Ubuntu 16.04 LTS.
I set compose key on CapsLock.
It seems some specific compose key combinations don't work at all. For example, typing Compose+'+j does totally nothing. This combination should be easy to reproduce on most keyboards, corresponding string from the Compose file:
<Multi_key> <apostrophe> <j> : "jÃŒÂ" # LATIN SMALL LETTER J U006A with COMBINING ACUTE ACCENT U0301
Note that this combination results in two characters, unlike most other combinations which seem to work fine. I'm not sure whether it's X bug or Unity bug.
unity keyboard shortcut-keys keyboard-layout compose-key
unity keyboard shortcut-keys keyboard-layout compose-key
asked Feb 13 at 9:59
Ivan G.
385
asked Feb 13 at 9:59
Ivan G.
385
asked Feb 13 at 9:59
Ivan G.
385
asked Feb 13 at 9:59
Ivan G.
385
asked Feb 13 at 9:59
Ivan G.
385
385
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
To access all the characters in en_US.UTF-8/Compose, you need to enable XIM as input method (can be done from System Settings -> Language Support) and relogin (or possibly reboot).
Please note that XIM does not work on Wayland - can't tell if it's a bug or intentionally - so for Ubuntu 17.10 you need to log in to an "Ubuntu on Xorg" session.
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
1
a potentially unwanted side effect of enabling XIM in GTK apps is that it disables thectrl+shift+umethod for entering an arbitrary unicode point (link).
– quixotic
Feb 13 at 16:15
Thanks, but it seems that using XIM also creates more problems. Likewise, it seems impossible to use CJK IME anymore.
– Ivan G.
Feb 16 at 14:21
@IvanG.: Indeed you need to have e.g. IBus or Fcitx enabled for CJK input methods, and that precludes the use of XIM concurrently.
– Gunnar Hjalmarsson
Feb 16 at 20:34
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
To access all the characters in en_US.UTF-8/Compose, you need to enable XIM as input method (can be done from System Settings -> Language Support) and relogin (or possibly reboot).
Please note that XIM does not work on Wayland - can't tell if it's a bug or intentionally - so for Ubuntu 17.10 you need to log in to an "Ubuntu on Xorg" session.
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
1
a potentially unwanted side effect of enabling XIM in GTK apps is that it disables thectrl+shift+umethod for entering an arbitrary unicode point (link).
– quixotic
Feb 13 at 16:15
Thanks, but it seems that using XIM also creates more problems. Likewise, it seems impossible to use CJK IME anymore.
– Ivan G.
Feb 16 at 14:21
@IvanG.: Indeed you need to have e.g. IBus or Fcitx enabled for CJK input methods, and that precludes the use of XIM concurrently.
– Gunnar Hjalmarsson
Feb 16 at 20:34
add a comment |Â
up vote
0
down vote
To access all the characters in en_US.UTF-8/Compose, you need to enable XIM as input method (can be done from System Settings -> Language Support) and relogin (or possibly reboot).
Please note that XIM does not work on Wayland - can't tell if it's a bug or intentionally - so for Ubuntu 17.10 you need to log in to an "Ubuntu on Xorg" session.
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
1
a potentially unwanted side effect of enabling XIM in GTK apps is that it disables thectrl+shift+umethod for entering an arbitrary unicode point (link).
– quixotic
Feb 13 at 16:15
Thanks, but it seems that using XIM also creates more problems. Likewise, it seems impossible to use CJK IME anymore.
– Ivan G.
Feb 16 at 14:21
@IvanG.: Indeed you need to have e.g. IBus or Fcitx enabled for CJK input methods, and that precludes the use of XIM concurrently.
– Gunnar Hjalmarsson
Feb 16 at 20:34
add a comment |Â
up vote
0
down vote
up vote
0
down vote
To access all the characters in en_US.UTF-8/Compose, you need to enable XIM as input method (can be done from System Settings -> Language Support) and relogin (or possibly reboot).
Please note that XIM does not work on Wayland - can't tell if it's a bug or intentionally - so for Ubuntu 17.10 you need to log in to an "Ubuntu on Xorg" session.
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
To access all the characters in en_US.UTF-8/Compose, you need to enable XIM as input method (can be done from System Settings -> Language Support) and relogin (or possibly reboot).
Please note that XIM does not work on Wayland - can't tell if it's a bug or intentionally - so for Ubuntu 17.10 you need to log in to an "Ubuntu on Xorg" session.
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
answered Feb 13 at 14:49
Gunnar Hjalmarsson
18.1k23060
18.1k23060
1
a potentially unwanted side effect of enabling XIM in GTK apps is that it disables thectrl+shift+umethod for entering an arbitrary unicode point (link).
– quixotic
Feb 13 at 16:15
Thanks, but it seems that using XIM also creates more problems. Likewise, it seems impossible to use CJK IME anymore.
– Ivan G.
Feb 16 at 14:21
@IvanG.: Indeed you need to have e.g. IBus or Fcitx enabled for CJK input methods, and that precludes the use of XIM concurrently.
– Gunnar Hjalmarsson
Feb 16 at 20:34
add a comment |Â
1
a potentially unwanted side effect of enabling XIM in GTK apps is that it disables thectrl+shift+umethod for entering an arbitrary unicode point (link).
– quixotic
Feb 13 at 16:15
Thanks, but it seems that using XIM also creates more problems. Likewise, it seems impossible to use CJK IME anymore.
– Ivan G.
Feb 16 at 14:21
@IvanG.: Indeed you need to have e.g. IBus or Fcitx enabled for CJK input methods, and that precludes the use of XIM concurrently.
– Gunnar Hjalmarsson
Feb 16 at 20:34
1
1
a potentially unwanted side effect of enabling XIM in GTK apps is that it disables the
ctrl+shift+u method for entering an arbitrary unicode point (link).– quixotic
Feb 13 at 16:15
a potentially unwanted side effect of enabling XIM in GTK apps is that it disables the
ctrl+shift+u method for entering an arbitrary unicode point (link).– quixotic
Feb 13 at 16:15
Thanks, but it seems that using XIM also creates more problems. Likewise, it seems impossible to use CJK IME anymore.
– Ivan G.
Feb 16 at 14:21
Thanks, but it seems that using XIM also creates more problems. Likewise, it seems impossible to use CJK IME anymore.
– Ivan G.
Feb 16 at 14:21
@IvanG.: Indeed you need to have e.g. IBus or Fcitx enabled for CJK input methods, and that precludes the use of XIM concurrently.
– Gunnar Hjalmarsson
Feb 16 at 20:34
@IvanG.: Indeed you need to have e.g. IBus or Fcitx enabled for CJK input methods, and that precludes the use of XIM concurrently.
– Gunnar Hjalmarsson
Feb 16 at 20:34
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1005754%2fcompose-sequences-with-multicharacter-result-dont-work%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e)
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom))
StackExchange.using('gps', function() StackExchange.gps.track('embedded_signup_form.view', location: 'question_page' ); );
$window.unbind('scroll', onScroll);
;
$window.on('scroll', onScroll);
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password