Typing L with stroke with us-intl-altgr
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgO9GURib1T8z7lCwjOGLQaGtrueEthgQ8LO42ZX8cOfTqDK4jvDDpKkLFwf2J49kYCMNW7d4ABih_XCb_2UXdq5fPJDkoyg7-8g_YfRUot-XnaXkNYycsNp7lA5_TW9td0FFpLQ2APzKcZ/s1600/1.jpg)
![Creative The name of the picture](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYQ0N5W1qAOxLP7t7iOM6O6AzbZnkXUy16s7P_CWfOb5UbTQY_aDsc727chyphenhyphen5W4IppVNernMMQeaUFTB_rFzAd95_CDt-tnwN-nBx6JyUp2duGjPaL5-VgNO41AVsA_vu30EJcipdDG409/s400/Clash+Royale+CLAN+TAG%2523URR8PPP.png)
up vote
0
down vote
favorite
How do I type an L with stroke or Ã
Â, which appears notably in Polish, when using the us-intl-altgr
keyboard mapping for X? More generally, is there a way to find out systematically how I can produce a certain symbol with a given keymap?
I have searched online and found several illustrations of this layout, but none seems to include this symbol.
keyboard-layout internationalization
add a comment |Â
up vote
0
down vote
favorite
How do I type an L with stroke or Ã
Â, which appears notably in Polish, when using the us-intl-altgr
keyboard mapping for X? More generally, is there a way to find out systematically how I can produce a certain symbol with a given keymap?
I have searched online and found several illustrations of this layout, but none seems to include this symbol.
keyboard-layout internationalization
3
Btw: the keyboard layout can be seen withgkbd-keyboard-display -l "us(altgr-intl)"
. There's noà Â
shown, though. :-( I'd suggest to pressCTRL-SHIFT-u
so an underlinedu
appears to indicate Unicode. Then let go of the keys and type0141
(forà Â
) or0142
(forà Â
).
â PerlDuck
May 13 at 17:15
1
@PerlDuck That interface does not display all the symbols that can be entered, though, For instance, using deadkeys I can type another Polish character, ÃÂ (AltGr+8 then e), but it's not shown by gkbd-keyboard-display. Actually, it seems to me that it shows certain characters at...
, and it does not highlight deadkeys at all.
â Federico Poloni
May 13 at 21:50
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How do I type an L with stroke or Ã
Â, which appears notably in Polish, when using the us-intl-altgr
keyboard mapping for X? More generally, is there a way to find out systematically how I can produce a certain symbol with a given keymap?
I have searched online and found several illustrations of this layout, but none seems to include this symbol.
keyboard-layout internationalization
How do I type an L with stroke or Ã
Â, which appears notably in Polish, when using the us-intl-altgr
keyboard mapping for X? More generally, is there a way to find out systematically how I can produce a certain symbol with a given keymap?
I have searched online and found several illustrations of this layout, but none seems to include this symbol.
keyboard-layout internationalization
asked May 13 at 16:32
Federico Poloni
262111
262111
3
Btw: the keyboard layout can be seen withgkbd-keyboard-display -l "us(altgr-intl)"
. There's noà Â
shown, though. :-( I'd suggest to pressCTRL-SHIFT-u
so an underlinedu
appears to indicate Unicode. Then let go of the keys and type0141
(forà Â
) or0142
(forà Â
).
â PerlDuck
May 13 at 17:15
1
@PerlDuck That interface does not display all the symbols that can be entered, though, For instance, using deadkeys I can type another Polish character, ÃÂ (AltGr+8 then e), but it's not shown by gkbd-keyboard-display. Actually, it seems to me that it shows certain characters at...
, and it does not highlight deadkeys at all.
â Federico Poloni
May 13 at 21:50
add a comment |Â
3
Btw: the keyboard layout can be seen withgkbd-keyboard-display -l "us(altgr-intl)"
. There's noà Â
shown, though. :-( I'd suggest to pressCTRL-SHIFT-u
so an underlinedu
appears to indicate Unicode. Then let go of the keys and type0141
(forà Â
) or0142
(forà Â
).
â PerlDuck
May 13 at 17:15
1
@PerlDuck That interface does not display all the symbols that can be entered, though, For instance, using deadkeys I can type another Polish character, ÃÂ (AltGr+8 then e), but it's not shown by gkbd-keyboard-display. Actually, it seems to me that it shows certain characters at...
, and it does not highlight deadkeys at all.
â Federico Poloni
May 13 at 21:50
3
3
Btw: the keyboard layout can be seen with
gkbd-keyboard-display -l "us(altgr-intl)"
. There's no Ã
Â
shown, though. :-( I'd suggest to press CTRL-SHIFT-u
so an underlined u
appears to indicate Unicode. Then let go of the keys and type 0141
(for Ã
Â
) or 0142
(for Ã
Â
).â PerlDuck
May 13 at 17:15
Btw: the keyboard layout can be seen with
gkbd-keyboard-display -l "us(altgr-intl)"
. There's no Ã
Â
shown, though. :-( I'd suggest to press CTRL-SHIFT-u
so an underlined u
appears to indicate Unicode. Then let go of the keys and type 0141
(for Ã
Â
) or 0142
(for Ã
Â
).â PerlDuck
May 13 at 17:15
1
1
@PerlDuck That interface does not display all the symbols that can be entered, though, For instance, using deadkeys I can type another Polish character, ÃÂ (AltGr+8 then e), but it's not shown by gkbd-keyboard-display. Actually, it seems to me that it shows certain characters at
...
, and it does not highlight deadkeys at all.â Federico Poloni
May 13 at 21:50
@PerlDuck That interface does not display all the symbols that can be entered, though, For instance, using deadkeys I can type another Polish character, ÃÂ (AltGr+8 then e), but it's not shown by gkbd-keyboard-display. Actually, it seems to me that it shows certain characters at
...
, and it does not highlight deadkeys at all.â Federico Poloni
May 13 at 21:50
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
2
down vote
A generic method to type a character, which is not present with the keyboard layout you are using, is to type it using its code points.
So for the example you mentioned:
Ctrl+Shift+U followed by 0142 followed by Enter => Ã Â
Thanks! But is there a way to know which characters are present in the keyboard layout? Something likedumpkeys
for the tty console.
â Federico Poloni
May 13 at 21:53
add a comment |Â
up vote
2
down vote
accepted
Answering my own question after some research.
A list of defined keys is in /usr/share/X11/xkb/symbols/us
. The character Ã
 appears there as lstroke
, and it is unfortunately not defined in the altgr-intl
section, unfortunately (but only in colemak
).
A different way to obtain it would be with the dead key dead_stroke
followed by l
. Unfortunately, the key dead_stroke
isn't defined in altgr-intl
either (but only in mac
). So the answer is that there is no way to enter that symbol with the "vanilla" altgr-intl
apart from the cumbersome method described in @GunnarHjalmarsson's answer, which allows to enter a generic Unicode codepoint: Ctrl+Shift+U, 0142, Enter.
There is a different solution, though: defining a Compose key. Using gnome-tweaks
, one can set up a modifier key (for instance, right-alt, or caps lock) to act as a compose key. Then, pressing compose, /, l produces Ã
Â.
Right, a compose key is one way, but you probably don't want to define <Right Alt> as the compose key when using theus+altgr-intl
layout, since that would make all the 3:rd and 4:th level symbols unavailable (unless you also define anotherlv3:
option).
â Gunnar Hjalmarsson
May 13 at 22:45
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
A generic method to type a character, which is not present with the keyboard layout you are using, is to type it using its code points.
So for the example you mentioned:
Ctrl+Shift+U followed by 0142 followed by Enter => Ã Â
Thanks! But is there a way to know which characters are present in the keyboard layout? Something likedumpkeys
for the tty console.
â Federico Poloni
May 13 at 21:53
add a comment |Â
up vote
2
down vote
A generic method to type a character, which is not present with the keyboard layout you are using, is to type it using its code points.
So for the example you mentioned:
Ctrl+Shift+U followed by 0142 followed by Enter => Ã Â
Thanks! But is there a way to know which characters are present in the keyboard layout? Something likedumpkeys
for the tty console.
â Federico Poloni
May 13 at 21:53
add a comment |Â
up vote
2
down vote
up vote
2
down vote
A generic method to type a character, which is not present with the keyboard layout you are using, is to type it using its code points.
So for the example you mentioned:
Ctrl+Shift+U followed by 0142 followed by Enter => Ã Â
A generic method to type a character, which is not present with the keyboard layout you are using, is to type it using its code points.
So for the example you mentioned:
Ctrl+Shift+U followed by 0142 followed by Enter => Ã Â
answered May 13 at 17:19
![](https://i.stack.imgur.com/aZsF6.jpg?s=32&g=1)
![](https://i.stack.imgur.com/aZsF6.jpg?s=32&g=1)
Gunnar Hjalmarsson
17.7k23059
17.7k23059
Thanks! But is there a way to know which characters are present in the keyboard layout? Something likedumpkeys
for the tty console.
â Federico Poloni
May 13 at 21:53
add a comment |Â
Thanks! But is there a way to know which characters are present in the keyboard layout? Something likedumpkeys
for the tty console.
â Federico Poloni
May 13 at 21:53
Thanks! But is there a way to know which characters are present in the keyboard layout? Something like
dumpkeys
for the tty console.â Federico Poloni
May 13 at 21:53
Thanks! But is there a way to know which characters are present in the keyboard layout? Something like
dumpkeys
for the tty console.â Federico Poloni
May 13 at 21:53
add a comment |Â
up vote
2
down vote
accepted
Answering my own question after some research.
A list of defined keys is in /usr/share/X11/xkb/symbols/us
. The character Ã
 appears there as lstroke
, and it is unfortunately not defined in the altgr-intl
section, unfortunately (but only in colemak
).
A different way to obtain it would be with the dead key dead_stroke
followed by l
. Unfortunately, the key dead_stroke
isn't defined in altgr-intl
either (but only in mac
). So the answer is that there is no way to enter that symbol with the "vanilla" altgr-intl
apart from the cumbersome method described in @GunnarHjalmarsson's answer, which allows to enter a generic Unicode codepoint: Ctrl+Shift+U, 0142, Enter.
There is a different solution, though: defining a Compose key. Using gnome-tweaks
, one can set up a modifier key (for instance, right-alt, or caps lock) to act as a compose key. Then, pressing compose, /, l produces Ã
Â.
Right, a compose key is one way, but you probably don't want to define <Right Alt> as the compose key when using theus+altgr-intl
layout, since that would make all the 3:rd and 4:th level symbols unavailable (unless you also define anotherlv3:
option).
â Gunnar Hjalmarsson
May 13 at 22:45
add a comment |Â
up vote
2
down vote
accepted
Answering my own question after some research.
A list of defined keys is in /usr/share/X11/xkb/symbols/us
. The character Ã
 appears there as lstroke
, and it is unfortunately not defined in the altgr-intl
section, unfortunately (but only in colemak
).
A different way to obtain it would be with the dead key dead_stroke
followed by l
. Unfortunately, the key dead_stroke
isn't defined in altgr-intl
either (but only in mac
). So the answer is that there is no way to enter that symbol with the "vanilla" altgr-intl
apart from the cumbersome method described in @GunnarHjalmarsson's answer, which allows to enter a generic Unicode codepoint: Ctrl+Shift+U, 0142, Enter.
There is a different solution, though: defining a Compose key. Using gnome-tweaks
, one can set up a modifier key (for instance, right-alt, or caps lock) to act as a compose key. Then, pressing compose, /, l produces Ã
Â.
Right, a compose key is one way, but you probably don't want to define <Right Alt> as the compose key when using theus+altgr-intl
layout, since that would make all the 3:rd and 4:th level symbols unavailable (unless you also define anotherlv3:
option).
â Gunnar Hjalmarsson
May 13 at 22:45
add a comment |Â
up vote
2
down vote
accepted
up vote
2
down vote
accepted
Answering my own question after some research.
A list of defined keys is in /usr/share/X11/xkb/symbols/us
. The character Ã
 appears there as lstroke
, and it is unfortunately not defined in the altgr-intl
section, unfortunately (but only in colemak
).
A different way to obtain it would be with the dead key dead_stroke
followed by l
. Unfortunately, the key dead_stroke
isn't defined in altgr-intl
either (but only in mac
). So the answer is that there is no way to enter that symbol with the "vanilla" altgr-intl
apart from the cumbersome method described in @GunnarHjalmarsson's answer, which allows to enter a generic Unicode codepoint: Ctrl+Shift+U, 0142, Enter.
There is a different solution, though: defining a Compose key. Using gnome-tweaks
, one can set up a modifier key (for instance, right-alt, or caps lock) to act as a compose key. Then, pressing compose, /, l produces Ã
Â.
Answering my own question after some research.
A list of defined keys is in /usr/share/X11/xkb/symbols/us
. The character Ã
 appears there as lstroke
, and it is unfortunately not defined in the altgr-intl
section, unfortunately (but only in colemak
).
A different way to obtain it would be with the dead key dead_stroke
followed by l
. Unfortunately, the key dead_stroke
isn't defined in altgr-intl
either (but only in mac
). So the answer is that there is no way to enter that symbol with the "vanilla" altgr-intl
apart from the cumbersome method described in @GunnarHjalmarsson's answer, which allows to enter a generic Unicode codepoint: Ctrl+Shift+U, 0142, Enter.
There is a different solution, though: defining a Compose key. Using gnome-tweaks
, one can set up a modifier key (for instance, right-alt, or caps lock) to act as a compose key. Then, pressing compose, /, l produces Ã
Â.
answered May 13 at 22:21
Federico Poloni
262111
262111
Right, a compose key is one way, but you probably don't want to define <Right Alt> as the compose key when using theus+altgr-intl
layout, since that would make all the 3:rd and 4:th level symbols unavailable (unless you also define anotherlv3:
option).
â Gunnar Hjalmarsson
May 13 at 22:45
add a comment |Â
Right, a compose key is one way, but you probably don't want to define <Right Alt> as the compose key when using theus+altgr-intl
layout, since that would make all the 3:rd and 4:th level symbols unavailable (unless you also define anotherlv3:
option).
â Gunnar Hjalmarsson
May 13 at 22:45
Right, a compose key is one way, but you probably don't want to define <Right Alt> as the compose key when using the
us+altgr-intl
layout, since that would make all the 3:rd and 4:th level symbols unavailable (unless you also define another lv3:
option).â Gunnar Hjalmarsson
May 13 at 22:45
Right, a compose key is one way, but you probably don't want to define <Right Alt> as the compose key when using the
us+altgr-intl
layout, since that would make all the 3:rd and 4:th level symbols unavailable (unless you also define another lv3:
option).â Gunnar Hjalmarsson
May 13 at 22:45
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%2f1035761%2ftyping-l-with-stroke-with-us-intl-altgr%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
3
Btw: the keyboard layout can be seen with
gkbd-keyboard-display -l "us(altgr-intl)"
. There's noà Â
shown, though. :-( I'd suggest to pressCTRL-SHIFT-u
so an underlinedu
appears to indicate Unicode. Then let go of the keys and type0141
(forà Â
) or0142
(forà Â
).â PerlDuck
May 13 at 17:15
1
@PerlDuck That interface does not display all the symbols that can be entered, though, For instance, using deadkeys I can type another Polish character, ÃÂ (AltGr+8 then e), but it's not shown by gkbd-keyboard-display. Actually, it seems to me that it shows certain characters at
...
, and it does not highlight deadkeys at all.â Federico Poloni
May 13 at 21:50