Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Peter Dalgaard <p.dalgaard@biostat.ku.dk>
Subject: Re: Those blasted \201 characters
Date: 15 Sep 2006 22:36:54 +0200	[thread overview]
Message-ID: <x2d59wn9y1.fsf@turmalin.kubism.ku.dk> (raw)
In-Reply-To: <v9odthuhnb.fsf@marauder.physik.uni-ulm.de>

Reiner Steib <reinersteib+gmane@imap.cc> writes:

> On Fri, Sep 15 2006, Peter Dalgaard wrote:
> 
> > Every accented character received in mail from certain senders get
> > preceded by the dreaded \201 character. 
> >
> > I think this happened after I killed an ancient line with
> >
> > (standard-display-european 1)
> >
> > to get rid of a UTF8 display problem. It appears to be happening in
> > the nnmail step - i.e. there are no \201's in $MAIL, but they are
> > there in ~/Mail/misc/mail/12345.  
> >
> > I tried reinstating the above line, 
> 
> Please don't.
> 
> > which reintroduced the UTF8 problem, but didn't cure the \201
> > thing... (well, maybe I didn't check on newly arrived mail, need to
> > recheck).
> >
> > Any clues? 
> >
> > [LC_CTYPE=da_DK, other LC items set to C] 
> 
> I'm quite sure that there's something bogus in your setup.  I haven't
> used Gnus 5.9 since ages, but I guess it should not show this problem
> (unless you use standard-display-european).

> Could you upgrade to Gnus 5.10.8 or upgrade to CVS Emacs (some
> distributions offer it as emacs-snapshot or similar) which includes a
> more recent Gnus version and see it the problem persists?

That's awkward since it is my department account and they'd rather not
support things not in SuSE. (The 10.0 running on some other machines
is still only emacs 21.3/gnus 5.9)
 
> Else, can you send me one of the problematic mails as gzipped
> attachment (secret stuff x-ed out)?  If the problem also appears in
> news or mailing list article you could simply give us the Message-Id
> or the URL to an mbox file if available.

I can give it a try. Most likely I can reproduce with mail sent by
myself (which should help with the secrecy thing). The ones that bit
me earlier are gone from $MAIL for obvious reasons. Haven't seen it in
news. 

-- 
   O__  ---- Peter Dalgaard             Øster Farimagsgade 5, Entr.B
  c/ /'_ --- Dept. of Biostatistics     PO Box 2099, 1014 Cph. K
 (*) \(*) -- University of Copenhagen   Denmark          Ph:  (+45) 35327918
~~~~~~~~~~ - (p.dalgaard@biostat.ku.dk)                  FAX: (+45) 35327907

  reply	other threads:[~2006-09-15 20:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-15 15:07 Peter Dalgaard
2006-09-15 18:08 ` Reiner Steib
2006-09-15 20:36   ` Peter Dalgaard [this message]
2006-09-15 20:56     ` Peter Dalgaard
2006-09-15 21:06       ` Peter Dalgaard
2006-09-15 22:51         ` Reiner Steib
2006-09-16  7:51           ` Peter Dalgaard
2006-09-16 11:44             ` Reiner Steib
2006-09-25 12:37               ` Peter Dalgaard

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=x2d59wn9y1.fsf@turmalin.kubism.ku.dk \
    --to=p.dalgaard@biostat.ku.dk \
    /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).