Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 419335

Summary: media-libs/fontconfig-? - fc-cat charmap field shows gibberish
Product: Gentoo Linux Reporter: ac.serbanescu
Component: [OLD] UnspecifiedAssignee: Gentoo Fonts Team <fonts>
Status: RESOLVED INVALID    
Severity: normal CC: immerdabeiundnie
Priority: Normal    
Version: unspecified   
Hardware: AMD64   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---

Description ac.serbanescu 2012-06-02 10:41:21 UTC
Hello,

I've stumbled over this problem when the Terminus font wouldn't display unicode characters under mlterm or xterm if handled by xft (but did display them when handled by X).

When doing "fc-cat | grep Terminus" I found out that the charset field displayed gibberish (so I guess that's why it couldn't select iso10646-1 out of the rest). 

It turned out that all my fonts were affected, not just Terminus, but I didn't notice it because Terminus was the only one which brought in non-unicode fonts. What's wrong?

Reproducible: Always

Steps to Reproduce:
I'm not sure. I remember it always happened, but I ignored since I thought its scope was limited.

If you have Terminus and Xterm with TrueType support, you can add "XTerm.VT100.faceName: Terminus" to .Xdefaults, then type some character in xterm that's in the Unicode version, but not in the others, such as ƒ. Also, run fc-cat.
Actual Results:  
You would see a box instead of an ƒ in xterm. Also, fc-cat would display something like:

"ter-x16n.pcf.gz" 0 "Terminus:style=Regular:slant=0:weight=80:width=100:pixelsize=16:spacing=110:foundry=xos4:antialias=False:index=0:outline=False:scalable=False:charset= |>^1!|>^1!|>^1!P0oWQ |>^1!|>^1!|>^1!!!!%#|>^1!|>^1!|>^1!|%1ViEs8D6!2b&R  !!!)$&olY4!3yva%V7@B!!K?&!!K?&6~ryb7{o>{ !!!.%!!!X/!!!)$  |>[gE|>^0{!!&TQ!$Ve?!!!1&|>^1!|>^1!|>^1! 9W@fi(){Nj|>T)!#%lqi!!#(E !(/HW   5H<IZ!!$/f!{{BZ!!#0G|>TE*Bao&! P0oWR !!$rM  !!#3H!)wC#!!!!n  !)gMi!%J@H!)gMi !!#6Ii^WNb!!!<Y!!!%#!!!!Z    !!#9J!!.)(!!!!%   8?0Ef  !!#>K!!$5h!!!!5      !!#AL|>^.4|>^1!|>T^4!!#0F|7JA^(8HCz!{{iz !!#DM +~x|C!!!!(!!!LG    !!+fv     9WIlj  !!.%!       /?6HG:lang=aa|af|ast|av|ay|az-az|ba|bm|be|bg|bi|bin|br|bs|bua|ca|ce|ch|chm|co|cs|cv|da|de|el|en|eo|es|et|eu|fi|fj|fo|fr|fur|fy|gd|gl|gn|gv|haw|ho|hr|hu|ia|ig|id|ie|ik|io|is|it|kaa|ki|kk|kl|kum|kv|kw|ky|la|lb|lez|ln|lt|lv|mg|mh|mi|mk|mo|mt|nb|nds|nl|nn|no|nr|nso|ny|oc|om|os|pl|pt|rm|ro|ru|sah|se|sel|sh|sk|sl|sm|sma|smj|smn|so|sq|sr|ss|st|sv|sw|tg|tk|tl|tn|to|tr|ts|tt|tw|tyv|uk|uz|vo|vot|wa|wen|wo|xh|yap|zu|ak|an|crh|csb|fat|fil|hsb|ht|jv|kj|ku-tr|kwm|lg|li|mn-mn|ms|na|ng|pap-an|pap-aw|rn|rw|sc|sg|sn|su|ty|za:fontversion=0:fontformat=PCF:decorative=False"


Expected Results:  
If you select a font with "XTerm.VT100.font: -xos4-terminus-medium-r-normal--16-160-72-72-c-80-iso10646-1" you would see the expected character. Also, fc-cat should display a real charset.

I'm running Gentoo on AMD64 with the latest stable packages, albeit configured with minimal options.

Portage 2.1.10.49 (default/linux/amd64/10.0, gcc-4.5.3, glibc-2.14.1-r3, 3.2.12-gentoo x86_64)
=================================================================
System uname: Linux-3.2.12-gentoo-x86_64-AMD_Phenom-tm-_II_X6_1100T_Processor-with-gentoo-2.1
Timestamp of tree: Sat, 02 Jun 2012 08:15:01 +0000
app-shells/bash:          4.2_p20
dev-lang/python:          2.7.3-r1, 3.2.3
dev-util/cmake:           2.8.7-r5
dev-util/pkgconfig:       0.26
sys-apps/baselayout:      2.1-r1
sys-apps/openrc:          0.9.8.4
sys-apps/sandbox:         2.5
sys-devel/autoconf:       2.13, 2.68
sys-devel/automake:       1.9.6-r3, 1.11.1
sys-devel/binutils:       2.21.1-r1
sys-devel/gcc:            4.5.3-r2
sys-devel/gcc-config:     1.5-r2
sys-devel/libtool:        2.4-r1
sys-devel/make:           3.82-r1
sys-kernel/linux-headers: 3.1 (virtual/os-headers)
sys-libs/glibc:           2.14.1-r3
Repositories: gentoo x-portage
ACCEPT_KEYWORDS="amd64"
ACCEPT_LICENSE="*"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-O2 -march=native -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc"
CONFIG_PROTECT_MASK="/etc/ca-certificates.conf /etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/gentoo-release /etc/revdep-rebuild /etc/sandbox.d /etc/terminfo /etc/texmf/language.dat.d /etc/texmf/language.def.d /etc/texmf/updmap.d /etc/texmf/web2c"
CXXFLAGS="-O2 -march=native -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="assume-digests binpkg-logs distlocks ebuild-locks fixlafiles news parallel-fetch protect-owned sandbox sfperms strict unknown-features-warn unmerge-logs unmerge-orphans userfetch"
FFLAGS=""
GENTOO_MIRRORS="http://ftp.romnet.org/gentoo/"
LANG="en_GB.utf8"
LDFLAGS="-Wl,-O1 -Wl,--as-needed"
LINGUAS="en_GB"
MAKEOPTS="-j7"
PKGDIR="/usr/portage/packages"
PORTAGE_CONFIGROOT="/"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --stats --human-readable --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://ftp.romnet.org/gentoo-portage"
USE="3dnow 3dnowext alsa amd64 minimal mmx mmxext multilib nptl opencl opengl openmp smp sse sse2 sse3 sse4a threads threadsafe unicode vaapi xv" ELIBC="glibc" INPUT_DEVICES="evdev" KERNEL="linux" LINGUAS="en_GB" USERLAND="GNU" VIDEO_CARDS="fglrx"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_BUNZIP2_COMMAND, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, USE_PYTHON
Comment 1 Hans 2012-09-14 22:56:07 UTC
From what I can tell, this is not a bug. Reasons:

a) fc-cat does not display "gibberish", what you are seeing there is just about what it is supposed to look like

b) using "XTerm.VT100.faceName: Terminus" does not select the font you actually want

c) "XTerm.VT100.font: -xos4-terminus-medium-r-normal--16-160-72-72-c-80-iso10646-1" selects the font you want... because you actually tell it to, unlike you did in the attempt you mentioned before. Read the man page.


I think you should read up on how to select fonts in your preferred terminal emulator. While I don't know about mlterm, xterm has a somewhat strange unicode implementation, but it seems to work.
Took me a while to figure things out for my own system (using rxvt-unicode). :)