7:28 p.m.
Hello
This problem looks less wired in a way.
I want to translate
Nation-->Nación (spanish)
So first I don't have used
(set-default-coding-systems 'utf-8)
I open a new file I type Nation I run babel but I obtain
Nación
Which looks like UTF-8 buts somehow the *babel* buffer can not deal with
it.
So I thought using
(set-default-coding-systems 'utf-8)
Would solve the issue since it the buffer must display then utf-8
correctly but it does not so I am puzzled.
Most likely the solution is easy, can somebody please enlighten me
again?
thanks
Uwe Brauer
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
4:23 a.m.
Uwe Brauer writes:
So I thought using
(set-default-coding-systems 'utf-8)
Would solve the issue since it the buffer must display then utf-8
correctly but it does not so I am puzzled.
You must re-read the files to get correct display. Did you?
Setting the default coding system changes the priority for reading
and decoding files in the future, but does not affect existing buffer
display because those files have already been decoded.
Setting `buffer-file-coding-system', which people often expect to
change the display, does not work either, for exactly the same
reason. Buffer text is conceptually abstract characters and has *no*
coding systems. Coding systems are applied on input and output, or on
explicit application by a program or at user request.
See also C-h v for
file-coding-system-alist - Alist to decide a coding system to
use for a file I/O operation.
network-coding-system-alist - Alist to decide a coding system to
use for a network I/O operation.
process-coding-system-alist - Alist to decide a coding system to
use for a process I/O operation.
for ways to make this default apply specifically to babel.el buffers.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
9:49 a.m.
>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
Uwe Brauer writes:
> So I thought using
> (set-default-coding-systems 'utf-8)
>
> Would solve the issue since it the buffer must display then utf-8
> correctly but it does not so I am puzzled.
You must re-read the files to get correct display. Did you?
No, how do I suppose to do this, it is a tmp buffer (see below)? Apropos
does not return anything on the issue re read.
The babel (or google) translation service sends the translated word with
UTF-8 coding to a tmp buffer called *babel*.
The relevant lines of code are
(save-excursion
(set-buffer "*babel*")
(babel-mode))
This can be read by GNU emacs, just fine but Xemacs 21.4/5 cannot.
I tried to modify these lines above
(save-excursion
(set-buffer "*babel*")
(set-buffer-file-coding-system 'utf-8 nil)
(set-default-coding-systems 'utf-8)
(babel-mode))
But this does not change.
Setting the default coding system changes the priority for reading
and decoding files in the future, but does not affect existing
buffer display because those files have already been decoded.
I don't understand if I have set
(set-default-coding-systems 'utf-8) [1]
at the startup and _then_ call babel translation which generated a new
buffer I thought this buffer must be decoded correctly (as in GNU emacs)
Setting `buffer-file-coding-system', which people often expect
to
change the display, does not work either, for exactly the same
reason. Buffer text is conceptually abstract characters and has *no*
coding systems. Coding systems are applied on input and output, or on
explicit application by a program or at user request.
Right but I receive an input as a result of the babel translation?!
See also C-h v for
file-coding-system-alist - Alist to decide a coding system to
use for a file I/O operation.
network-coding-system-alist - Alist to decide a coding system to
use for a network I/O operation.
process-coding-system-alist - Alist to decide a coding system to
use for a process I/O operation.
for ways to make this default apply specifically to babel.el buffers.
Well as I said a tmp buffer is generated called *babel* I don't see how
file-coding-system-alist is relevant here. As for the other two I don't
,----
| where PATTERN is a regular expression matching a network service name
| or is a port number to connect to,
`----
know the port
,----
| The format is ((PATTERN . VAL) ...),
| where PATTERN is a regular expression matching a program name,
`----
And I don't know the program name neither.
Uwe
[1] I am still puzzled why having set this coding, and saving a file
explicitly to iso-8859-1 babel does not work, while it does work
when I don't have used this setting and save the file with the same
coding. Is this a BUG?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
10:58 a.m.
Uwe Brauer writes:
>>>>> "Stephen" == Stephen J Turnbull
<stephen(a)xemacs.org> writes:
> Uwe Brauer writes:
>> So I thought using
>> (set-default-coding-systems 'utf-8)
>>
>> Would solve the issue since it the buffer must display then utf-8
>> correctly but it does not so I am puzzled.
> You must re-read the files to get correct display. Did you?
No, how do I suppose to do this, it is a tmp buffer (see below)? Apropos
does not return anything on the issue re read.
I don't know. It depends on the details of how babel.el works, and
I'm not going to have time to look at it this week.
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
11:11 a.m.
>
> > Uwe Brauer writes:
> >> So I thought using
> >> (set-default-coding-systems 'utf-8)
> >>
> >> Would solve the issue since it the buffer must display then utf-8
> >> correctly but it does not so I am puzzled.
>
> > You must re-read the files to get correct display. Did you?
>
> No, how do I suppose to do this, it is a tmp buffer (see below)? Apropos
> does not return anything on the issue re read.
I don't know. It depends on the details of how babel.el works,
and
I'm not going to have time to look at it this week.
Right you are travelling? May somebody else, Aidan :) ? Will come up
with and advice
If not I will come back to you in due time O:-)
Uwe
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
2:07 p.m.
Ar an naoú lá déag de mí na Samhain, scríobh Uwe Brauer:
> I don't know. It depends on the details of how babel.el
works, and
> I'm not going to have time to look at it this week.
Right you are travelling? May somebody else, Aidan :) ? Will come up
with and advice
Try
(setq-default buffer-file-coding-system 'utf-8)
Check that it’s worked by evaluating the following in *scratch*:
(with-temp-buffer
(message "b-f-c-s is %S" buffer-file-coding-system))
If not I will come back to you in due time O:-)
Uwe
--
¿Dónde estará ahora mi sobrino Yoghurtu Nghé, que tuvo que huir
precipitadamente de la aldea por culpa de la escasez de rinocerontes?
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta
6114
days inactive
6115
days old
5 comments
3 participants
participants (3)
-
Aidan Kehoe -
Stephen J. Turnbull -
Uwe Brauer