Many monospace fonts not properly spaced when mixing weights in gedit/gtksourceview

Bug #565393 reported by Dag Odenhall
76
This bug affects 13 people
Affects Status Importance Assigned to Milestone
ttf-droid (Ubuntu)
Confirmed
Undecided
Unassigned
Declined for Jaunty by Sebastien Bacher
Declined for Karmic by Sebastien Bacher
Declined for Lucid by Sebastien Bacher

Bug Description

Binary package hint: ttf-droid

I was coding in gedit with Droid Sans Mono 10 when I couldn't line up some Python code properly.

Revision history for this message
Dag Odenhall (dag.odenhall) wrote :
Revision history for this message
Dag Odenhall (dag.odenhall) wrote :
Revision history for this message
Dag Odenhall (dag.odenhall) wrote :

Seems to be related to mixing bold and normal; Droid Sans Mono Bold lines up properly.

Revision history for this message
Lucas Vieites (lucasvieites) wrote :

According to the font's creators (see: http://www.droidfonts.com/droidfonts/about/) this bug could be unrelated to the .ttf file. At about half-way into the article (under the Droid Sans Mono image) it says:
"We did one weight of the mono – the 3 other styles (italic, bold and bold italic) are currently made algorithmically by the font renderer."
Could this mean that the incorrect rendering is due to Xft2, freetype or a combination of these?

Revision history for this message
Dag Odenhall (dag.odenhall) wrote :

I have this issue with many other fonts as well, such as Monofur and Inconsolata. Should try the buggy fonts in something other than gedit/gtksourceview probably...

summary: - Droid Sans Mono not really monospaced
+ Many monospace fonts not properly spaced when mixing weights in
+ gedit/gtksourceview
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ttf-droid (Ubuntu):
status: New → Confirmed
Revision history for this message
Ruslan F. Atnabayeff (rfatnabayeff) wrote :

Looks like the bug appears when the bold version of the font is not directly available and is artificially created by the rendering background. See the discussion with examples: http://askubuntu.com/questions/100672/how-to-prevent-automatic-bold-version-of-a-font-to-be-wider-than-regular-havin

Revision history for this message
Ruslan F. Atnabayeff (rfatnabayeff) wrote :

Removing a symbolic link to 90-synthetic.conf from /etc/fonts/conf.d/ makes the fonts properly spaced, but disables the artificial emboldening of fonts that do not have the dedicated bold versions.

Revision history for this message
james_mcl (james-d-mclaughlin-googlemail) wrote :

I know this hasn't been posted in since February, but I wanted to note that the removal of 90-synthetic.conf's symlink from /etc/fonts/conf.d/ has an irritating side effect when using gedit (or pluma) - unsaved documents no longer have their names italicised in the side panel (or "side pane").

This problem doesn't occur when using the other workaround from http://askubuntu.com/questions/100672/how-to-prevent-automatic-bold-version-of-a-font-to-be-wider-than-regular-havin - that is, the one in which you create ~/.fonts.conf and add the XML code from that site to it.

Revision history for this message
Ruslan F. Atnabayeff (rfatnabayeff) wrote :

90-synthetic.conf enables synthesis of bold and italic version of the fonts that do not originally have those versions. Removing the symlink disables the synthesis, so fonts without built-in bold and/or italic would render as regular. The issue is indeed somewhere within the font renderer - within freetype, probably.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.