Gnus development mailing list
 help / color / mirror / Atom feed
From: Sviatoslav Reyentenko <rsvato@comset.net>
Cc: ding@gnus.org
Subject: Re: problem with XEmacs and Mule
Date: 22 Oct 2000 14:26:09 +0400	[thread overview]
Message-ID: <m3k8b141fi.fsf@slava.comset.net> (raw)
In-Reply-To: ShengHuo ZHU's message of "Sat, 21 Oct 2000 21:27:20 -0400"

>>>>> "ZSH" == ShengHuo ZHU <zsh@cs.rochester.edu> writes:

    ZSH> You might load a wrong base64.el.  Possibly, it is base64.el in w3
    ZSH> package.  `M-x list-load-path-shadows RET' may help you find out
    ZSH> which one is loaded.

Thanks, the problem was here. It was base64.el from w3 package, but there
was not base64.el in my gnus installation (i got gnus from precompiled
xemacs package -- may be it is bug?)

    ZSH> BTW, is there a builtin base64 in XEmacs 21.1?

There is file base64.c, with some lisp functions like base64-encode-region
and base64-decode-region, but they don't work with second half of ASCII
table. 

    >> I'd prefer to not encode cyrillic headers, and, of course it concern
    >> not only subject but cc and to fields, and when i get messages with
    >> base64-encoded cyrillic fields, gnus don't decode it in summary nor
    >> in article buffer, while it correct work with sending replies,
    >> forwards etc. When gnus used tm there was variable
    >> mime/field-encoding-method-alist but now i don't know how to work
    >> with it :(

    ZSH> Are you looking for mm-body-charset-encoding-alist ?

No, but it seems exactly what i need.

-- 
	Best regards,
 Sviatoslav Reentenko.




      reply	other threads:[~2000-10-22 10:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-17  8:37 Sviatoslav Reyentenko
2000-10-21 14:18 ` ShengHuo ZHU
2000-10-21 22:28   ` Sviatoslav Reyentenko
2000-10-22  1:27     ` ShengHuo ZHU
2000-10-22 10:26       ` Sviatoslav Reyentenko [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=m3k8b141fi.fsf@slava.comset.net \
    --to=rsvato@comset.net \
    --cc=ding@gnus.org \
    /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).