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.
>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.
>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 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.
//Bernie
http://bernie.arachne.cz/ DOS programs, Star Wars ...
