On Thu, June 25, 2009 4:30 pm, John-Mark Bell wrote: > On Thu, 2009-06-25 at 16:19 +0100, Dave Lawton wrote: Snip >> Bug 2807419 refers. > > That bug report has nothing to do with the issue raised in this thread. > >> Given the advice about using a dev build or reverting to 2.0, I was >> suggesting that removing the link to 2.1 for RISC OS might be a good >> idea. > > Not really. The number of people affected by the bug reported in this > thread can be counted on the fingers of one hand. For everybody else, > NetSurf 2.1 is a useful upgrade. > > As you say that you're running NetSurf 2.1 on VRPC, then you're not > going to be affected by the bug in question; it only manifests itself on > RISC OS 5, and only if the user is using a font management tool (and > only then in the specific circumstances that Richard mentioned).
Sorry, me jumping to conclusions :( > At some point, we'll release 2.2. However, coordinating a release across > 5+ different platforms isn't something to be done in a hurry so I can > make no concrete statements about when such a release might happen. > No, nor would I expect you to. You and the other guys have done, and do, such sterling work, that I can't praise you highly enough. I remember back to all the negative stuff at the beginning, like how it wasn't possible for anyone to create a browser from scratch. I've removed 2.1 and installed 2.0, this ran for several pages more, before falling in a heap. The logs for 2.1 and 2.0 all have this same line near the end : Fatal signal received: Floating point exception I've pasted the last few lines from each of the logs on to the bug tracker, in case they are meaningful. -- Regards from Dave Lawton
