From: Colin Rafferty <craffert@ms.com>
Subject: Re: bbdb, Umlauts, pgnus-0.79 and emacs-20.2
Date: 05 Mar 1999 12:09:35 -0500 [thread overview]
Message-ID: <vgv7lsv3ltc.fsf@ms.com> (raw)
In-Reply-To: "Johannes Weinert"'s message of "05 Mar 1999 16:47:53 +0100"
Johannes Weinert writes:
> Colin Rafferty <craffert@ms.com> writes:
>> If you do have the problem, insert the following text in the *scratch*
>> buffer, and type C-j (control j) after it. Send back the results.
>>
>> (mail-extract-address-components "Max Schäfer <max@plank.org>")
> Well, funny. I put this text via cut-and-paste in the scratch buffer
> and evaluated the expression as desired. The result was:
> ("Max Sch" "max@plank.org")
This means that the problem is with `mail-extract-address-components'
(as you can see). Since the base emacs functionality doesn't work,
there nothing that I can do, other than try to hack around it, which
is not something that I want to do.
You may want to try getting the 20.3 version of mail-extr, and see if
that fixes the problem.
> But, if I startet another emacs (language-environment was not already
> set to "Latin-1", I execute the function in gnus-startup-hook), and
> pasted the text from scratch-buffer to it, a \201 showed up before the
> "ä". If I delete this, then mail-extract-address-components returns
> ("Max Schäfer" "max@plank.org")
> als desired. Otherwise it's the same as above.
I think that emacs-20.2 is screwing with your characters. This
paragraph has been garbled by putting in all those \201 characters.
> Well, I think, I should convince the system administrator to install
> emacs-20.3 (or the bad way: do it for myself - as suggested before).
That seems to be the only fix. I hope that they will do it.
--
Colin
prev parent reply other threads:[~1999-03-05 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-05 13:23 Johannes Weinert
1999-03-05 13:31 ` Lee Willis
1999-03-05 14:53 ` Colin Rafferty
1999-03-05 15:47 ` Johannes Weinert
1999-03-05 17:09 ` Colin Rafferty [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=vgv7lsv3ltc.fsf@ms.com \
--to=craffert@ms.com \
/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).