On Tue, Nov 2, 2010 at 1:39 PM, Uwe Brauer <oub(a)mat.ucm.es> wrote:
>> Regarding [Bug: 21.5-b29] babel does not work, encoding
problem; "Stephen J. Turnbull" <stephen(a)xemacs.org> adds:
> Uwe Brauer writes:
>> Babel.el allows you to translate online using googles
>> service.
>>
>> While the encoding works fine in 21.4
>> in 21.5 it does not: look at the following
> We've been through this before, I think the last time you tried 21.5.
This is correct.
> You need to set some coding system to utf-8, possibly
> `default-process-coding-system' or `default-network-coding-system', to
> `(utf-8 . utf-8)'.
Well I had
(set-coding-priority-list '(utf-8))
(set-coding-category-system 'utf-8 'utf-8)
Now I added
(setq default-process-coding-system '(utf-8))
(set-coding-priority-list '(utf-8))
(set-coding-category-system 'utf-8 'utf-8)
(setq default-network-coding-system '(utf-8 . utf-8))
But babel still fails.
It would be useful if there was a way to ask "what coding systems were
used for that process that just ran", or some other way of finding out
what is decided without having to do elisp debugging/tracing. It would
be even better if this would also explain how it was decided,
step-by-step. Some kind of toggleable tracing, maybe?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://lists.xemacs.org/mailman/listinfo/xemacs-beta