Re: puzzling email
> > I ran the html file which was with the message, which appears as an > > attchment, in !Pluto, in NetSurf. The BMP file was also an attachment > > to the message. NetSurf tried to load the file. End of. > OK. But an html message or web page shouldn't contain BMP images. On what basis shouldn't it, please? It's the first time I've seen a BMP file employed in this way. If this is likely to become a more common procedure then surely NetSurf developers would wish to know, yes? > I expect that Internet Explorer might open them, but then it'll handle > URLs containing backslashes. So the problem lies with whatever lump of > shit (Outlook Express?) sent the message. I'm not surprised that > NetSurf barfed at it. > Your correspondent could do with a little education too. Not my problem. It was commercial, thus drawing my attention to the event.
Re: puzzling email
> > I ran the html file which was with the message, which appears as an > > attchment, in !Pluto, in NetSurf. The BMP file was also an attachment > > to the message. NetSurf tried to load the file. End of. > NetSurf has full support for BMP images. Thanks, John. Noted, but NetSurf clearly doesn't like this one. > For us to be able to debug this issue, we need the following: > 1) What filetype does Pluto give the BMP file? (69c) > 2) Please email me the log file from NetSurf's attempt to load the HTML >document in question OK, John I will re-run it and send logfile as requested. > 3) Please email me both the HTML and BMP files in question Wilco. Bit busy at the moment, but will get back to you. > Without _all_ of the above, there is precisely nothing we can do to > help. So you /are/ regarding it as a bug. > Thanks, Ditto! Brian
Not working on woman's hour again
Using version 2.8 (18th Septemeber)and going to the correct location, which worked before, it shows the correct information for a few seconds, then quits. I saved the failure log to my temp directory, I loaded infozip onto the iconbar, I dragged the saved log to it, Infozip changed from "Idle" to "Busy" and then quit with this failure message. Infozip (Zipping) (Taskwindow) zip warning: missing end signature--probably not a zip file (did you zip warning: remember to use binary mode when you transferred it?) zip error: Zip file structure invalid (ADFS::HardDisc4.$.Private.Temp.Log) Michael Bell --
Re: puzzling email
On Mon, 17 Oct 2011 22:19:56 +0100, Richard Porter wrote: > On 17 Oct 2011 Brian Bailey wrote: > > > I ran the html file which was with the message, which appears as an > > attchment, in !Pluto, in NetSurf. The BMP file was also an attachment to > > the message. NetSurf tried to load the file. End of. > > OK. But an html message or web page shouldn't contain BMP images. I > expect that Internet Explorer might open them Actually BMP files are pretty well supported by web browsers - presumably mostly because favicons started out using BMP or ICO files. Wikipedia has a reasonable table although the BMP column is incomplete (NetSurf entry needs filling in!): http://en.wikipedia.org/wiki/Comparison_of_web_browsers#Image_format_support I'd agree that BMP is an odd choice though... > I'm not surprised that NetSurf barfed at it. NetSurf's BMP support is very complete/compatible from what I've seen. It's certainly much better than the rubbish which comes with AmigaOS :) (fortunately easily replaced with libnsbmp code) Chris
puzzling email
> Could it be a .bmp format not currently understood by NetSurf? I just created a test html file that included a BMP image, and made an interesting discovery. If ImageFS2 has its action for BMP files set to Inactive, then NetSurf renders the BMP image on the page. But if ImageFS2 has its action for BMP files set to Active (which is the normal state for most files on my machine) then NetSurf doesn't render the image on the page (unless it has already done so). Regards -- John Harrison Website http://jaharrison.me.uk
Re: puzzling email
On 17 Oct 2011 John-Mark Bell wrote: > NetSurf has full support for BMP images. You're right it does! -- Richard Porterhttp://www.minijem.plus.com/ mailto:r...@minijem.plus.com I don't want a "user experience" - I just want stuff that works.
Re: puzzling email
On 17 Oct 2011 Brian Bailey wrote: > I ran the html file which was with the message, which appears as an > attchment, in !Pluto, in NetSurf. The BMP file was also an attachment to > the message. NetSurf tried to load the file. End of. OK. But an html message or web page shouldn't contain BMP images. I expect that Internet Explorer might open them, but then it'll handle URLs containing backslashes. So the problem lies with whatever lump of shit (Outlook Express?) sent the message. I'm not surprised that NetSurf barfed at it. Your correspondent could do with a little education too. -- Richard Porterhttp://www.minijem.plus.com/ mailto:r...@minijem.plus.com I don't want a "user experience" - I just want stuff that works.
Re: puzzling email
On Mon, 2011-10-17 at 21:56 +0100, Brian Bailey wrote: > I ran the html file which was with the message, which appears as an > attchment, in !Pluto, in NetSurf. The BMP file was also an attachment to > the message. NetSurf tried to load the file. End of. NetSurf has full support for BMP images. For us to be able to debug this issue, we need the following: 1) What filetype does Pluto give the BMP file? 2) Please email me the log file from NetSurf's attempt to load the HTML document in question 3) Please email me both the HTML and BMP files in question Without _all_ of the above, there is precisely nothing we can do to help. Thanks, John-Mark.
Re: puzzling email
> > I just got an email from i4imaging which included a file oleO.bmp which > > NetSurf didn't like very much declaring BadType as it was fetching and > > processing. Said file didn't seem to render. Are bmp file a no go area, > > perhaps? > Could that be because NetSurf is a web browser and isn't designed to > handle Windows BMP files? Why were you trying to load it into NetSurf? > Wouldn't an image processing app like !DPlngScan be more appropriate? No, not really. I ran the html file which was with the message, which appears as an attchment, in !Pluto, in NetSurf. The BMP file was also an attachment to the message. NetSurf tried to load the file. End of.
Re: puzzling email
On 17 Oct 2011 Brian Bailey wrote: > I just got an email from i4imaging which included a file oleO.bmp which > NetSurf didn't like very much declaring BadType as it was fetching and > processing. Said file didn't seem to render. Are bmp file a no go area, > perhaps? Could that be because NetSurf is a web browser and isn't designed to handle Windows BMP files? Why were you trying to load it into NetSurf? Wouldn't an image processing app like !DPlngScan be more appropriate? -- Richard Porterhttp://www.minijem.plus.com/ mailto:r...@minijem.plus.com I don't want a "user experience" - I just want stuff that works.
Re: puzzling email
> > > My BMP file starts with the characters 'BM' as viewed in a text > > > editor. > [Snip] > > If you can't read that file, then either the file is corrupt (easy > > enough with e-mail) or you haven't got ImageFS (or whatever you use) > > set up to convert BMP files. > The OP indicated that NetSurf was being used, therefore presumably its > own routines? Exactly so. My comment was neither a bug report nor 'arm wavy', just noting a characteristic/behaviour of netSurf. I very much appreciate there are limited resources available for NetSurf development, but I am really not in any position to judge whether rendering a BMP file, or not, is of any real significance, thus my comment. I am just glad that development seems to be going so well as it is, IMHO. > Could it be a .bmp format not currently understood by NetSurf? That's what I assumed. > I say this because NS seems quite tolerant to corruption! If you take a > .bmp file and delete a chunk in !Edit (or similar) you will see that > although corrupted, the file will often display in NetSurf when other > programs can complain that the file is corrupt. Brian
Re: puzzling email
In article <5223a930a9j...@jaharrison.me.uk>, John Harrison wrote: > > My BMP file starts with the characters 'BM' as viewed in a text > > editor. [Snip] > If you can't read that file, then either the file is corrupt (easy > enough with e-mail) or you haven't got ImageFS (or whatever you use) > set up to convert BMP files. The OP indicated that NetSurf was being used, therefore presumably its own routines? Could it be a .bmp format not currently understood by NetSurf? I say this because NS seems quite tolerant to corruption! If you take a .bmp file and delete a chunk in !Edit (or similar) you will see that although corrupted, the file will often display in NetSurf when other programs can complain that the file is corrupt. T -- Tim Hill .. www.timil.com
Re: puzzling email
> My BMP file starts with the characters 'BM' as viewed in a text editor. > It does indeed start with 'BM' but I'm mostly sure that it wasn't > generated with DPIngScan. Bound to be from the dark side, really, but it > does beg the question how many other BadFile types might there be > lurking out there? It's not a 'bad file type' any more that DOC is a bad file type. BMP is a Windows Bit MaP file. It's not very efficient, but nor is a SpriteFile. If you can't read that file, then either the file is corrupt (easy enough with e-mail) or you haven't got ImageFS (or whatever you use) set up to convert BMP files. Regards -- John Harrison Website http://jaharrison.me.uk
Re: puzzling email
On Mon, Oct 17, 2011 at 04:10:32PM +0100, Brian Bailey wrote: > John > > > > I just got an email from i4imaging which included a file oleO.bmp which > > > NetSurf didn't like very much declaring BadType as it was fetching and > > > processing. Said file didn't seem to render. Are bmp file a no go area, > > > perhaps? > > > A BMP file made with DPIngScan loads fine, so your file is probably > > faulty - or, as sometimes happens, has the wrong file extension perhaps > > (?). > > > My BMP file starts with the characters 'BM' as viewed in a text editor. > > Thanks for that. It does indeed start with 'BM' but I'm mostly sure that > it wasn't generated with DPIngScan. Bound to be from the dark side, > really, but it does beg the question how many other BadFile types might > there be lurking out there? > > I've had something similar happen before but ignored it! > > Brian > It is most likely that your application has saved the bitmap with a data filetype. NetSurf (correctly) converts the RO data filetype to the application/octet-stream MIME type which will not be considered as anything beyond binary data that cannot be interpreted. Additionally if the bitmap is small you might try opening a bug on the bugtracker and placing it there to be examined as without it no-one can make any sensible determination. And *not* specific to this report, just using it as an opportunity: Please, PLEASE, there are only a very small number of use working on NetSurf. Can users read http://www.chiark.greenend.org.uk/~sgtatham/bugs.html and follow its advice. Also http://catb.org/~esr/faqs/smart-questions.html is worth a read but be aware of the offensive language in that one. We welcome bug reports, however, hand-wavy reports take a disproportionately large amount of time to answer so you run the risk of simply never receiving a reply. -- Regards Vincent
Re: puzzling email
John > > I just got an email from i4imaging which included a file oleO.bmp which > > NetSurf didn't like very much declaring BadType as it was fetching and > > processing. Said file didn't seem to render. Are bmp file a no go area, > > perhaps? > A BMP file made with DPIngScan loads fine, so your file is probably > faulty - or, as sometimes happens, has the wrong file extension perhaps > (?). > My BMP file starts with the characters 'BM' as viewed in a text editor. Thanks for that. It does indeed start with 'BM' but I'm mostly sure that it wasn't generated with DPIngScan. Bound to be from the dark side, really, but it does beg the question how many other BadFile types might there be lurking out there? I've had something similar happen before but ignored it! Brian
Re: puzzling email
In article <5223956cc4bbai...@argonet.co.uk>, Brian Bailey wrote: > I just got an email from i4imaging which included a file oleO.bmp which > NetSurf didn't like very much declaring BadType as it was fetching and > processing. Said file didn't seem to render. Are bmp file a no go area, > perhaps? A BMP file made with DPIngScan loads fine, so your file is probably faulty - or, as sometimes happens, has the wrong file extension perhaps (?). My BMP file starts with the characters 'BM' as viewed in a text editor. John
puzzling email
Hi I just got an email from i4imaging which included a file oleO.bmp which NetSurf didn't like very much declaring BadType as it was fetching and processing. Said file didn't seem to render. Are bmp file a no go area, perhaps? Cheers
