Opened 11 years ago

Closed 11 years ago

#8674 closed defect (fixed)

Use older version of FreeMono.ttf

Reported by: Jim Stichnoth <stichnot@…> Owned by: sphery
Priority: minor Milestone: unknown
Component: MythTV - General Version: Unspecified
Severity: medium Keywords:
Cc: Ticket locked: no


The version of FreeMono?.ttf included in myth has a problem with the 2-character "st" sequence, which is displayed as a "t" with a slight bit of leading space. This makes it look like the "s" is missing. There is obviously a mistake in the kerning, but a larger question is why a monospaced font should include kerning at all.

I tried using QFont::setKerning(false) and QFont::setFixedPitch(true), to no effect.

I recommend downgrading to a version of FreeMono?.ttf that predates kerning, specifically the 2008-03-23 version (

Change History (4)

comment:1 Changed 11 years ago by stuartm

Better yet, let's just drop FreeMono? in favour of something better. Now that the OSD* has been ported to mythui we can use any font we want and there are several better open source/free fonts available.

*MHEG code still seems to use freetype, but it only uses FreeSans?, not FreeMono?.

comment:2 Changed 11 years ago by sphery

Owner: set to sphery
Status: newaccepted

comment:3 Changed 11 years ago by Jim Stichnoth <stichnot@…>

My testing was faulty, I somehow thought myth was using a later version of FreeFont?. The current version in myth has the problem, but the latest version of FreeMono?.ttf (2009-01-04) does not have the problem, when tested on my system. So I recommend moving to the latest FreeFont?.

comment:4 Changed 11 years ago by sphery

Resolution: fixed
Status: acceptedclosed

(In [25382]) Update the FreeFont? fonts distributed with MythTV to the current 20090104 version.

The 20060126 version we were previously distributing had some kerning issues that are now apparent since the OSD is rendered using MythUI (which uses Qt library code) rather than our own custom freetype code. Note, also, that MythArchive? was modified to work with the old FreeFont? fonts in [14025], but the description makes it sound like the new fonts will work, too.

Refs #3749. Fixes #8674. Thanks to Jim Stichnoth for testing and identifying the issue.

Note: See TracTickets for help on using tickets.