Gnus development mailing list
 help / color / mirror / Atom feed
From: Fabrice Popineau <Fabrice.Popineau@supelec.fr>
Subject: gnus no 0.3 and xemacs
Date: Thu, 28 Oct 2004 15:53:12 +0200	[thread overview]
Message-ID: <1xfj6jav.fsf@esemetz.metz.supelec.fr> (raw)


Hi,

I have switched to the latest cvs version and I will post a couple of question
for which I hope I'll get some help. 

The first one is: I'm using a mule/win32 native version of xemacs 21.5. All the
gnus buffers show 'Noconv' as the buffer encoding. My otherwise encoding default
(outside gnus) is MSW-MB (mswindows-multibyte-default). Is that normal?

I also noticed a possibly related interaction by which any names using
iso-latin-1 chars (in my case) in the From: header end up truncated into bbdb:
everything after the first 8 bits char is removed.

Any hint on this ?

Thanks in advance,

-- 
Fabrice Popineau
------------------------
e-mail:       Fabrice.Popineau@supelec.fr  |  The difference between theory 
voice-mail:   +33 (0) 387764715            |  and practice, is that
surface-mail: Supelec, 2 rue E. Belin,     |  theoretically,
	      F-57070 Metz 	           |  there is no difference !




                 reply	other threads:[~2004-10-28 13:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1xfj6jav.fsf@esemetz.metz.supelec.fr \
    --to=fabrice.popineau@supelec.fr \
    /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).