Typing L with stroke with us-intl-altgr

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








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.







share|improve this question
















  • 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






  • 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














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.







share|improve this question
















  • 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






  • 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












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.







share|improve this question












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.









share|improve this question











share|improve this question




share|improve this question










asked May 13 at 16:32









Federico Poloni

262111




262111







  • 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






  • 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




    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




    @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










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 => ł






share|improve this answer




















  • 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

















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 ł.






share|improve this answer




















  • 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










Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















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






























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 => ł






share|improve this answer




















  • 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














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 => ł






share|improve this answer




















  • 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












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 => ł






share|improve this answer












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 => ł







share|improve this answer












share|improve this answer



share|improve this answer










answered May 13 at 17:19









Gunnar Hjalmarsson

17.7k23059




17.7k23059











  • 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















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












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 ł.






share|improve this answer




















  • 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














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 ł.






share|improve this answer




















  • 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












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 ł.






share|improve this answer












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 ł.







share|improve this answer












share|improve this answer



share|improve this answer










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 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















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












 

draft saved


draft discarded


























 


draft saved


draft discarded














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













































































Popular posts from this blog

Which professions warranted travel in Medieval times?

How do so many people here on Academia.SE, and in general, afford lavish higher education programs?

Trouble downloading packages list due to a “Hash sum mismatch” error