wine users - May 2006 - Further to 0.9.8 to 0.9.12 update problems

Hi NG

Well I started with a vanilla install using the SuSE 0.9.12 9.3 rpm as 
previously mentioned. I erased the 0.9.8 version first.

Then ran wineprefixcreate

Then launched winecfg; This is the screen output

http://members.cox.net/bob3bob3/winecfg.png

notepad also had the same kind of output with small/non existant text

Tried installing fonts from the winetools folder I had before, thinking 
the default might be missing. No help..

I am wonderng if "- Several improvements to the font support." found
in
the ANNOUNCE file might be related to the issue..

I note there are no *.fon/*.ttf files in the .wine structure.. I guess 
this is normal given that my working install doesnt have them either. 
Ran SuSEconfig that I guess rebuilds /usr/lib/X11/fonts font database 
etc but no help.

Might I have a wrong font subsituted in there? What font does Windows 
use for its startup in notepad, install screens etc.

Any further ideas please?

Cheers Bob

-- 
This e-mail was scanned with a private,
non-commercial version of AntiVir MailGate.
See http://www.antivir.de for details.

-- 
This e-mail was scanned with a private,
non-commercial version of AntiVir MailGate.
See http://www.antivir.de for details.
-------------- next part --------------
Skipped content of type multipart/signed

Well I had problems with the rpm build of wine 0.9.12 for SUSE 9.1. I
tracked the problem to a faulty patch aplied to the wine source by the
maintainer, I allso noticed that this patch modifies
"wine-0.9.12/dlls/gdi/freetype.c" that comes with the wine source.
My recomendation is that you download the wine source and build wine.
Note beacouse of SUSE specific isues you shuld get the suse source rpm
for your distro and modify the patch (remove the lines that mod
freetype.c).

I have grabbed the source and am building it. I note that during 
configure it complained about the lack of freetytpe or fontforge with 
the warning that the output would look exactly as I described if I didnt 
fix it!

Cheers Bob

ilija01@gmail.com wrote:
> 
> Well I had problems with the rpm build of wine 0.9.12 for SUSE 9.1. I
> tracked the problem to a faulty patch aplied to the wine source by the
> maintainer, I allso noticed that this patch modifies
> "wine-0.9.12/dlls/gdi/freetype.c" that comes with the wine
source.
> My recomendation is that you download the wine source and build wine.
> Note beacouse of SUSE specific isues you shuld get the suse source rpm
> for your distro and modify the patch (remove the lines that mod
> freetype.c).
>

Grrr!

This is more information only.. It appears to be my installation 
specific, possibly in the font area but I havent spent time on it yet.

I built from source after applying the SuSE specific patches, with the 
freetype section removed as suggested. Did the usual remove of old wine 
rpm, ldconfig, SuSEconfig etc beforehand. Tried running wine notepad 
with NO .wine directory thus allowing it to auto create same. The fault 
persisted.

I shd point out that configure had previously complained about the lack 
of freetype and fontforge so I had to install that from the distro first.

I can see myself doing some heavy reading on the diffs between 0.9.8 and 
0.9.12.

Cheers Bob

ilija01@gmail.com wrote:
> My recomendation is that you download the wine source and build wine.
> Note beacouse of SUSE specific isues you shuld get the suse source rpm
> for your distro and modify the patch (remove the lines that mod
> freetype.c).
>

Bob Bob wrote:
> I shd point out that configure had previously complained about the lack 
> of freetype and fontforge so I had to install that from the distro first.
> 
> I can see myself doing some heavy reading on the diffs between 0.9.8 and 
> 0.9.12.
> 
> Cheers Bob
Between 0.9.8 and 0.9.12 the font handling in wine has been overhauled. 
Before it used the wrong but available fonts for defaults. Now it uses 
the correct but hard to build fonts. If you make clean in the wine build 
font folder then then make depend in the root, Then make in the font 
folder to see what errors pop up. There will be some missing glyphs 
warning but that is ok.
Paul

Hi Duane

wine --version
Wine 0.9.12

Yes the fonts are in the right place as you indicated.

This time I used the tools/wineinstall script with the same outcome.

Does wine ONLY look at the share fonts directory for fonts or does it 
(also) look elsewhere? (like in X11 etc) I also wonder where fonts 
downloaded via winetools ends up. (I hope it isnt a issue for my current 
efforts!)

To describe the problem a little better with notepad as an example, the 
typing and menu areas have a small dash (the underscore for the Alt kb 
combination maybe?), graphics are okay as is the title bar text 
(although I assume this is done in X)

I note there is no "fonts-cache" file in the folder that seems to be 
common with other fonts on my disk. I guess this file is something built 
by SuSEconfig?

Interesting to note that the SuSE RPM for 0.9.8 has the fonts in 
/usr/share/fonts/wine/ and the 0.9.12 version in /usr/share/wine/fonts/. 
Building from source as you mentioned puts them in 
/usr/local/share/wine/fonts/ so I quickly tried copying to fonts to the 
other location without effect.

Next step is to go down a version to see where the "fault" starts.

Cheers Bob

Duane Clark wrote:
> Were the fonts built and installed? They should be in 
> /usr/local/share/wine/fonts/ by default.
> 
> And when you execute "wine --version", it is the correct Wine
(you don't
> have an old version lying around)?

Hi Paul

No untoward errors in the font directory make. As stated lots of missing 
glyphs. A section follows;

fontforge -script ../fonts/genttf.ff courier.sfd courier.ttf
Copyright (c) 2000-2004 by George Williams.
  Executable based on sources from 16:07 8-Aug-2004.
FontForge used to be named PfaEdit.
LD_LIBRARY_PATH="../libs/unicode:$LD_LIBRARY_PATH" ../tools/sfnt2fnt 
courier.ttf 13 1255 96 128 8
Missing glyph for char 008a
Missing glyph for char 008c

And of course it creates all the fonts and copies them to the right 
place when install is run..

I am wondering if it really is a font issue?

Tnxs for your help!

Cheers Bob

paul wrote:
> 
> Between 0.9.8 and 0.9.12 the font handling in wine has been overhauled. 
> Before it used the wrong but available fonts for defaults. Now it uses 
> the correct but hard to build fonts. If you make clean in the wine build 
> font folder then then make depend in the root, Then make in the font 
> folder to see what errors pop up. There will be some missing glyphs 
> warning but that is ok.

Hi Duane,

Yes renaming my live .wine folder to something different was done 
earlier on. All my current tests are done on a new .wine created 
whenever I start a W32 pgm (like notepad). I guess it is is conceivable 
that the initial registry/prefix create has gane bad but I havent tried 
to investigate. (Something like an "old" setting that is the same in 
0.9.8. That would have to be a pretty major bug that others should have 
picked up)

Tnxs for the info about the font directories. I would surmise then that 
if it didnt find the *right* ones it would default to something else, 
but not endup blank looking.

I am beginning to wonder whether it is a font problem at all..

I'll stick to it for a few days then email the SuSE maintainer..

Cheers Bob

Duane Clark wrote:
> Looking through your previous emails, I did not see any mention whether 
> you tried moving your current .wine to a temporary name, 
----------
> This location changed fairly recently (a few months ago, as I recall).
> 
>