El mar, 04-06-2013 a las 01:01 +0100, Rupert Swarbrick escribi?:
> Mario Rodriguez <biomates at telefonica.net> writes:
> > It seems the problem was introduced when the file intl.lisp was written
> > for the first time.
> >
> > In any case, function 'describe' speaks in Spanish again when (getenv
> > "LANG") is called before (getenv "LANGUAGE") in the 'or' statement:
> >
> >
> > (defun setlocale (&optional locale)
> > (setf *locale* (or locale
> > (getenv "LANG")
> > (getenv "LC_ALL")
> > (getenv "LC_MESSAGES")
> > (getenv "LANGUAGE")
> > *locale*)))
>
> LANG being last follows at least the Gettext manual [1]. I confess that
> I don't play around with such things much (since I'm lucky and speak
> en_GB but don't mind en_US in moderation...). Why do you think that LANG
> should precede LANGUAGE?
>
> Rupert
>
>
> [1] https://www.gnu.org/software/gettext/manual/html_node/Locale-Environment-Variables.html
After a *fresh* installation of Xubuntu 12.10 I get the following output
from locale:
$ locale
LANG=es_ES.UTF-8
LANGUAGE=es_ES:en
...
After installing Maxima,
(%i1) :lisp (or (intl::getenv "LANGUAGE") (intl::getenv "LANG"))
es_ES:en
(%i1) :lisp (or (intl::getenv "LANG") (intl::getenv "LANGUAGE"))
es_ES.UTF-8
Looking for "LANGUAGE" first, information on codification is lost, and
global variable *maxima-lang-subdir* can't be set to "es.utf8".
In most linux systems around here I get
$ locale
LANG=es_ES.utf8
LANGUAGE=
...
In these cases, I haven't found any problems with the current order,
since LANGUAGE is not defined. That's why I didn't detect the problem
before.
And quoting myself,
"I'm not sure if this change breaks something else."
--
Mario