Re: txt encoding conversion
From: Robert Hull (Robert_at_please.do-not-spam.me.uk)
Date: Thu, 20 Oct 2005 23:09:36 +0100
> Robert Hull wrote:
>> You are still talking in Win-doze mode. Just because a file ends
>> with the three letters txt does not mean that file will declare it
>> to be ASCII text. Fortunately, the Unix/linux file tools are more
>> intelligent than to believe that the end of a file name imbues a
>> file with magical properties.
> What a great pity.
> I take it you subscribe to the Zappa school of Linux?
> "The problem with the world is stupidity. Not saying there should be
> a capital punishment for stupidity, but why don't we just take the
> safety labels off of everything and let the problem solve itself?"
> Frank Zappa
> Once we have come to terms with the fact our computers are
> spitefully intelligent we will be better equipped to use Linux then?
> I bet you cried when the distros started getting user friendly.
Not sure what you were on when you wrote this, but I'm sure it was not
If I choose to call a file This_file_is_not_the.bbc the last three
letters do not transform the file into the British Broadcasting
If I choose to call a file Phone_Calls that does not make it any less
of a text file than had I subscribed to the Mircosft idea of calling
And If I choose to call an executable "Picture.gif" that does *not*
transform the file into a picture.
The original poster declared (before correcting himself in response to
my post) that running file against any txt file would declare it to
be ASCII text. This is patent rubbish, the fact that a file ends in
txt does not transform it from what it really is into ASCII text.
-- Robert It's not because I am paranoid That the whole world *isn't* against me