In article <[email protected]>, James Knott <[email protected]> wrote: > Tanstaafl wrote: > > On 2010-03-13 7:23 AM, Daniel Lewis wrote: > > > >> When you save a document for the first time, the Save As window > >> opens. At the bottom near the middle is a check box. It is labeled > >> "Automatic file name extension". This should be checked. Normally, it > >> is, but if you accidentally unchecked it, it will remain unchecked > >> until you save a document and check the box. Just be sure to look at > >> this check box when you save a file for the first time. To correct the > >> files which have this problem, open them in OpenOffice.org and use > >> "Save As". To do this, click File to open the File menu. Click Save > >> As. This time make sure that this check box is checked when you save > >> the file. > >> > > Which begs the question - why is that checkbox even there? All it does > > is cause this problem (our users have been bit by it a lot too)... > > > > > It's a problem in Windows, but not Linux, OS/2 and I expect Mac. Unlike > other operating systems, Windows still relies on the file extension to > determine the file type. Is the rest of the world supposed to be stuck > in the past because Microsoft can't get it's act together?
I know I'm going to regret this, but I'll ask anyway. What exactly is wrong with using an extension to identify a file type? It is a simple, straightforward system that works. Also it does have a couple of advantages, as far as I can see, one being that it makes it immediately obvious from the file name what application is needed to open that file, the other that it makes it possible to use the same file name (eg all relating to one project) on a number of files with different extensions. As far as I can see, there are only three possible ways of identifying a file type. One is to add an extension, one is to embed a coded file type within the file, the third is to rely purely on the structure of the file to identify it. Options two and three both rely on either the OS or an installed application to identify the file which can cause problems if it is either a new file type that the OS hasn't met before, or a file type for which there is no installed application to handle. I should perhaps add three things to deflect some of the flack. Firstly, most of my work is done on an operating system (RISC OS) that uses embedded file types, so I'm totally familiar with the advantages (?) and disadvantages of such a system. Secondly, I use that OS daily under emulation on a Windows XP box which, in my experience, is not particularly unstable (I can't remember the last time it crashed). True Windows is the system that attracts (well it would, wouldn't it) and is vulnerable to viruses, but the risk is small provided appropriate precautions are taken. Thirdly, whatever you say about how good Linux is (and I do have a Linux box, a small netbook which is a pleasure to use), merely reading this list tells me that Linux is not a trouble free environment by any means. It comes across as a computer system for techies with a very steep learning curve. Not for me, I think, nor for anyone else who just wants to turn the computer on and go. I'll get my coat... R. -- Richard Travers [email protected] Truro, Cornwall --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
