Roger Oberholtzer said the following on 11/28/2010 12:22 PM:
On Sun, 2010-11-28 at 11:05 -0500, Anton Aylward wrote:
erhaps running from a terminal (which means a shell) will set the environment from ~/.bashrc before starting the application.
Why not try that ?
That is what I do. It was my 'Step 2'.
I meant as an experimental step to differentiate between functionality
The need for a second step is doubtful. I'm sure some KDE developer will argue this is how it should be. But that would be pure nonsense.
I agree. But I also agree that * settings, once set should be 'remembered' not only across further invocation but across sessions, including the start-up of programs at the beginning of sessions (I mean the global environmental settings, not the setting they had when they were previously started recorded and use again) * this should be part of KDE not something you have to set in ~/.xinitrc
Setting the language so it is only used partially is like being partially pregnant. Meaning that is is in the category of things that are either all on or all off. There is no logical between.
Actually it is. The thing is that the ENVIRONMENT is exported unless you change it. My point was that it WAS NOT set in KDE start up, but was set (by the ~/.bashrc) when a shell is started under Konsole. I suspect the same holds with other session managers.
But that won't help with session restore? Or will it? Either way, putting something in ~/.xinitrc that is shared with or calls or sources ~/.bashrc might be more useful and more generic..
It is a more pervasive thing. Take openOffice: KDE shows the ICON on the desktop in the selected locale, but when you start the program, it reverts to English. The locale info is not passed on.
I'm unclear what you mean about "shows the icon" in a locale. And there is also the matter of how OpenOffice is configured. I can run $ LANG=de_DE oowriter and it will come up in English because I have it set to "English" in Menu: Tools -> Options -> Languages In my experience, the command line and config file over-rides the environment; whether the command line over-rides the config file isn't always consistent. I think it should be. But then not all settings can be controlled on the command line.
Linux uses the locale mechanism to control things like language. If KDE is letting you select the desktop language, it must use that mechanism to communicate this information in the standard Linux method. Simple, really.
NOT! Some things like OpenOffice, Firefox, Thunderbird, InkSkape and Gimp also run on other platforms that don't follow those conventions. On top of which, as I say, there are individual config files for applications, and those will over-ride the environment settings, be they from bash or KDE I've pointed how KDE can be invoked with no LANG set in its environment (i.e. nothing in the global xinitrc, nothing in `/.xinitrc) but its children can have LANG set from the ~/.bashrc or other sources. Those sources can be specific to the application and can over-ride the KDE setting. The language database that is compiled and that these programs draw on may be standard, but that's another matter. I don't see any confusion here. Local overrides global. That's how its always been. -- In the beginning was The Word and The Word was Content-type: text/plain -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org