Version: (using KDE 4.3.0) OS: Linux Installed from: Fedora RPMs When setting locale preferences, there is the possibility to choose the currency symbol and it's position before or after the number. But it always gets separated with normal space, no chance to change this. This behaviour is wrong e.g. for * the pound sign - 'In English-language use, the pound sign is placed before the number (i.e. "£12,000" and not "12,000£"), and separated from the following number by no space or a thin space.' (http://www.answers.com/topic/pound-sign) * the shekel sign - 'It is either not separated from the preceding number, or is separated only by a thin space.' (http://en.wikipedia.org/wiki/Shekel_sign)
It should be added the space by default if this is the rule. Adding another configuration means add extra confusion to users.
(In reply to comment #1) > It should be added the space by default if this is the rule. Adding another > configuration means add extra confusion to users. the catch is that the rules may differ, they may be a subject to personal taste - see the links above, you may choose to use thin space or no space (but using normal space, as KDE currently does, is wrong) so, if KDE allows to reconfigure the other things (like the currency symbol or thousands separator) to diverge from the default of the given country, I don't see adding one more option as an "extra confusion"
Assign to kdelibs as this would need to be supported in KLocale. This option is not supported in the POSIX standard locales, so not in Linux or OSX, but Windows does support it. I'll have a think about it.
(In reply to comment #3) > Assign to kdelibs as this would need to be supported in KLocale. This option > is not supported in the POSIX standard locales, so not in Linux or OSX, but > Windows does support it. I'll have a think about it. I don't want to compete with Windows or whatever, I just want KDE to support a bit nicer output, please :-)
Hi, kdelibs (version 4 and earlier) is no longer maintained since a few years. KDE Frameworks 5 or 6 might already have implemented this wish. If not, please re-open against the matching framework if feasible or against the application that shows the issue. We then can still dispatch it to the right Bugzilla product or component. Greetings Christoph Cullmann