From: Hubert Chan <hubert@uhoreg.ca>
Subject: Re: UTF-8 in articles
Date: Fri, 07 Mar 2003 13:39:54 -0500 [thread overview]
Message-ID: <87k7fb6ul8.fsf@labatt.uhoreg.ca> (raw)
In-Reply-To: <u4r6fxofr.fsf@hschmi22.userfqdn.rz-online.de> (Frank Schmitt's message of "Fri, 07 Mar 2003 15:04:56 +0100")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 655 bytes --]
>>>>> "Frank" == Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
Frank> spamtrap@koldfront.dk (Adam SjÂøgren) writes:
>> Sometimes people post news-articles that are UTF-8-encoded. My
>> XEmacs/Gnus doesn't display the characters correctly (I get the ugly
>> two-chars-instead-of-one symptom).
Frank> You mean
Frank> ä,Âö,Âü,ÂÃ,Âé,Âè,Âî,Ââ¬
Frank> and such stuff? :-)
Whoa. That's interesting. The first time I looked at the article,
those characters showed up fine. But when I switched to the parent
article, then back, it shows up as \201<A aigu>... . I'm using emacs
CVS as of yesterday.
Hubert
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
parent reply other threads:[~2003-03-07 18:39 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <u4r6fxofr.fsf@hschmi22.userfqdn.rz-online.de>]
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=87k7fb6ul8.fsf@labatt.uhoreg.ca \
--to=hubert@uhoreg.ca \
/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).