xrvt-unicode doesn't display unicode charactersHow to get Ubuntu to display unicode supplementary characters?display all unicode charactersubuntu cannot display all the unicodeHow to make Autokey type Unicode characters?How to make xdotool type Unicode charactersxterm cannot display unicodeHow do I resolve missing characters in my unicode font?Unicode characters are displayed wrong in bashTerminal - how to display 'shades' unicode characters properly?Unicode characters missing
Is it unprofessional to ask if a job posting on GlassDoor is real?
Why did the Germans forbid the possession of pet pigeons in Rostov-on-Don in 1941?
How can I make my BBEG immortal short of making them a Lich or Vampire?
Python: next in for loop
What does "Puller Prush Person" mean?
To string or not to string
Languages that we cannot (dis)prove to be Context-Free
Modeling an IPv4 Address
Why doesn't Newton's third law mean a person bounces back to where they started when they hit the ground?
Do I have a twin with permutated remainders?
How is the claim "I am in New York only if I am in America" the same as "If I am in New York, then I am in America?
Problem of parity - Can we draw a closed path made up of 20 line segments...
What defenses are there against being summoned by the Gate spell?
What are these boxed doors outside store fronts in New York?
What typically incentivizes a professor to change jobs to a lower ranking university?
Why Is Death Allowed In the Matrix?
Why are 150k or 200k jobs considered good when there are 300k+ births a month?
Can I ask the recruiters in my resume to put the reason why I am rejected?
What would happen to a modern skyscraper if it rains micro blackholes?
Why are electrically insulating heatsinks so rare? Is it just cost?
How could an uplifted falcon's brain work?
Theorems that impeded progress
Is it legal for company to use my work email to pretend I still work there?
Today is the Center
xrvt-unicode doesn't display unicode characters
How to get Ubuntu to display unicode supplementary characters?display all unicode charactersubuntu cannot display all the unicodeHow to make Autokey type Unicode characters?How to make xdotool type Unicode charactersxterm cannot display unicodeHow do I resolve missing characters in my unicode font?Unicode characters are displayed wrong in bashTerminal - how to display 'shades' unicode characters properly?Unicode characters missing
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
I do not understand why rxvt-unicode doesn't display some Unicode characters correctly such as ☁ or ☂ while ⚡ is displayed correctly. These symbols are replaced by a little box as you can see in the screenshot:
Here's my locale:
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
And here my .Xresources:
URxvt.font: xft:Ubuntu Mono:size=11:antialias=true:hinting=true
URxvt.letterSpace: -2
URxvt.lineSpace: -2
URxvt.scrollKey: true
URxvt.depth: 32
URxvt.loginShell: true
URxvt.geometry: 100x30
URxvt.saveLines: 10000
URxvt.cutchars: "`"'&()*,:;<=>?[\]^$"
URxvt.scrollBar: false
URxvt.visualBell: true ```
These symbols are displayed correctly in gnome-terminal.
Suggestions from google are not ubuntu-related and they all suggest to add .utf-8 to locale, which I already have in my settings. If you can help me in any way it would be awesome, this problem is really bugging me!
unicode rxvt
edited 19 mins ago
Kevin Bowen
14.8k155970
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
add a comment |
I do not understand why rxvt-unicode doesn't display some Unicode characters correctly such as ☁ or ☂ while ⚡ is displayed correctly. These symbols are replaced by a little box as you can see in the screenshot:
Here's my locale:
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
And here my .Xresources:
URxvt.font: xft:Ubuntu Mono:size=11:antialias=true:hinting=true
URxvt.letterSpace: -2
URxvt.lineSpace: -2
URxvt.scrollKey: true
URxvt.depth: 32
URxvt.loginShell: true
URxvt.geometry: 100x30
URxvt.saveLines: 10000
URxvt.cutchars: "`"'&()*,:;<=>?[\]^$"
URxvt.scrollBar: false
URxvt.visualBell: true ```
These symbols are displayed correctly in gnome-terminal.
Suggestions from google are not ubuntu-related and they all suggest to add .utf-8 to locale, which I already have in my settings. If you can help me in any way it would be awesome, this problem is really bugging me!
unicode rxvt
edited 19 mins ago
Kevin Bowen
14.8k155970
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
add a comment |
I do not understand why rxvt-unicode doesn't display some Unicode characters correctly such as ☁ or ☂ while ⚡ is displayed correctly. These symbols are replaced by a little box as you can see in the screenshot:
Here's my locale:
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
And here my .Xresources:
URxvt.font: xft:Ubuntu Mono:size=11:antialias=true:hinting=true
URxvt.letterSpace: -2
URxvt.lineSpace: -2
URxvt.scrollKey: true
URxvt.depth: 32
URxvt.loginShell: true
URxvt.geometry: 100x30
URxvt.saveLines: 10000
URxvt.cutchars: "`"'&()*,:;<=>?[\]^$"
URxvt.scrollBar: false
URxvt.visualBell: true ```
These symbols are displayed correctly in gnome-terminal.
Suggestions from google are not ubuntu-related and they all suggest to add .utf-8 to locale, which I already have in my settings. If you can help me in any way it would be awesome, this problem is really bugging me!
unicode rxvt
edited 19 mins ago
Kevin Bowen
14.8k155970
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
I do not understand why rxvt-unicode doesn't display some Unicode characters correctly such as ☁ or ☂ while ⚡ is displayed correctly. These symbols are replaced by a little box as you can see in the screenshot:
Here's my locale:
LANG=en_US.UTF-8
LANGUAGE=en_US:en
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_US.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY=en_US.UTF-8
LC_MESSAGES="en_US.UTF-8"
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_US.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
And here my .Xresources:
URxvt.font: xft:Ubuntu Mono:size=11:antialias=true:hinting=true
URxvt.letterSpace: -2
URxvt.lineSpace: -2
URxvt.scrollKey: true
URxvt.depth: 32
URxvt.loginShell: true
URxvt.geometry: 100x30
URxvt.saveLines: 10000
URxvt.cutchars: "`"'&()*,:;<=>?[\]^$"
URxvt.scrollBar: false
URxvt.visualBell: true ```
These symbols are displayed correctly in gnome-terminal.
Suggestions from google are not ubuntu-related and they all suggest to add .utf-8 to locale, which I already have in my settings. If you can help me in any way it would be awesome, this problem is really bugging me!
unicode rxvt
unicode rxvt
edited 19 mins ago
Kevin Bowen
14.8k155970
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
edited 19 mins ago
Kevin Bowen
14.8k155970
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
edited 19 mins ago
Kevin Bowen
14.8k155970
edited 19 mins ago
Kevin Bowen
14.8k155970
edited 19 mins ago
Kevin Bowen
14.8k155970
14.8k155970
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
asked Jul 2 '13 at 20:37
random.cpprandom.cpp
1313
1313
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The screenshot is virtually unreadable due to lack of color contrast, but it seems that the reason for the problem is simply that the font being used does not contain glyphs for the characters ☁ or ☂. A little box is typically the way programs indicate the presence of a character that has been recognized but cannot be displayed due to lack of a glyph.
This explanation sounds problematic, because xrvt FAQ says: “When rxvt-unicode sees a character, it will first look at the base font. If the base font does not contain the character, it will go to the next font, and so on.” So it should find a glyph if any available font contains it. But presumably this process goes wrong, e.g. because character repertoire information in some font is faulty (a font may say it supports a character but lacks a glyph for it). Testing with different base font settings may help to identify the problem.
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
You're right, I've tested with Monospace and those glyphs are displayed. I didn't tested other fonts before, because Ubuntu Mono works perfectly in GVIM and gnome-terminal. Is there any possibility to set a fallback font for those glyphs?
– random.cpp
Jul 3 '13 at 7:28
1
Ok I found this workaround that does the trick:URxvt.font: xft:Ubuntu Mono:size=11,xft:Monospace:size=9:antialias=true:hinting=trueI set Ubuntu Mono as first font and Monospace as fallback, I had to set different sizes though.. Thanks for your help
– random.cpp
Jul 3 '13 at 7:54
add a comment |
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f315608%2fxrvt-unicode-doesnt-display-unicode-characters%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The screenshot is virtually unreadable due to lack of color contrast, but it seems that the reason for the problem is simply that the font being used does not contain glyphs for the characters ☁ or ☂. A little box is typically the way programs indicate the presence of a character that has been recognized but cannot be displayed due to lack of a glyph.
This explanation sounds problematic, because xrvt FAQ says: “When rxvt-unicode sees a character, it will first look at the base font. If the base font does not contain the character, it will go to the next font, and so on.” So it should find a glyph if any available font contains it. But presumably this process goes wrong, e.g. because character repertoire information in some font is faulty (a font may say it supports a character but lacks a glyph for it). Testing with different base font settings may help to identify the problem.
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
You're right, I've tested with Monospace and those glyphs are displayed. I didn't tested other fonts before, because Ubuntu Mono works perfectly in GVIM and gnome-terminal. Is there any possibility to set a fallback font for those glyphs?
– random.cpp
Jul 3 '13 at 7:28
1
Ok I found this workaround that does the trick:URxvt.font: xft:Ubuntu Mono:size=11,xft:Monospace:size=9:antialias=true:hinting=trueI set Ubuntu Mono as first font and Monospace as fallback, I had to set different sizes though.. Thanks for your help
– random.cpp
Jul 3 '13 at 7:54
add a comment |
The screenshot is virtually unreadable due to lack of color contrast, but it seems that the reason for the problem is simply that the font being used does not contain glyphs for the characters ☁ or ☂. A little box is typically the way programs indicate the presence of a character that has been recognized but cannot be displayed due to lack of a glyph.
This explanation sounds problematic, because xrvt FAQ says: “When rxvt-unicode sees a character, it will first look at the base font. If the base font does not contain the character, it will go to the next font, and so on.” So it should find a glyph if any available font contains it. But presumably this process goes wrong, e.g. because character repertoire information in some font is faulty (a font may say it supports a character but lacks a glyph for it). Testing with different base font settings may help to identify the problem.
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
You're right, I've tested with Monospace and those glyphs are displayed. I didn't tested other fonts before, because Ubuntu Mono works perfectly in GVIM and gnome-terminal. Is there any possibility to set a fallback font for those glyphs?
– random.cpp
Jul 3 '13 at 7:28
1
Ok I found this workaround that does the trick:URxvt.font: xft:Ubuntu Mono:size=11,xft:Monospace:size=9:antialias=true:hinting=trueI set Ubuntu Mono as first font and Monospace as fallback, I had to set different sizes though.. Thanks for your help
– random.cpp
Jul 3 '13 at 7:54
add a comment |
The screenshot is virtually unreadable due to lack of color contrast, but it seems that the reason for the problem is simply that the font being used does not contain glyphs for the characters ☁ or ☂. A little box is typically the way programs indicate the presence of a character that has been recognized but cannot be displayed due to lack of a glyph.
This explanation sounds problematic, because xrvt FAQ says: “When rxvt-unicode sees a character, it will first look at the base font. If the base font does not contain the character, it will go to the next font, and so on.” So it should find a glyph if any available font contains it. But presumably this process goes wrong, e.g. because character repertoire information in some font is faulty (a font may say it supports a character but lacks a glyph for it). Testing with different base font settings may help to identify the problem.
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
The screenshot is virtually unreadable due to lack of color contrast, but it seems that the reason for the problem is simply that the font being used does not contain glyphs for the characters ☁ or ☂. A little box is typically the way programs indicate the presence of a character that has been recognized but cannot be displayed due to lack of a glyph.
This explanation sounds problematic, because xrvt FAQ says: “When rxvt-unicode sees a character, it will first look at the base font. If the base font does not contain the character, it will go to the next font, and so on.” So it should find a glyph if any available font contains it. But presumably this process goes wrong, e.g. because character repertoire information in some font is faulty (a font may say it supports a character but lacks a glyph for it). Testing with different base font settings may help to identify the problem.
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
answered Jul 3 '13 at 6:35
Jukka K. KorpelaJukka K. Korpela
47437
47437
You're right, I've tested with Monospace and those glyphs are displayed. I didn't tested other fonts before, because Ubuntu Mono works perfectly in GVIM and gnome-terminal. Is there any possibility to set a fallback font for those glyphs?
– random.cpp
Jul 3 '13 at 7:28
1
Ok I found this workaround that does the trick:URxvt.font: xft:Ubuntu Mono:size=11,xft:Monospace:size=9:antialias=true:hinting=trueI set Ubuntu Mono as first font and Monospace as fallback, I had to set different sizes though.. Thanks for your help
– random.cpp
Jul 3 '13 at 7:54
add a comment |
You're right, I've tested with Monospace and those glyphs are displayed. I didn't tested other fonts before, because Ubuntu Mono works perfectly in GVIM and gnome-terminal. Is there any possibility to set a fallback font for those glyphs?
– random.cpp
Jul 3 '13 at 7:28
1
Ok I found this workaround that does the trick:URxvt.font: xft:Ubuntu Mono:size=11,xft:Monospace:size=9:antialias=true:hinting=trueI set Ubuntu Mono as first font and Monospace as fallback, I had to set different sizes though.. Thanks for your help
– random.cpp
Jul 3 '13 at 7:54
You're right, I've tested with Monospace and those glyphs are displayed. I didn't tested other fonts before, because Ubuntu Mono works perfectly in GVIM and gnome-terminal. Is there any possibility to set a fallback font for those glyphs?
– random.cpp
Jul 3 '13 at 7:28
You're right, I've tested with Monospace and those glyphs are displayed. I didn't tested other fonts before, because Ubuntu Mono works perfectly in GVIM and gnome-terminal. Is there any possibility to set a fallback font for those glyphs?
– random.cpp
Jul 3 '13 at 7:28
1
1
Ok I found this workaround that does the trick:
URxvt.font: xft:Ubuntu Mono:size=11,xft:Monospace:size=9:antialias=true:hinting=true I set Ubuntu Mono as first font and Monospace as fallback, I had to set different sizes though.. Thanks for your help– random.cpp
Jul 3 '13 at 7:54
Ok I found this workaround that does the trick:
URxvt.font: xft:Ubuntu Mono:size=11,xft:Monospace:size=9:antialias=true:hinting=true I set Ubuntu Mono as first font and Monospace as fallback, I had to set different sizes though.. Thanks for your help– random.cpp
Jul 3 '13 at 7:54
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f315608%2fxrvt-unicode-doesnt-display-unicode-characters%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
