On Sun, 12 Mar 2000 08:47:04 +0100 (MET), Bernie <[EMAIL PROTECTED]> wrote:
> Sam Heywood wrote:
>> I don't know how you and the other
>> folks on this list who do your emails in various languages can deal with the
>> problem.
> I use the "standard" US "ASCII" table, therefor I never have any problems
> with diffrent languages. (�, � and � are in the US "ASCII" table). The only
> problem that arises is that ex. RAR get som of the "graphical signs" wrong
> - and that doesn't bother me at all.
I don't have a problem with different languages either, as long as both
myself and my correspondent use the same email program and have their systems
set up for the same code pages. I explained this. Within Arachne's Insight
the characters you wrote above are seen OK at my end. When viewed from the
DOS console they are garbage. If your correspondent has his machine set up
for a different code page then the characters you send might look like garbage
on the receiving end regardless of what method your correspondent uses to view
your message.
>> It would be nice to be able to use a single table to be universally
>> compatible with all good email readers.
> You are forced to use Unicode if you need to be able to mail whoever you
> want (assuming the reader has unicode as well). An option would be HTML
> here - it's much more wide spread IMHO then Unicode.
A problem with sending HTML attachments is that people who use a defective
operating system such as Micro$oft Window$ will be afraid to open them for
fear of getting a virus.
>> Assuming we both have normal vision, if I should send a string of
>> characters from my machine to your machine, you should be able to load those
>> characters on your display and see them the same as I do.
> I wouldn't, as of yesterday my monitor thinks most things are supposed to
> be blue :(
> Any ideas on what might be wrong with it are appriciated, I'm still looking
> for the guarantee.
I once had an old VGA monitor that started to lose its color. Then some
other things went wrong with it. I had to replace it. There was no point
in repairing it because I got a replacement at a flea market for $15.00
>> I did not know at the time that I needed to change my code page. I don't
>> even understand why code pages are needed to deal with any situation that
>> does not involve encryption.
> (snip)
>> Characters sent should be
>> the same as characters received and displayed. Why do we need code pages
>> when no encryption or conversion is being made? The exchanging of words
>> ought to be made as easy as the exchanging of music.
> If I where to send you the following code: 01000011 (in binary) you need to
> know how to interpret it - and this is what the code pages do. This code
> will be seen as the same since it's a "C", but something starting with a 1
> instead of a 0 must be handled in some way since these aren't standard.
I understand that. That is why we need standardization and compatibility.
You don't put a descramber on your telephone in order to try to understand
a caller who speaks to you in some language other than the one you
normally use at home. Why should you have to install a code page on your
computer to view a written message the same way as your correspondent wrote
it? It should not matter what language it is written in. Anything that
gets transmitted in the clear should appear on the receiving end the same
way as it looked on the sending end. If this is not happening, then there
is a problem.
Sam Heywood
-- This mail was written by user of Arachne, the Ultimate Internet Client
