Bug 60865

Summary:	Bitstream Vera Sans Mono font not rendered correctly
Product:	[Applications] konsole	Reporter:	Rick Kennell <kennell>
Component:	general	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED WORKSFORME
Severity:	normal
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	menu1.png menu2.png menu1: the file to 'cat' to produce menu1.png menu2: the file to 'cat' to produce menu2.png

Description Rick Kennell 2003-07-07 09:01:08 UTC

Version:            (using KDE KDE 3.1.2)
Installed from:    Debian testing/unstable Packages
OS:          Linux

For some types of text, the Bitstream Vera Sans Mono font is not rendered correctly.  Some characters are rendered with double width depending on their color or bold attribute.  The effect is most pronounced in the lxdialog display of the Linux kernel "make menuconfig".

I'll attempt to attach examples below.

This only happens when I use Konsole with Bitstream Vera Sans Mono.  Changing the font corrects the problem.  I do not see the problem when using this font in gnome-terminal.  The size of the font is irrelevant.

This problem may be related to Bug 52538.

Comment 1 Rick Kennell 2003-07-07 09:03:30 UTC

Created attachment 1957 [details]
menu1.png

Notice that some of the letters on the left edge of the menu are missing.
Some of the border characters are double-spaced.

Comment 2 Rick Kennell 2003-07-07 09:05:01 UTC

Created attachment 1958 [details]
menu2.png

Again, things are messed up on the left side.

Comment 3 Rick Kennell 2003-07-07 09:06:22 UTC

Created attachment 1959 [details]
menu1: the file to 'cat' to produce menu1.png

'cat' this file to produce the effect seen in menu1.png.

Comment 4 Rick Kennell 2003-07-07 09:07:28 UTC

Created attachment 1960 [details]
menu2: the file to 'cat' to produce menu2.png

'cat' this file to produce the effect shown in menu2.png.

Comment 5 Rick Kennell 2004-05-11 19:59:30 UTC

Resolved a long time ago.  The 3.2.0 release certainly worked correctly.