Version: (using 4.1.3 (KDE 4.1.3), MS Visual Studio 2005 SP1) Compiler: cl.exe OS: Microsoft Windows (i686) release 5.1 (XP Professional) I recently installed the latest version of KDE for Windows (4.1.3) and I was disappointed to see I did not get to choose language. My Windows XP is installed in English even though I am located in Sweden - yet my KDE apps defaulted to Swedish. I've tried to find a way to change this, looking for kcontrol or general system settings, with no success. KDE on Windows should definitely let you choose regional settings - or at least match the Windows installation. In short it's a bug that KDE defaults to your actual location instead of matching your current OS.
systemsettings should be available now in kdebase-apps package. There you should be able to change your preferred language. Other changes have to be discussed.
I've had some discussions about this area on the kde-core-devel list. The general consensus is that KLocale should default all settings to the host desktop (Windows/OSX/Gnome/KDE/etc) where these exist, and only use the KDE settings where they don't. So use the desktop language, country, number formats, calendar system, etc. This would be done through pluggable KLocalePrivate backends for Win/OSX/etc using QLocale where possible. The systemsettings locale kcm would also be modified to disable setting/changing the KDE settings based on what each desktop already provides, but with a global override in case the user does want to use KDE settings anyway. My plan was to start working on this for the 4.5 release, but in 4.4 I have already started a process to implement missing locale features that other desktops support that we don't (e.g. Currency Code, number decimal places, etc). I have also been looking at using QLocale in 4.4 to provide a more intelligent default KDE Language and Locale when users first install/run KDE just as the OP requests above, but it must be noted that there could still be inconsistencies in formats, etc.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.