On 30 March 2016 12:34:45 BST, Jim Nagel <jim(a)archivemag.co.uk> wrote:
>Chris Young wrote on 30 Mar:
>> On 30 March 2016 00:20:52 BST, Jim Nagel <netsurf(a)abbeypress.co.uk>
>>>What is it about the formatting of my local newspaper's web pages?
>>>Netsurf shows the main column of text so narrow that every line
>>>requires horizontal scrolling. Typical example:
>> Is it the same as this?
>Yes, seems to be same. I note that Michael Drake (of the Netsurf
>team) replied to your post at 9:01 this morning.
>I might be jumping to conclusions from his rather cryptic reply, but
>I'm guessing that my local paper and yours both use Media Queries
>software to generate web pages. Results certainly look alike!
>By the way, did you mean to reply to me privately rather than to the
I did a "reply all", should have gone to both. Replying to this to ensure the trail is all on the list.
---------- Forwarded message ----------
From: Renchen.Sun <sunrenchen(a)gmail.com>
Date: Wed, Mar 16, 2016 at 10:41 AM
Subject: Bug report for libnsbmp
Not sure if it's the correct email address to talk about this. I use
libnsbmp lib in my project and realize that it crashes on decoding a bmp
file as attached in this email.
Please take a look and fix it if possible. This bimap has rle-8 encoding
and it seems like libnsbmp has out-of-bound access to the memory.
[image: Inline image 1]
Attached is an updated RISC OS !Run file for your consideration.
The checks for 5 of the modules that are distributed with NS are
out of date. Rather than pointing failures at dead links, we
should get the user to update the computer's !System.
Bearing in mind a recent user's mishap, I've worded it so as to
try to head off such activity... anyway, read it and you'll see,
but if anyone can think of less clumsy wording, I'll happily
Receive Notifications of Incoming Messages
Easily monitor multiple email accounts & access them with a click.
Visit http://www.inbox.com/notifier and check it out!
So the 3.4 release was a bit of a lemon and due to lack of testing
appears to have been non functional on most supported platforms
Because of this I will be aiming for a 3.5 release on 12th March 2016.
Please can all front end maintainers ensure they are confident with
the state of their implementations before this date.
The toolchains have been updated for this release to include the
recent openssl critical fixes, however this has resulted in the amiga
frontendusing a new toolchain for this release
Can the amiga maintainers please ensure this toolchain change was what
they wanted and let us know if we need to back it out as soon as
One final plea. Making a release is a lot of work and generally
devolves to me, there is a wiki page for the release  can other
mainatiners add anything they are aware of and help get it fixed so
this release is not another complete stuff up and I can actually
announce this one!