Invisible fonts regression
I am no longer able to see fonts in: - the GTA installer - for example on the intial screen ("What language to use?") - Steam (*with* Tahoma previously installed and working). When selecting menus fonts will flash quickly making the menu visible, and then disappear. In addition, when re-creating a new clean wine root, I also lose the ability to see fonts in winecfg. This is Wine 0.9.11 on Fedora Rawhide x86_64. There is no error output. The Steam problem was in the last release as well. What should I do to track down the problem?
Ivan Gyurdiev wrote:
I am no longer able to see fonts in: - the GTA installer - for example on the intial screen ("What language to use?") - Steam (*with* Tahoma previously installed and working). When selecting menus fonts will flash quickly making the menu visible, and then disappear.
In addition, when re-creating a new clean wine root, I also lose the ability to see fonts in winecfg. This is Wine 0.9.11 on Fedora Rawhide x86_64. There is no error output. The Steam problem was in the last release as well.
What should I do to track down the problem?
I dont know if this will help, but it is worth a shot... Install fontforge from fontforge.sourceforge.net Tom
On Thursday 06 April 2006 11:06, Tom Spear (Dustin Booker, Dustin Navea) wrote:
I dont know if this will help, but it is worth a shot... Install fontforge from fontforge.sourceforge.net
Actually it looks like having fontforge installed *causes* the problem. Try removing /usr/local/share/wine/fonts or making it inaccessible. -- Troy Rollo - wine(a)troy.rollo.name
On Thursday 06 April 2006 12:31, Troy Rollo wrote:
On Thursday 06 April 2006 11:06, Tom Spear (Dustin Booker, Dustin Navea)
wrote:
I dont know if this will help, but it is worth a shot... Install fontforge from fontforge.sourceforge.net
Actually it looks like having fontforge installed *causes* the problem. Try removing /usr/local/share/wine/fonts or making it inaccessible.
The problem is due to an old version of fontforge. In Debian, version 0.0.20041218-0.1 generates incorrect ascent information for the Windows font header. Version 0.0.20051205-0.1 gets it right. For Debian users, 0.0.20051205-0.1 is only available in testing and higher. Unfortunately 0.0.20051205-0.1 depends on other things from testing (such as libc6 >= 2.3.5-1), so if you want to build on a pure Sarge system you will need to either do without fontforge, build it yourself, or find a backport somewhere. -- Troy Rollo - wine(a)troy.rollo.name
Troy Rollo wrote:
On Thursday 06 April 2006 12:31, Troy Rollo wrote:
On Thursday 06 April 2006 11:06, Tom Spear (Dustin Booker, Dustin Navea)
wrote:
I dont know if this will help, but it is worth a shot... Install fontforge from fontforge.sourceforge.net
Actually it looks like having fontforge installed *causes* the problem. Try removing /usr/local/share/wine/fonts or making it inaccessible.
The problem is due to an old version of fontforge. In Debian, version 0.0.20041218-0.1 generates incorrect ascent information for the Windows font header. Version 0.0.20051205-0.1 gets it right. For Debian users, 0.0.20051205-0.1 is only available in testing and higher. Unfortunately 0.0.20051205-0.1 depends on other things from testing (such as libc6 >= 2.3.5-1), so if you want to build on a pure Sarge system you will need to either do without fontforge, build it yourself, or find a backport somewhere.
Is there not an option for debian users similar to rpm's --nodeps option where it doesnt check the dependencies but installs anyways?
On Thursday 06 April 2006 13:54, Tom Spear (Dustin Booker, Dustin Navea) wrote:
Is there not an option for debian users similar to rpm's --nodeps option where it doesnt check the dependencies but installs anyways?
There is, but it's bad mojo to use it - it will hurt down the track more than it will to build a backport. Given the problems with older fontforge, it would be nice if the configure script verified that the fontforge version in use was recent enough to work. The problem is there are 21 versions between the two versions I have tested, so unless we're willing to just say "20051205 or higher" somebody will have to figure out which of those is the first viable version. -- Troy Rollo - wine(a)troy.rollo.name
Actually it looks like having fontforge installed *causes* the problem. Try removing /usr/local/share/wine/fonts or making it inaccessible.
The problem is due to an old version of fontforge. In Debian, version 0.0.20041218-0.1 generates incorrect ascent information for the Windows font header. Version 0.0.20051205-0.1 gets it right. For Debian users, 0.0.20051205-0.1 is only available in testing and higher. Unfortunately 0.0.20051205-0.1 depends on other things from testing (such as libc6 >= 2.3.5-1), so if you want to build on a pure Sarge system you will need to either do without fontforge, build it yourself, or find a backport somewhere.
Hi, I have: fontforge-20060125-6.fc5 installed. I also have every other font under the sun installed, as this is an "everything" install. Removing or moving /usr/share/wine/fonts causes wine to refuse to generate .wine, and start up. In order for that to work, it seems wine requires the directory to exist, and for there to be at least one file in it (/usr/share/wine/fonts/* exists). Making a bogus file in there makes it work. I can see fonts in winecfg, and fonts in the GTA installer in a newly created wine root. I haven't yet tried to install Steam in there. Using my old wine root, Steam still does not work. Otoh the GTA works with the old root.
On Thu, Apr 06, 2006 at 01:49:52PM +1000, Troy Rollo wrote:
On Thursday 06 April 2006 12:31, Troy Rollo wrote:
On Thursday 06 April 2006 11:06, Tom Spear (Dustin Booker, Dustin Navea)
wrote:
I dont know if this will help, but it is worth a shot... Install fontforge from fontforge.sourceforge.net
Actually it looks like having fontforge installed *causes* the problem. Try removing /usr/local/share/wine/fonts or making it inaccessible.
The problem is due to an old version of fontforge. In Debian, version 0.0.20041218-0.1 generates incorrect ascent information for the Windows font header. Version 0.0.20051205-0.1 gets it right. For Debian users, 0.0.20051205-0.1 is only available in testing and higher. Unfortunately 0.0.20051205-0.1 depends on other things from testing (such as libc6 >= 2.3.5-1), so if you want to build on a pure Sarge system you will need to either do without fontforge, build it yourself, or find a backport somewhere.
Troy, Could you send me ms_sans_serif.ttf that the broken fontforge generates? Thanks, Huw. -- Huw Davies huw(a)codeweavers.com
On Thu, Apr 06, 2006 at 01:49:52PM +1000, Troy Rollo wrote:
The problem is due to an old version of fontforge. In Debian, version 0.0.20041218-0.1 generates incorrect ascent information for the Windows font header. Version 0.0.20051205-0.1 gets it right. For Debian users, 0.0.20051205-0.1 is only available in testing and higher. Unfortunately 0.0.20051205-0.1 depends on other things from testing (such as libc6 >= 2.3.5-1), so if you want to build on a pure Sarge system you will need to either do without fontforge, build it yourself, or find a backport somewhere.
http://www.backports.org/ has it. Jan
participants (5)
-
Huw D M Davies -
Ivan Gyurdiev -
Jan Zerebecki -
Tom Spear (Dustin Booker, Dustin Navea) -
Troy Rollo