[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lynx-dev] rendering — (0x97)

From: Mouse
Subject: Re: [Lynx-dev] rendering — (0x97)
Date: Mon, 29 Jun 2020 14:43:13 -0400 (EDT)

>> but if they are sending — over the wire, rather than the a byte
>> containing the value 151, the contents encoding wouldn't matter, as
>> entities are interpreted in Unicode,

> What do you mean?  The actual Unicode number is U+2014, or 8212, and
> — is simply cp1252 in disguise.

I think the double-quoted text above is saying that — is defined
to be not "codepoint 151 in the encoding specified by the
Content-Type:" but rather "Unicode codepoint 151".

Is that actually true?  I don't know; I'm not au courant enough with
Web specs to know where to look - I have as little to do with the Web
as I can get away with.

> I hav seen that, and 	, in Microsoft HTML from Word.

That means little.  Just because a Microsoft program generates
something does not mean it's compatible with non-Microsoft software,
and sometimes does not even mean it's compatible with other Microsoft
software, and certainly does not mean it's correct.

For example, I've seen mail generated by Microsoft tools with
codepoints in the 128-159 range, obviously intended to be printable
characters, but labeled as being 8859-1.

/~\ The ASCII                             Mouse
\ / Ribbon Campaign
 X  Against HTML      
/ \ Email!           7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

reply via email to

[Prev in Thread] Current Thread [Next in Thread]