From: Felix Hagemann <fx-2-2002@coop-x.de>
Subject: Subjectlines get extra spaces in summary buffer
Date: Wed, 15 May 2002 12:25:22 +0200 [thread overview]
Message-ID: <uk7q57lnx.fsf@coop-x.de> (raw)
Hi!
I am trying to reply to this article in de.comp.text.tex:
<845c2351.0205150032.427c0b64@posting.google.com>, which has this
subject line:
,----
| Abstand zwischen Kapitelüberschrift und oberer Seitenkante
`----
I edit my followup and send it via C-c C-c. When I later read my own
article, I see that the subject line has an extra space. It looks
like this in the summary buffer (not in the article buffer!):
,----
| Re: Abstand zwischen Kapitelüberschrift und oberer Seitenkante
`----
After some googling I think that the umlaut in the subject might be
the problem. The OP uses:
,----
| Content-Type: text/plain; charset=ISO-8859-1
| Content-Transfer-Encoding: 8bit
`----
which looks ok to me.
Can I do anything to fix this? Is this a problem that anybody sees or
just me (I don't have any other newsreader here)? I use:
,----
| User-Agent: Gnus/5.090005 (Oort Gnus v0.05) Emacs/21.1 (i386-msvc-nt4.0.1381)
`----
Bye,
Felix
next reply other threads:[~2002-05-15 10:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-15 10:25 Felix Hagemann [this message]
2002-05-15 14:57 ` Kai Großjohann
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=uk7q57lnx.fsf@coop-x.de \
--to=fx-2-2002@coop-x.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).