Re: NetSurf RISC OS archive files
On 28/01/2011 13:13, Mike Hobbs wrote: In my opinion&a91 was a bad idea. It would be nice to know how to set mimemap and extensions translations so that all archive types are handled seamlessly but I have not succeeded in doing this. There is then no easy way to distinguish between cross platform compatible zips, and RISC OS only archive formats, if you want to transfer files off the system, so I would not recommend it. Further discussion would be best continued on csa.apps. Cheers -- David J. Ruck email: dr...@druck.org.uk phone: +44(0)7974 108301
Re: NetSurf RISC OS archive files
In message <519ca0651ft...@netsurf-browser.org> you wrote: > In article <519c9f4858joh...@ukgateway.net>, >John Williams wrote: >> I have noticed recently that the NetSurf download for RISC OS varies >> between zip (&a91) and archive (&ddc) between versions. >> So, is the variation of archive type just an accident of convenience for >> members of the team, and are any other users affected practically by this >> inconsistency? > The NetSurf archives are always zip files. Sounds like something on your > system gives them different RISC OS filetypes when they're downloaded. Do > you use different apps to download NetSurf? > Archive (&ddc) is always used for .zip files here. &a91 was introduced some time ago, presumably to distinguish ZIP from other types of archive file. SparkFS knows how to handle &a91 and &ddc (which may be various formats). It defaults to using &a91 when creating zip files. I find the use of &a91 very annoying because depending on where the files are sent/used the filetype may or may not be recognised and when transferring to HostFS or NFS file systems ",a91" may be appended, making them unrecognizable to applications in Linux or Windows. Depending on whether SparkFS has been Filer_Booted the filetype "Zip" may be either &ddc or &a91 so I guess NetSurf is using the textual filetype rather than the hex when saving zip downloads. I don't have a foolproof solution although at various times I've tried to get SparkFS to default to the old &ddc, but it won't cooperate. Usually, I just manually change the &a91 to &ddc before transferring to a foreign file system or sending via email. In my opinion &a91 was a bad idea. It would be nice to know how to set mimemap and extensions translations so that all archive types are handled seamlessly but I have not succeeded in doing this. -- Mike Hobbs
Re: NetSurf RISC OS archive files
In article <448da49c51.pnyo...@pnyoung.ormail.co.uk>, Dr Peter Young wrote: > FWIW (not worth much, probably) I also have a home-made downloader > using wget, which also does backups of previous versions. One line in > this sets the type of the downloaded file to Archive. Would this line > be useful in your setup? I see that mine does the same. What I'm suspecting is that the alias 'archive' is being usurped somewhere, so I've swapped it for '&ddc'. Now awaiting a few new versions to see what transpires. Thanks for your input. John
Re: NetSurf RISC OS archive files
On 28 Jan 2011 John Williams wrote: > In article <519ca0651ft...@netsurf-browser.org>, >Michael Drake wrote: >> Sounds like something on your system gives them different RISC OS >> filetypes when they're downloaded. Do you use different apps to download >> NetSurf? > No, but I do use a home-made auto-downloader which uses CURL and generally > messes about with stuff, checking for new versions etcetera. So I guess > that's what's causing it. I shall look assiduously at that and see what > I've done wrong. FWIW (not worth much, probably) I also have a home-made downloader using wget, which also does backups of previous versions. One line in this sets the type of the downloaded file to Archive. Would this line be useful in your setup? With best wishes, Peter. -- Peter \ / zfc Lu \ Prestbury, Cheltenham, Glos. GL52 and \/ ____ \ England. family / / \ | | |\ | / _ \ http://pnyoung.orpheusweb.co.uk / \__/ \_/ | \| \__/ \__ pnyo...@ormail.co.uk
Re: NetSurf RISC OS archive files
In article <519ca0651ft...@netsurf-browser.org>, Michael Drake wrote: > Sounds like something on your system gives them different RISC OS > filetypes when they're downloaded. Do you use different apps to download > NetSurf? No, but I do use a home-made auto-downloader which uses CURL and generally messes about with stuff, checking for new versions etcetera. So I guess that's what's causing it. I shall look assiduously at that and see what I've done wrong. At a first guess, I'm specifying the filetype by an alias which something else is altering! At least I have an idea when it started, which may help trace the culprit! > Archive (&ddc) is always used for .zip files here. Thanks, and sorry to have bothered you! John
Re: NetSurf RISC OS archive files
In article <519c9f4858joh...@ukgateway.net>, John Williams wrote: > I have noticed recently that the NetSurf download for RISC OS varies > between zip (&a91) and archive (&ddc) between versions. > So, is the variation of archive type just an accident of convenience for > members of the team, and are any other users affected practically by this > inconsistency? The NetSurf archives are always zip files. Sounds like something on your system gives them different RISC OS filetypes when they're downloaded. Do you use different apps to download NetSurf? Archive (&ddc) is always used for .zip files here. -- Michael Drake (tlsa) http://www.netsurf-browser.org/
NetSurf RISC OS archive files
I have noticed recently that the NetSurf download for RISC OS varies between zip (&a91) and archive (&ddc) between versions. Formerly only the archive type was used. The change was first recorded here around r10940. I noticed this because I am in the habit¹ of pinning the latest development version I have to my backdrop from within the archive. If I restart my machine, the icon from within the RISC OS archive file survives the reset and remains on the pinboard, whereas that from within a zip archive does not. I imagine that if I make my pinboard file run later I may be able to solve this problem, though here SparkFS handles both filetypes, which is a bit puzzling. So, is the variation of archive type just an accident of convenience for members of the team, and are any other users affected practically by this inconsistency? John ¹ Old dog syndrome
