From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Strange coding bug.
Date: Wed, 27 Jun 2001 11:37:23 +0200 [thread overview]
Message-ID: <vafg0cmw9f0.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <vaf8zifa1kk.fsf@lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 26 Jun 2001 14:05:31 +0200")
On Tue, 26 Jun 2001, Kai Großjohann wrote:
> Note the word "oeuvre" in Rolf's posting. It displays properly with
> the ligature. I used Gnus to create a followup to Rolf's posting,
> and in the followup, the word "oeuvre" is b0rked.
>
> What's wrong?
I wonder, maybe Mule-UCS and the UCS support in Emacs 21 step on each
other's toes?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2001-06-27 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-26 12:05 Kai Großjohann
2001-06-27 9:37 ` Kai Großjohann [this message]
2001-06-29 9:48 ` what's wrong with viewing multipart messages in current gnus? (was: Strange coding bug.) Vladimir Volovich
2001-06-29 19:16 ` Simon Josefsson
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=vafg0cmw9f0.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).