single-width unicode chars are displayed double-width

[Bas Zoetekouw]

Ever since I upgraded from breezy to dapper, gnome-terminal doesn't display all unicode characters correctly anymore. The lowest 256 character (i.e. the unicode blocks basic latin and latin-1 supplement) are displayed correctly,
but characters from (for example) the latin extended A/B and greek/coptic blocks are displayed as double-width characters, while they should be single-width (see screenshot).

This only happens in gnome-terminal: other terminals (xterm specifically) and
other gnome input boxes (the gnome-character-map input line for example) work
fine and display the characters as single-width.

My locales are:
[bas@ophelia]~> locale
LANG=en_GB.UTF-8
LANGUAGE=en_NL:en
LC_CTYPE=en_GB.UTF-8
LC_NUMERIC="en_GB.UTF-8"
LC_TIME=nl_NL.UTF-8
LC_COLLATE="en_GB.UTF-8"
LC_MONETARY=nl_NL.UTF-8
LC_MESSAGES="en_GB.UTF-8"
LC_PAPER=nl_NL.UTF-8
LC_NAME="en_GB.UTF-8"
LC_ADDRESS="en_GB.UTF-8"
LC_TELEPHONE="en_GB.UTF-8"
LC_MEASUREMENT=nl_NL.UTF-8
LC_IDENTIFICATION="en_GB.UTF-8"
LC_ALL=

I'm using gnome-terminal 2.13.0-0ubuntu2 on dapper.

[Bas Zoetekouw (baszoetekouw)]

Hmm, this systems doesn't seem to be able to handle attachments. The screenshot I mentioned above, can be found at http://zoetekouw.net/screens/screen70.png

The é, ç and ô chars (from latin1-supplement) are displayed correctly, but the others chars are double-width instead of single width.

[Bas Zoetekouw (baszoetekouw)]

Ah, found the attachment uplaod function ;)

[Sebastien Bacher (seb128)]

Thanks for your bug. Do you still have that issue? Does it happen on the command line too or only with vim? How do you create the chars? I've tried by doing some dnd from gucharmap and that works fine for me

[Bas Zoetekouw (baszoetekouw)]

Hey Sebastian!

Yeah, I still have this bug. It happens with all console application, including the shell command line and applications like slrn and mutt. It doesn't seem to matter hoe I create the chars; I've tried using the compose key, and by copy-and-paste from gnome-character-map. In both cases the problem show up.

Please let me know if you need some more info, or is I can do something else to debug this problem.

[Bas Zoetekouw (baszoetekouw)]

Hmm, it seems it's a font issue. I use a bitmap font for my terminals (fixed-semicondensed), but if I change the font to a scalable one (like Monospace), all chars are displayed correctly.

It's not an issue with the fixed-semicondensed font itself though, as xterm display all characters correctly with the same font.

It's also not a fontconfig/pango issue, as other gnome applications (like gedit) also display all characters correctly with the fixed-semicondensed font.

[Sebastien Bacher (seb128)]

It works fine for me with the same font, what setting do you use exactly for fontconfig and the font?

[Bas Zoetekouw (baszoetekouw)]

My fontconfig configuration is pretty default:

[bas@ophelia]/etc/fonts/conf.d> ls
20-debconf-sub-pixel.conf@ no-bitmaps.conf sub-pixel.conf yes-bitmaps.conf
autohint.conf no-sub-pixel.conf unhinted.conf

and in ~/.fonts.conf contains some stuff about hinting and rewriting of Helvetica fonts (I'll attach the file).

The setting I use for the fixed font is:

<entry name="monospace_font_name" mtime="1136393560" type="string">
<stringvalue>Fixed Semi-Condensed 10</stringvalue>
</entry>

[Bas Zoetekouw (baszoetekouw)]

my ~/.fonts.conf

[Sebastien Bacher (seb128)]

I'm tempted to categorize that as not an app bug, it's due to the font. You can try picking different font size and note if that fixes your issue

[Bas Zoetekouw (baszoetekouw)]

It's definately not a font bug: gedit for example can use the same font perfectly.

[Sebastien Bacher (seb128)]

What does "fc-match fixed-semicondensed" return?

[Bas Zoetekouw (baszoetekouw)]

[bas@ophelia]~> fc-match fixed-semicondensed
12x13ja.pcf.gz: "Fixed" "ja"

[Sebastien Bacher (seb128)]

My config is matching the same font and works fine. What fontconfig options do you have (dpkg-reconfigure fontconfig, the default choices are the current options used)?

[Bas Zoetekouw (baszoetekouw)]

Hmm, it seems I can't reproduce this anymore; everything works fine now.

[Sebastien Bacher (seb128)]

I'm closing the bug as fixed so, feel free to reopen if you get it again