[SOLVED] Re: Picasa2- works great, one font issue

[Matthew Mastracci]

Okay - I checked out the latest Wine from CVS and it seems to be fixed.  
I think this patch was the one that fixed it:

revision 1.82
date: 2005/02/25 13:59:22;  author: julliard;  state: Exp;  lines: +9 -9
TANABE Hiroshi <hirokun_dayomon at infoseek.to> wrote:
Remove (buf && !buflen) checking.
Fixed outline rendering with GGO_GRAY?_BITMAP option.
Improved fixed-pitch fonts detection.

Here's some screenshots from the program while running:

http://www.grack.com/news/Picasa2underWine.html

Note that clicking the "email" button in Picasa will crash it - probably 
the MAPI stubs that cause it:

err:mapi:MAPILogon Stub
fixme:seh:EXC_RtlRaiseException call (from 0x53e297) to unimplemented 
function mapi32.dll.MAPISendMail

Thanks,
Matt.

Matthew Mastracci wrote:

> I tried out the latest Picasa2 (picasa2-setup-1884.exe) on a whim 
> against the Wine 20050111 package and it works great.  There don't 
> seem to be any major functionality issues and the app is very 
> responsive - it almost feels like a native gnome app.
>
> The one visual issue with the program is that certain fonts within the 
> program seem to be blitted incorrectly:
>
> http://www.grack.com/news/Picasa2underWine.html
>
> It appears that Picasa 2 might ship with some pre-computed 
> alpha-blended fonts in the form of ".ytf" files in the runtime 
> directory.  When I move these fonts out of the way, all the fonts 
> (including those fonts used to create the 
> Import/Slideshow/Timeline/etc. buttons) within the program appear 
> screwed up like the album-title fonts do when those files are 
> present.  Note that after copying the generated .ytf files from a 
> Windows '98 installation, all of the characters within Picasa are 
> rendered perfectly.
>
> Where might I start looking for the problem?  I think it has something 
> to do with drawing to backbuffer that eventually gets flushed to disk, 
> since copying the cached font files from a standard Windows install 
> seems to fix the problem.  WINEDEBUG=+gdi doesn't yield much, but I 
> think WINEDEBUG=+bitmap or WINEDEBUG=+font is where I'm supposed to be 
> looking.
>
> Matt.
>