Opened 16 years ago
Closed 15 years ago
#3494 closed defect (fixed)
shift+d form should be accept coma as well as dots
Reported by: | Bürste | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
shift+d form should be accept coma as well as dots and remove spaces and other not printable signs for itself.
Attachments (0)
Change History (5)
comment:1 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 15 years ago
Resolution: | fixed |
---|---|
Status: | closed → reopened |
@Gubaer
Why? it's normal to split the values via "," in Germany, so if you use it with German translation you have to enter English values. This doesn't make sense.
follow-up: 4 comment:3 by , 15 years ago
Because we everywhere else request values with "." as separator as well?
comment:4 by , 15 years ago
Replying to stoecker:
Because we everywhere else request values with "." as separator as well?
Yes, that's what I was thinking too. And I didn't want to introduce locale specific formatting requests on the fly because what might work for a german user might lead to problems in other locales.
But Bürste has a point. We can be less restrictive on the input format. One step ahead would be to replace parsing with Double.parseDouble by the respective parsing methods in NumberFormat. The later take locale specific formatting rules (i.e. commata as separator in the german locale) into account.
I'm working on it.
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
Fixed in r2531. Except for the request of accepting "," in place of "." too, it doesn't make sense IMHO.