From: Mike Ayers (firstname.lastname@example.org)
Date: Mon May 24 2004 - 18:35:20 CDT
> From: email@example.com [mailto:firstname.lastname@example.org]On
> Behalf Of Philippe Verdy
> Sent: Monday, May 24, 2004 3:28 PM
> Peter Constable wrote:
> > Hebrew MCS/ASCII MCS/Unicode
> > literal code unit literal UTF-8
> > ------------------------------------------------
> > alef ) 0x29 ) 0x29
> > bet B 0x42 B 0x42
> > gimel G 0x47 G 0x47
> > ...
> > To encode any different from this in Unicode to support MCW
> > texts would have been fairly bad news for the people that use
> > it.
> Is it a joke? UTF-8 designates Unicode codepoints refering to
> Unicode abstract characters with all their semantic (including
> the character name and properties).
> This table looks like a tweak. Or it is not correctly explained here:
> what is MCS and MCW above?
> You can't say that the tableabove is ASCII not either Unicode.
> It's only a separate legacy 7-bit encoding.. which is probably
> not widely interoperable because unimplemented or not documented
> in the same common places as where ASCII and Unicode are defined.
The table describes how the MCW code sits atop ASCII (and therefore
Unicode). MCW operates by defining ASCII characters to represent Hebrew
(et. al.) characters and marks. Many such codes exist, dating from the "8
bit dirty" days of email, when only ASCII codes were sure to go cleanly
through email (and newsgroups, IIRC). Another such code is VISCII for
This archive was generated by hypermail 2.1.5 : Mon May 24 2004 - 18:36:11 CDT