Bug 346930

Summary:	Bad rendering, white space on Droid Sans
Product:	[Applications] konsole	Reporter:	Turbo <turbo477>
Component:	font	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	justin.zobel, nucrap
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Turbo 2015-04-30 03:52:05 UTC

Konsole v. 3.0.1
KDE Frameworks 5.9.0
Kubuntu 15.04 Plasma 5.3

Very easy, just change Edit current profile and set the font to Droid Sans (bold). Now, there is a whole invisible "char" or empty line getting in the way when, for example, using BS key. If you use Monospace font it works fine.

Reproducible: Always

Steps to Reproduce:
1. Change and Edit current profile and set the font to Droid Sans (bold).
2. Apply.


Actual Results:  
Now, there is a whole invisible "char" or empty space getting in the way when, for example, using Back Space key.

Expected Results:  
Normal drawing of Droid Sans font. Surely there are others affected.


Monospace font works fine.

Comment 1 nuc 2015-05-15 10:34:37 UTC

This is to be expected since terminals are only to be used with monospaced fonts and Droid Sans (bold) isn't monospaced, try Droid Sans Mono instead.

However the question is why you get "Droid Sans" displayed as an option at all. Normally the options dialog only shows fixed-witdth fonts (so you shouldn't even get Droid Sans as an option)...

Is Droid Sans the only non-monospaced font in the options dialog, or do you get shown every type of font?

Comment 2 Turbo 2015-05-25 18:57:43 UTC

Hi,

I change it on general preferences, you cant set the fonts for all of Kubuntu (I normally set them in Droid Sans and then check Bold).

Regards.

Comment 3 Justin Zobel 2020-11-01 05:23:02 UTC

(In reply to Turbo from comment #2)
> Hi,
> 
> I change it on general preferences, you cant set the fonts for all of
> Kubuntu (I normally set them in Droid Sans and then check Bold).
> 
> Regards.

Hi Turbo, as mentioned by Phillip this is expected, terminals use monospaced fonts by default for this reason to ensure text is always legible.

In your initial report as well you confirmed that Monospace fonts work fine. I'm going to close this as not a bug, if you feel that it needs further discussion please open a new bug report.