Bugzilla Bug 771

When writing a perl script in abiword i choose to save the file as type "all
files" and name it with the pl extension. When i open the document again is has
converted the script into an html format.

Currently, if you choose "Automatically Detected," which is presumably what
this
person meant by "all files" and use an extension that AbiWord does not
recognize
(such as .pl) AbiWord assumes that you are creating an AbiWord document (which
is probably what the reporter mistook for HTML).  While for .pl we should
probably default to txt, I'm not sure if this a generally solvable problem.  We
can't have a list of every possible extension, and I think that an AbiWord
default value is good, because otherwise it would be harder to create documents
with a "." in the name - violating the Just Work principle.  For example, if
you
have automatically detected (the default), and type in the name abi.word, you
presumably want the document to be in .abw format, and to have a .abw
extension.

It is fundamentally wrong to use file extensions for anything other than a last
resort. I don't care about the brain-deadness of Win32, AbiWord is a cross
platform word proccessor and shouldn't function at the lowest common
denominator.

I've finally fixed this on UNIX. On Win32, it's none of my business :). I
consider MS's use of filename extensions to determine file type to be a bug, so
I am leaving this open. I think it is consistant, but horribly confusing to
always append .abw if the code is going to append .abw at all. If the code only
appended .abw if there was no filename extension in the filename the user gave,
that would be horribly inconsistant. I don't think most people will agree with
me, but that's the way I view it. The question is whether the windows frontend
people want to keep it like it is now or move to a more consistant behavior. But
I don't want to get involved with that descision :)

Verified. This works on long as you choose save as file type of text.