On Thu, 2009-06-25 at 16:19 +0100, Dave Lawton wrote: > On Thu, June 25, 2009 1:45 pm, John-Mark Bell wrote: > > On Thu, 2009-06-25 at 13:39 +0100, Dave Lawton wrote: > >> On Thu, June 25, 2009 1:18 pm, John-Mark Bell wrote: > >> > On Thu, 2009-06-25 at 12:23 +0100, Dave Lawton wrote: > >> > > >> >> Ah, that explains the issue I had that I logged the bug for. > >> >> I'll go and close it. > >> >> Perhaps reverting the link to 2.0 would be a good idea ? > >> > > >> > What link, where? > >> > > >> http://www.netsurf-browser.org/downloads/releases/netsurf-2.1.zip > >> > >> Starting at the home page. > > > > You did scroll down the downloads page to find the links to all previous > > releases, right? > > > Yes :^)) > I have a V2.0 CD (Wakefield), but I decided to install 2.1 since I'd > rebuilt the laptop with VRPC-Adjust on. > > 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). 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. John.
