From: Toby Speight <streapadair@gmx.net>
Subject: Re: Strange `UTF-8'?
Date: 08 Aug 2000 11:01:59 +0100 [thread overview]
Message-ID: <87g0ogxe94.fsf@delivery.cam.eu.citrix.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 8 Aug 2000 11:38:38 +0200"
0> In article <vaf4s4wt7mp.fsf@lucy.cs.uni-dortmund.de>,
0> Kai Großjohann <URL:mailto:Kai.Grossjohann@CS.Uni-Dortmund.DE> ("Kai") wrote:
Kai> I received a message which was labeled charset=UTF-8, but my name was
Kai> all wrong. I then used Mule-UCS to create a UTF-8 file with my name
Kai> in it, ran `less' on it, and got this output:
Kai>
Kai> Gro<C3><9F>johann
Decoding C39F gives 3<<6 + 1F == DF == ß
So that looks right to me.
Kai> Running `less' on the message file was different:
Kai>
Kai> Gro<C3><83>Yjohann
C383 => u-00C3 == Ã
And the Y (u-0059) is completely spurious. (Remember, in UTF-8, all
US-ASCII characters stand for themselves - C0-FF are initial bytes,
and 80-BF are continuation bytes).
Kai> What is happening here? Do the two encodings mean the same thing (but
Kai> Mule-UCS does not know that), or is the second one bogus? Why is it
Kai> bogus?
The second one is wrong (but not bogus in the sense of broken - it
just represents something different from the intent). I'm not sure
how it got like that. It looks like it's been double encoded: the
leading C3 has been re-encoded as C383, and 9F, not being in Unicode
has gone very random. Just a guess, though.
Kai> The message was created with:
Kai>
Kai> X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.14-15mdksecure i686)
next prev parent reply other threads:[~2000-08-08 10:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-08 9:38 Kai Großjohann
2000-08-08 10:01 ` Toby Speight [this message]
2000-08-08 10:44 ` Kai Großjohann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87g0ogxe94.fsf@delivery.cam.eu.citrix.com \
--to=streapadair@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).