xterm default is to fail to use available UTF-8 fonts

Bug #1207971 reported by B Bobo
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xterm (Ubuntu)
New
Wishlist
Unassigned

Bug Description

When "xterm" is started in its default out-of-the-box condition, i.e. without any command-line, .Xresources, or .[a-Z]*rc options, it should be able to display text in any of the available UTF-8 fonts, regardless of locale.

Install a range of truetype CJK and non-truetype CJK fonts and start gnome-terminal in a normal Ubuntu 13.04 Unity session. At the command-line, try viewing some foreign text in UTF-8,

 $ curl http://www.nhk.or.jp/ | lynx -dump -stdin

Notice how all of the characters are displayed by gnome-terminal. It should all work ok. If not, install more CJK fonts.

Start xterm at the command-line inside the gnome-terminal to ensure xterm is given the identical environment variables as gnome-terminal,

 $ xterm&

At the command-line in the xterm, try viewing some foreign text in UTF-8,

 $ curl http://www.nhk.or.jp/ | lynx -dump -stdin

What happens is that xterm displays the foreign UTF-8 text with little empty squares representing missing UTF-8 characters.

Tags: saucy
B Bobo (yout-bobo123)
tags: added: saucy
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

i'm pretty sure that's how xterm users want it to behave, you can enable truetype fonts easily from the menu..

Changed in xterm (Ubuntu):
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.