From: Frank Schmitt <usereplyto@Frank-Schmitt.net>
Subject: Re: \201 gone again?
Date: Wed, 19 Feb 2003 21:45:28 +0100 [thread overview]
Message-ID: <ulm0cuhhz.fsf@hschmi22.userfqdn.rz-online.de> (raw)
In-Reply-To: <84el64jcne.fsf@lucy.is.informatik.uni-duisburg.de>
kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
> It seems that there was a fix for the \201 bug today or yesterday.
> Or am I dreaming?
Yes, see emacs-devel, there was a problem with mutibyte characters in
Emacs AFAIK. This seems to be the relevant change in Emacs which made
them disappear again:
2003-02-17 Kenichi Handa <handa@m17n.org>
* fns.c (string_to_multibyte): Always return a multibyte string.
--
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.
prev parent reply other threads:[~2003-02-19 20:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 19:25 Kai Großjohann
2003-02-19 20:38 ` Henrik Enberg
2003-02-19 20:43 ` Reiner Steib
2003-02-20 9:59 ` Kai Großjohann
2003-02-19 20:45 ` Frank Schmitt [this message]
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=ulm0cuhhz.fsf@hschmi22.userfqdn.rz-online.de \
--to=usereplyto@frank-schmitt.net \
--cc=replies@Frank-Schmitt.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).