Xft hinting causes "bolding" problem in emacs-snapshot

Bug #234187 reported by rfvuhbtg
2
Affects Status Importance Assigned to Milestone
xft (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: libxft2

In essence, this bug report is a duplicate of bug #221100, filed under the emacs-snapshot package in Hardy.

Link: https://bugs.launchpad.net/ubuntu/+source/emacs-snapshot/+bug/221100

I'm refiling this bug report because it looks like Xft may be the root culprit, not the emacs-snapshot package. I'm just not sure exactly which of the xft packages in the repositories to file this against, but my guess is libxft2.

Please refer to the previous bug report for the details. However, I've found that the problem persists if any kind of smoothing is enabled, not just subpixel. The workaround suggested in the bug report does prevent the problem from happening, but it also disables any and all font smoothing, at least on laptop displays, thus defeating the purpose of using font smoothing and making all text ugly to the point of almost unreadable. A proper patch to Xft would be best.

I never used Gutsy, but this problem did not exist under Feisty.

I have also included a picture for reference. Look at the second to last "y" in the line. What happened there will happen at random to potentially any character. (And if you set the default font to a "bold" version, the character will get even "bolder.")

Revision history for this message
rfvuhbtg (rfvuhbtg) wrote :
Revision history for this message
rfvuhbtg (rfvuhbtg) wrote :

On second thought, this might be only with Emacs and not with Xft. Gvim/vim doesn't have any problems, anyway, but I don't know what that uses to render fonts.

I'm not really qualified to know exactly where the problem is, but I'd advise anyone coming across this to look at the original bug referenced in the first post. Once that is fixed, this bug report and be marked "fixed."

Revision history for this message
rfvuhbtg (rfvuhbtg) wrote :

Turns out a fix has been found for this bug. It was in emacs-snapshot and not xft after all. See the linked emacs-snapshot bug report for details. All it would take to fix this bug is for the emacs-snapshot maintainers to rebuild all the emacs-snapshot debs from the current cvs and update the repository.

Revision history for this message
rfvuhbtg (rfvuhbtg) wrote :

Marking invalid since xft apparently wasn't the root cause.

Changed in xft:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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