Hi
"Samuel W. Heywood" <[EMAIL PROTECTED]> wrote:
SH> With the American ISO that I am using, HTML entity values are not the
SH> same as ascii values.
Sorry ... but I'm not able to understand this sentence ... :)
First of all there is no american ISO ...
ISO stands for _INTERNATIONAL_ Standards Organization
HTML Entities are such things like ä -> parsed as �
SH> This means that if I were to send an email
SH> message written in the Spanish language to a person who uses Arachne
SH> Insight to read his mail, then the message would be perfectly
SH> intelligible to him provided I use the HTML entity values.
???
If you write the mail in a correctly configured insight, than it should be
readable.
If you write it in plain DOS, with the standard codepage 437, it will only
be readable by people who also use plain DOS with cp 437 ...
This is NOT what you want.
If you install the stuff that I zipped up, you will end up with a iso
latin1 in DOS.
So if you can read it in DOS, and send it away with the correct charset
header it should be readable to anybody with an average mail reader (or a
good one :)
SH> If he reads his mail with a program such as Net-Tamer or Barebones
SH> DOS, then I would have to compose the message by use of the ascii
SH> values.
You can't use ascii values for 'special' characters, because there ARE NO
ascii values for these characters !!!
SH> If I were to set up my ISO within DOS to use Latin-1, would the ALT +
SH> NUM characters as viewed from the DOS console be seen the same as
SH> viewed from within Arachne Insight Mail?
it should IMHO ...
SH> In order to achieve universal compatibility we will have to
SH> deconstruct this Tower of Babel.
And if you are dead than you feel no pain .... sorry :)))
but this is impossible ...
SH> I am merely suggesting that everybody should adopt one universal
SH> numbering scheme for all the characters used in all of the world's
SH> languages.
There IS such a scheme ... as I and many others have already written here
... goto http://www.unicode.org
SH> Please examine the characters below from within Insight and also from
SH> within the DOS console. I think we all can agree that this is a big
SH> problem.
Not really ... this is like I put my tape into the cd-player and I couldn't
hear anything.
SH> ALT + NUM, Spanish language characters
SH> from table
SH> http://utopia.knoware.nl/users/schluter/doc/tags/characters.html These
SH> are rendered correctly in Arachne's Insight Mail, but are
SH> incorrect when viewed at the DOS console:
SH> 225 � Corresponds to ascii 160 in DOS
SH> 233 � Corresponds to ascii 130 in DOS
SH> 237 � Corresponds to ascii 161 in DOS
SH> 243 � Corresponds to ascii 162 in DOS
SH> 250 � Corresponds to ascii 163 in DOS
SH> 241 � Corresponds to ascii 164 in DOS
SH> 170 � Corresponds to ascii 166 in DOS
SH> 186 � Corresponds to ascii 167 in DOS
SH> 191 � Corresponds to ascii 168 in DOS
SH> 161 � Corresponds to ascii 173 in DOS
OK ... again there is NO ASCII 160 !!!! (ASCII is 0-127)
But these seem to be correct ISO Latin-1 codes.
At least they display correctly here.
'a,'e, ....
SH> ALT + NUM, Spanish language characters
SH> from ascii chart, the version normally used in the US.
SH> These are viewed correctly from the DOS console, but are incorrect
SH> when viewed in Arachne's Insight Mail.
SH> 160 � Corresponds to HTML entity 225
SH> 130 � Corresponds to HTML entity 233
SH> 161 � Corresponds to HTML entity 237
SH> 162 � Corresponds to HTML entity 243
SH> 163 � Corresponds to HTML entity 250
SH> 164 Corresponds to HTML entity 241
SH> 166 | Corresponds to HTML entity 170
SH> 167 Corresponds to HTML entity 186
SH> 168 " Corresponds to HTML entity 191
SH> 173 - Corresponds to HTML entity 161
Does HTML entity mean codepage 437 to you ???
(The standard codepage for DOS)
PS: These are displayed as garbage.
Sure ... because your message haeder states that you used iso latin 1 ...
but this lines were written with cp437 !!!!!!
It can't be displayed correctly this way!
SH> BTW, I would be curious to know how this message looks to someone who
SH> is reading it with Outlook or Eudora, or any other popular Winblows
SH> program.
OK here the facts:
You state in your header that you used iso latin1.
So every sane Email program (including windows, nextstep, amiga ...)
will display it using an iso latin1 font.
So the 1. part is displayed correctly .... (in every sane mail program)
and the 2. part (written with the standard DOS codepage 437, but wrongly
assumed to be latin1) is displayed incorrectly.
This is not the fault of any mail reader, but a misconfiguration made by
you. (stating you use iso latin1 but you really used cp437 in that part of
the mail)
SH> Sam Heywood
CU, Ricsi
--
Richard Menedetter <[EMAIL PROTECTED]> [ICQ: 7659421] {RSA-PGP Key avail.}
-=> Rainy days and automatic weapons get me down... <=-
