In message <519ca0651ft...@netsurf-browser.org> you wrote: > In article <519c9f4858joh...@ukgateway.net>, > John Williams <joh...@ukgateway.net> 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
