Public bug reported: 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. ** Affects: xterm (Ubuntu) Importance: Undecided Status: New ** Tags: saucy ** Tags added: saucy -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1207971 Title: xterm default is to fail to use available UTF-8 fonts To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1207971/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
