From: Alf-Ivar Holm <affi@osc.no>
Subject: Re: Expire by moving
Date: 05 Apr 2000 09:56:54 +0200 [thread overview]
Message-ID: <r4u2hhugjd.fsf@serum.osc.no> (raw)
In-Reply-To: <87u2hlvte0.fsf@tea.thpoon.com>
Arcady Genkin <a.genkin@utoronto.ca> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Groъjohann) writes:
^
Hmmm, Kai's "double s", encoded in iso-8859-1 in the From field, was
not special handled in Arcady's reply, which was posted in koi8-r (and
therefore turned up as a cyrillic "hard sign"). Why did this happen?
Should the above line be in a iso-8859-1 part?
Affi
next prev parent reply other threads:[~2000-04-05 7:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-01 17:38 Arcady Genkin
2000-04-01 19:28 ` Kai Großjohann
2000-04-02 7:44 ` Arcady Genkin
2000-04-03 7:39 ` Kai Großjohann
2000-04-05 7:56 ` Alf-Ivar Holm [this message]
2000-04-03 2:33 ` Andrew Hobson
2000-04-03 7:15 ` Hrvoje Niksic
2000-04-20 0:49 ` Lars Magne Ingebrigtsen
2000-04-20 1:05 ` Daniel Pittman
2000-04-20 11:23 ` Hrvoje Niksic
2000-04-20 12:59 ` Lars Magne Ingebrigtsen
2000-05-02 8:35 ` Arcady Genkin
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=r4u2hhugjd.fsf@serum.osc.no \
--to=affi@osc.no \
/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).