Is this bug 5057? ...
I've just installed the latest version of wine from CVS and created a new
.wine directory. Upon running winecfg, there are no letters on any of the
buttons or tabs. After reading the text of bug 5057, I checked
.wine/drive_c/windows/fonts and there are no files.
I copied and pasted all of the font files from the equivalent location in
one of my backups to this directory and I can read all of the buttons again.
Thanks,
Vince
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://www.winehq.org/pipermail/wine-users/attachments/20060622/aad47e67/attachment.htm
On Thu, 2006-06-22 at 19:02 +0800, Vincente Aggrippino wrote:> Is this bug 5057? ... > > I've just installed the latest version of wine from CVS and created a > new .wine directory. Upon running winecfg, there are no letters on > any of the buttons or tabs. After reading the text of bug 5057, I > checked .wine/drive_c/windows/fonts and there are no files.Check that you have a correct fontforge/freetype version (./configure should warn you about it). Regards. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 191 bytes Desc: This is a digitally signed message part Url : http://www.winehq.org/pipermail/wine-users/attachments/20060622/be668b86/attachment.pgp
Vincente Aggrippino <vaggrippino@gmail.com> wrote:> I've just installed the latest version of wine from CVS and created a new > .wine directory. Upon running winecfg, there are no letters on any of the > buttons or tabs. After reading the text of bug 5057, I checked > .wine/drive_c/windows/fonts and there are no files.CVS can be brocken at any point in time. What version of fontforge do you have installed? Daniel
Please keep this on the list.> I know that a CVS version doesn't necessary represent a fully-functional > version. I just wanted to see if my experience was the bug 5057 that was > already reported (Core fonts don't install if they're found on the > host<http://bugs.winehq.org/show_bug.cgi?id=5057>) > or if it was something new.I don't think you are seeing bug #5057.> I have fontforge installed by RPM. configure (actually tools/wineinstall) > did warn me about fontforge. On my first attempt, I didn't have it > installed at all. Now, I see confusing version information reported by rpm > ... > > Version : 0.0 > Release : 0.cvs20050502.2.el4.rf > Vendor : Dries RPM Repository http://dries.ulyssis.org/rpm/ > Build Date : Mon 11 Jul 2005 02:33:09 PM MYT > > So I guess that the packager downloaded fontforge from CVS and built the > RPM. Is this a problem?That is not a problem. But your version may be too old. At least your problem is exactly what happens if your version of fontforge is too old. Daniel
Vincente Aggrippino <vaggrippino@gmail.com> wrote:> I've just downloaded and installed the latest RPM available from > fontforge.sourceforge.net and I can still reproduce the problem.Strange. Actually your screenshot looks exactly like the fontforge issue.> The creator of bug #5057 reports that the problem occurs because he has a > package installed that already includes the MS fonts. It's an unconfirmed > bug. I don't have any package including these fonts, but my > "C:\Windows\Fonts" directory is still empty. I think I may be experiencing > the same issue, but it's not because the fonts are found on the host.I don't have anything in C:\Windows\Fonts either, so that's not the problem.> What do you think?That maybe you found a new bug. It would be helpful if you could verify this with the latest released wine version before opening a bug report, though. Daniel