Re: problem with XEmacs and Mule

[ShengHuo ZHU <zsh@cs.rochester.edu>]

Sviatoslav Reyentenko <rsvato@comset.net> writes:

> Here is error message (this is for russian equivalent of 'test'):
> 
> Wrong number of arguments: #<compiled-function (start end) "...(496)"
> [message "Encoding base64..." nil 0 base64-alphabet inputpos alphabet bits
> cols counter work-buffer ((byte-code "<byte code that can't be send>" [work-buffer kill-buffer]
> 2)) generate-new-buffer " *base64-work*" buffer-disable-undo
> base64-encoder-program apply base64-run-command-on-region start end
> base64-encoder-switches status t error "%s" char-int 3 base64-insert-char
> lsh -18 1 logand -12 63 -6 4 72 ?\n 8 16 ?\= 2 markerp make-marker
> insert-buffer-substring "Encoding base64... done"] 8 nil "r">, 3 
> 
> so, it try to encode as base64, right?

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

BTW, is there a builtin base64 in XEmacs 21.1?

> 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 :(

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

ShengHuo