New version of fontforge and the src_uri is no longer .tgz but .tar.bz2 instead.
Created attachment 81864 [details] fontforge-20060209.ebuild
*** Bug 128800 has been marked as a duplicate of this bug. ***
This newer version of fontforge should be in portage, as newer versions of Wine depend on it (more specifically, fontforge-20050624 generates wrong fonts for a number of cases in the Wine build, this is fixed in newer versions of fontforge). Do a 'wine notepad' and type something in Notepad to see the issue. Browsing through the fonts list in Notepad also reveals a few other broken fonts.
You are correct, Neil. Please see bug #125145. This bug blocks that one. Perhaps the submitter or maintainer will add that bug to the blocks list here. Compiling wine > 0.9.9 with the new fontforge allows fonts to be properly compiled and viewed.
(In reply to comment #4) > You are correct, Neil. Please see bug #125145. This bug blocks that one. > Perhaps the submitter or maintainer will add that bug to the blocks list here. > Compiling wine > 0.9.9 with the new fontforge allows fonts to be properly > compiled and viewed. Nope. Issue of bug #125145 was completely different from this. That was related from the fonts in the menu and the problem was from an unexistant fonftforge on the system. This bugs affect just other fonts which older versions of fontforge don't build correctly.
Actually, the aspect of the default font is affected by fontforge. If the fonts are not made correctly, they will be wrong. I originally had made a new bug, but the wine maintainers thought it was close enough to be rolled up into the bug #125145. Regardless, updated fontforge solves the problems.
(In reply to comment #6) > Regardless, updated fontforge solves the problems. Yeah, that's clear and the new fontforge should be added into portage.
(In reply to comment #7) > (In reply to comment #6) > > Regardless, updated fontforge solves the problems. > > Yeah, that's clear and the new fontforge should be added into portage. > > I heard from vapier (Wine maintainer) and he's going to try and bug (pun intended) the fontforge maintainer to get this going.
Created attachment 84187 [details] fontforge-20060406.ebuild
fontforge-20060406 now in portage