--- On Wed, 26/3/08, Huw Davies <[EMAIL PROTECTED]> wrote: <snipped> > > The error message I got was 'attempt to read or > write protected memory. This is often > > an indication that other memory is corrupt'. > > Hi, > > Could you explain how this breaks .NET2, I can't see > why it should at the moment? > The purpose of the commit is to do what Windows does.
I am not entirely sure myself - all I know is I did a git bisect to find what was the problematic commit, and reverting this particular commit on top of 0.9.58 fixes my problem. My understanding is that the .NET framework uses the windows registry font entries for font look-ups, according to the discussion in http://bugs.winehq.org/show_bug.cgi?id=10467#c2, and it loads fonts directly based on the registry font list and does its own rendering thing with the font files directly; So changing font registry entries break things. ___________________________________________________________ Rise to the challenge for Sport Relief with Yahoo! For Good http://uk.promotions.yahoo.com/forgood/
