![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 27/06/2020 23.37, Dave Howorth wrote:
On Sat, 27 Jun 2020 20:25:41 +0200 "Carlos E. R." <> wrote:
On 27/06/2020 17.55, Dave Howorth wrote:
On Sat, 27 Jun 2020 16:07:34 +0100 Dave Howorth <> wrote:
On Sat, 27 Jun 2020 14:03:40 +0200 "Carlos E. R." <> wrote:
On 27/06/2020 13.49, Andrei Borzenkov wrote:
27.06.2020 11:31, Carlos E. R. пишет:
I tried "LANGUAGE=fr_ES.UTF-8:en vlc" and got the program in French. I have it set to "es_ES.UTF-8". It works.
cer@Telcontar:~> LANGUAGE=en:es uptime 20:22:39 arriba 2 días 9:47, 1 usuario, carga promedio: 0,22, 0,32, 0,30 cer@Telcontar:~>
It is using the "es" /locale/, however it interprets that.
Yeah, well there are lots of es* locales, including es itself, which includes a lot more than en by itself does.
Good :-)
I don't think it's good at all. I think it's so complicated that we can't even figure out what it is we're trying to bug report.
It's clear that different programs behave differently in identical circumstances, which as a user I find unacceptable, but I don't know enough (anything?) about the politics to know what is reasonable. Fortunately English is my native language, so I don't generally suffer too much from the consequences. And I don't try to operate multilingual machines.
How "LANGUAGE=..." works is very clear, there is no bug there. It works. No bug there. As far as I can see I can set it up to get the exact results I may want. The bug or missing feature is in how KDE allows or does not allow users to set that variable up. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)