Do not localize coordinate in info panel

[HolgerJeromin]

IMO the whole use of the structured coordinate in the info pane is to reuse in search or wikipedia.

But the German number format "51,8852685, 8,478078" is not parsable with its three comma.
ref #4672

[manfredbrandl]

Parsing the info panel might not be optimal, maybe there is a better alternative. What is the use case?

[bhousel]

Ah this makes sense that people expect the coordinates to be copy-pastable into other systems.
@1ec5 does this sound ok?

[manfredbrandl]

I see. What if we omit the comma between latitude and longitude?

[1ec5]

I always thought of the panel as being populated with human-readable text as opposed to machine-readable text. I’ve used some software (particularly on the Mac) that expects localized number input even for coordinates, but it’s true that this behavior is rare on the Web.

I’m not really opposed to unlocalizing this particular label, since the degree-minute-second label is still localized. On the other hand, if we figure out how to allow localized coordinates as input in the search bar, would it be confusing if this panel used unlocalized numbers?

[bhousel]

Ok I ended up unlocalizing the decimalCoordinatePair function.
I don't think anybody would be likely to be confused by the output, which is my main concern.

We can revisit later if people want to.
(For example, removing the comma from the German translation on Transifex would also be an equally ok solution).