Bug 421970 - Decimal comma unusable in Manual Price Update in Ivestments
Summary: Decimal comma unusable in Manual Price Update in Ivestments
Status: RESOLVED DUPLICATE of bug 423509
Alias: None
Product: kmymoney
Classification: Applications
Component: general (show other bugs)
Version: 5.0.8
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KMyMoney Devel Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-23 11:52 UTC by shorty365
Modified: 2020-09-16 09:39 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description shorty365 2020-05-23 11:52:19 UTC
SUMMARY
I'm using the Dutch language on mu Kubuntu 20.04 system and KMoney does respect the decimal comma we use in The Netherlands and has so for year. In the version of KMyMoney 5.0.8 in Kubuntu 20.04 in the screen of manual price update of an investment the decimal comma is not accepted and only the decimal point is accepted. 

STEPS TO REPRODUCE
1. On an Investment select "Manual Price Update"
2. Enter a new price with a decimal comma
3. 

OBSERVED RESULT
The decimal comma is ignored and only a decimal point is accepted. Everywhere else in KMyMoney the decimal comma is accepted,

EXPECTED RESULT
Decimal comma is accepted in the new price, just like everywhere else in KMyMoney.

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: Kubuntu 20.04
(available in About System)
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
In previous versions of KMyMoney this was not a problem and the decimal comma was accepted in a manual price update of an investment.
Comment 1 Thomas Baumgart 2020-05-23 14:56:51 UTC
Very strange. I tried to duplicate it here with the German locale (we do use the comma as well as decimal character) and don't have a problem at all.
Comment 2 shorty365 2020-05-24 10:09:04 UTC
It becomes even weirder; Based on the comment of Thomas Baumgart I just checked again and I don't believe it but now I have the comma separator again in the manual price update in an investment. Maybe something to do with updates that ran yesterday.
Ticket may be closed for now. Thanks for your support an continues work!
Comment 3 shorty365 2020-08-22 11:06:24 UTC
Tested again today and I think there is a bug. My locale is Dutch/Netherlands and we use the comma (,) as decimal separator. When I manually update a price of an investment the last known (entered) price is shown correctly. Now I clear the price field so I can enter the current price. For entering the price I use the numeric-keypad on mij keyboard and when I enter the decimal separator, the decimal point on the numpad, it is not translated to an comma. Manually entering a comma solves the problem but this is not what might be expected. Everywhere else in KMymoney the decimal separator is correctly translated to a comma.
Comment 4 dunkiper 2020-08-30 20:50:38 UTC
I have exactly the same problem in Arch Linux, KMyMoney 5.1.0. My Locale is Spanish/Spain.

I've been using Kmymoney for years and never happened to me before that pushing the "." dot in numeric keypad was not recognized as decimal ",". I have to push the "," in the keyboard just next to "M" to enter decimal numbers. I have not this problem in any other program such as calculator. Only in KMyMoney and I think that happened in the last update or two updates before.

I've checked KDE configuration and everything is well configured as Spanish/Spain as always has been.

Thanks
Comment 5 Thomas Baumgart 2020-08-31 08:51:47 UTC
This sounds very much related to bug 423509 for which a fix will be available in 5.1.1
Comment 6 Bug Janitor Service 2020-09-15 04:33:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 7 shorty365 2020-09-16 08:51:45 UTC
Status is on 'needs more info' but I can't find any questions asked to me for this ticket so maybe the status is wrong? Changes status to 'Confirmed' based on reaction from Thomas Baumgart dd 31-08-2020.
Comment 8 dunkiper 2020-09-16 09:38:42 UTC
I think it could be marked as duplicated, because is exactly the same as this bug:

https://bugs.kde.org/show_bug.cgi?id=423509

which is fixed for 5.1.0
Comment 9 dunkiper 2020-09-16 09:39:02 UTC

*** This bug has been marked as a duplicate of bug 423509 ***