Modify

Opened 5 years ago

Closed 5 years ago

#19073 closed enhancement (wontfix)

Presets: comma conversion

Reported by: jumat@… Owned by: jumat@…
Priority: normal Milestone:
Component: Core Version:
Keywords: l18n locale decimal number format presets Cc:

Description

Values like widths/heights etc. are regulary used in JOSM to specify certain tags, independently the used unit.
We in continental Europe use a comma instead of a point. E.g. 2,5 and not 2.5.
Is it possible to implement an automatic conversion (depended on the standard language that is choosen in JOSM), so that a user can fill in data as he/she is used to do it and JOSM converts this to the OSM-standard.
Advantage: always correct values displayed in JOSM to which a user is used to and on the other hand correct data in the OSM-database and its usage.

Attachments (0)

Change History (9)

comment:1 by simon04, 5 years ago

Keywords: l18n locale decimal number format added
Owner: changed from team to jumat@…
Status: newneedinfo

implement an automatic conversion

JOSM accepts decimal numbers in a dozens of places throughout the application. Please be more precise, which dialogs/functions lack the mentioned conversion.

comment:2 by skyper, 5 years ago

Type: defectenhancement
  • There is a validator warning with auto-fix option already.
  • JOSM does not use any translation for tags but always displays original data. Why should there be any differences in number format?

Only place I see room for improvements are "display_values" in presets.

comment:3 by anonymous, 5 years ago

Just one examples on values used in tags:
maxheight = 2.5 (m) In case I write 2,5 into this field, which value will be saved in OSM-database? Will it be converted automatically to 2.5?
2; 2,5; 2.5. I've made the experience, that - in case there is no correct conversion - applications, that are OSM-data based - read out only one number. My concern is - in case maxheight is 2.5 (m) - only 2(m) will be read out.
I hope I could specify the issue a bit.

comment:4 by simon04, 5 years ago

Keywords: presets added
Summary: Comma conversionPresets: comma conversion

comment:5 by jumat@…, 5 years ago

I still get an error message when using comma instead of point when I try to upload data.

in reply to:  5 comment:6 by Klumbumbus, 5 years ago

Replying to jumat@…:

I still get an error message when using comma instead of point when I try to upload data.

Thats the intended bahavior. If you use comma instead of point and try to upload the validator warns you, so you can fix it before you upload.

comment:7 by Klumbumbus, 5 years ago

In this case (comma instead of point) there is even the "Fix" button of the validator available for the most used keys.

comment:8 by gaben, 5 years ago

TL;DR He wants the comma -> dot auto-fix on the fly (without interaction) + show dot as comma depending on locale.

comment:9 by stoecker, 5 years ago

Resolution: wontfix
Status: needinfoclosed

As skyper already says. There is no reason to handle this special from all the other tags. JOSMs philospohy was always allow make access to the real data possible.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain jumat@….
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.