Author: twain
[Added to the original trac issue at 1.33pm, Tuesday, 24th November 2009]

I'm unable to find anywhere where nominatim fails to format responses as expected.

Could you please provide an example of an incorrect response and and indication of what should be done to fix it?

Author: Schusch
[Added to the original trac issue at 1.50pm, Wednesday, 25th November 2009]

ok, here we have an example:

http://nominatim.openstreetmap.org/details.php?place_id=9341487

and a first line:

Abbeyfeale (Point, ~46.4miles, node 52219218, GOTO)

there is no reason for the lack of typgraphy here, it should be ~46.4 miles (with the space).

The SI only specifies something which is usual for typography (before the times of MS-Word etc.). The space is for better readability, just take a look in books which are older than the word processor computer applications - it's not my illusion but a well known rule of typography.

Well and about the "downside" of the possible linebreak:

Without the space we have always a wrong typography, with the space only when the line is broken in the wrong place (which easily could be handled with a non breakable space). I just discovered this old bug report by me with a search ...

(by the way: for most of the people in the world the usage of "miles" is an anachronism and makes the finding quit unhandily (i'm not sure if this exactly applies to what I mean--I don't want to be offending ...))

Author: twain
[Added to the original trac issue at 5.45pm, Saturday, 5th December 2009]

space added.

km / miles switching is not possible since there is no way to store or obtain user preferences within nominatim.

Author: Schusch
[Added to the original trac issue at 3.12pm, Sunday, 6th December 2009]

thanks for the space :-)

(the other one with km/miles is one I won't write a bug for (I just noticed it while researching the space thing) ...)