Historical bug tracker for the Pacman package manager.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
The pacman bug tracker has moved to gitlab:
https://gitlab.archlinux.org/pacman/pacman/-/issues
This tracker remains open for interaction with historical bugs during the transition period. Any new bugs reports will be closed without further action.
FS#11395 - Do not respect KDE environment variables for language
Attached to Project:
Pacman
Opened by Edgar Kalkowski (Erki der Loony) - Thursday, 04 September 2008, 10:38 GMT
Last edited by Dan McGee (toofishes) - Thursday, 04 September 2008, 12:40 GMT
Opened by Edgar Kalkowski (Erki der Loony) - Thursday, 04 September 2008, 10:38 GMT
Last edited by Dan McGee (toofishes) - Thursday, 04 September 2008, 12:40 GMT
|
DetailsSummary and Info:
Pacman (and also makepkg) always used the English language on my system. But since the last update to KDE 4.1.1 they switched to german. All my locale environment variables (LC_*) were set to "en_GB.tuf8". Investigating further I found that there was an additional variable called LANGUAGE which was set to "de". Obviously this one had been introduced by KDE 4.1.1. I don't think pacman should respect a non standard environment variable to choose it's language. It should rather stick to the locale. Steps to Reproduce: Install KDE 4.1.1 on a system which uses an English locale and switch KDE's language to german. |
This task depends upon
Closed by Dan McGee (toofishes)
Thursday, 04 September 2008, 12:40 GMT
Reason for closing: Not a bug
Additional comments about closing: This is a gettext or kde4 issue, this has nothing to do with pacman. We use the same localization techniques as any other application.
Thursday, 04 September 2008, 12:40 GMT
Reason for closing: Not a bug
Additional comments about closing: This is a gettext or kde4 issue, this has nothing to do with pacman. We use the same localization techniques as any other application.
http://bbs.archlinux.org/viewtopic.php?pid=399664#p399664
Could you explain how that is a pacman specific issue?
Every localized apps behaved the same.