Ar an t-aonú lá is triochad de mí Iúil, scríobh Mike FABIAN:
[...] Please try this:
(setenv "LANG" "ja_JP.UTF-8")
That is bad, ‘set-language-environment’ should not change the value of
Well, LANG does determine what encoding subprocesses believe that data
passed to them from XEmacs is in, so there is a decent argument for XEmacs
to set it if it knows it’s going to be passing data in that encoding.
When I start my XEmacs in ja_JP.UTF-8 locale, I want subprocesses
started from XEmacs also use ja_JP.UTF-8 locale. But after
(set-language-environment "Japanese") subprocesses are suddenly
started in ja_JP.eucJP locale, which causes problems.
But changing from a xx_YY.UTF-8 locale to a locale with a non-UTF-8
encoding is just broken. It will cause problems for external programs
called from XEmacs.
Right. This has changed since you wrote your site-start.el; the current
situation is that when you start XEmacs in a ja_JP.UTF-8 locale like so:
env -i LANG=ja_JP.UTF-8 TERM=xterm ./xemacs -vanilla
the language environment information is initialised to:
=> "Japanese (UTF-8)"
(assq 'native-coding-system (assoc current-language-environment
=> (native-coding-system . utf-8)
By the way, I reported this problem already some time ago, in
2004 (Message-ID: <s3tllmsmzym.fsf(a)magellan.suse.de>). But I cannot
find this message in the archive, it is in my outgoing mail archive
but it may not have reached the xemacs-beta list for whatever reason.
My local archive goes back to November 2004, so I don’t have it either. It
may well be that the work I did was in reaction to it, though.
On the quay of the little Black Sea port, where the rescued pair came once
more into contact with civilization, Dobrinton was bitten by a dog which was
assumed to be mad, though it may only have been indiscriminating. (Saki)
XEmacs-Beta mailing list