Speaking of this, I just tried composing a message with NS Communicator
with some interesting characters in it, setting the encoding on the
message to UTF-8.
Examples:
Punctuation: +IBw-What?+IB0gFSAY-Huh+IBk-
Franc sign:+MAA- +IKM-
Infinity sign: +Ih4-
Union & Greeks:+MAA- +A7E- +IsM- +A7I-
Seems to work fine, but who knows what it looks like to an +IBg-old+IBk-
emailer!
Mark
Unicode Discussion wrote:
> Unicode Discussion wrote:
>
> > They have many documents that use "smart quotes" :
> > 0x93+MAAwADAA- 0x201c+MAA- #LEFT DOUBLE QUOTATION MARK
> > 0x94+MAAwADAA- 0x201d+MAA- #RIGHT DOUBLE QUOTATION MARK
> >
> > How to represent these in HTML?
> >
> > 1. Convert to dumb quotes
> > They would be hopping mad if these turned into "dumb" straight
> quotes.
> >
> > This may seem like a reasonable degradation to the average technical
>
> > person, but to customers this is known as "document corruption".
> >
> > 2. Write out as Unicode &# NCRs. (the "correct" way)
> > Unless they are using a Unicode enabled browser, these are ignored
> as
> > noted in this mail stream. On a corporate Intranet it is conceivable
>
> > that you could tell the customer they are required to upgrade their
> > browsers to the newest ones, but they really don't like that kind of
>
> > thing. On the Internet itself, it is obvious that only a fraction of
>
> > people upgrade to newer browsers as you noted. Fortunately this is a
>
> > growing fraction.
> >
> > 3. Write out as “ and ”.
> > Oh look, on all of the customer's machines these display just fine.
> It
> >
> > turns out that virtually all old browsers can understand these
> > characters. There is a small % that does not (e.g. some Unix
> > browsers).
> > This is a problem for the external web site, but all the home users
> > they
> > are trying to reach can read those characters fine.
>
> A 4th possibility would be to use the actual single-byte values from
> CP1252. Strictly speaking, the document would then have to have a
> charset label that corresponds to CP1252. I also think Microsoft
> should
> register "windows-1252" as an alias for
> "ISO-8859-1-Windows-3.1-Latin-1".
>
> Erik van der Poel @ Netscape, but not speaking for Netscape
+MAAwAA-
This archive was generated by hypermail 2.1.2 : Tue Jul 10 2001 - 17:20:35 EDT