2

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

finefoot
  • 561

1 Answers1

4

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.