Author: TomH
[Added to the original trac issue at 8.45am, Monday, 19th August 2013]

All our translations are crowd-sourced using Translatewiki, so if you find something missing you can fix it yourself by going to http://translatewiki.net/wiki/Translating:OpenStreetMap.

We are not able to accept translations other than via Translatewiki.

Author: pyrog[at]laposte.net
[Added to the original trac issue at 9.31am, Monday, 19th August 2013]

Your right, but I can't find the word tomb in Translatewiki.

I understood (but may be i'am wrong) that developper should add a key before other could translate it ?

Could i add a key Osm:Geocoder.search osm nominatim.prefix.historic.tomb/fr myself ?

Author: TomH
[Added to the original trac issue at 9.36am, Monday, 19th August 2013]

Ah right. I assumed as Sarah had only updated that list a few days ago that there wouldn't be anything missing but apparently there was. I've added it now, but it probably won't appear on TW until next weekend.

Author: lonvia
[Added to the original trac issue at 9.45am, Monday, 19th August 2013]

There are still quite a few terms missing because I've only included key/value combinations with a certain usage level. The full list would probably be two or three times the current size. If that is not a problem, I can extend it further.

Author: lonvia
[Added to the original trac issue at 10.13am, Monday, 19th August 2013]

On second thought, the correct general solution to the problem would be to fall back to the class (i.e. key) instead of the type (i.e value) when a class/type combination is not found. The set of classes is fixed while the set of class/type combinations is as infinite as the number of typos in the database.