Closed SomeoneElseOSM closed 7 years ago
Thank you for the hint. I'm not using a translation platform.
Actually, my first contact with translation platforms is the translation of JOSM into German. While 90% of all entries are correct, about 5% are so profoundly wrong that I turned JOSM to English permanently to avoid translation-back-and-forth headaches. Similar problems exists for the texts of osm.org although these are translated on a different platform.
The design problem of these translation platform is that they encourage to translate as quick as possible and discourage to dispute poorly translated items, i.e. the feedback channel doesn't work.
On the other hand, you are not the first one who ran into poor English at Overpass API (DaveF did bring up the issue of "attic" on the talk-gb mailing list, which I refuse to change to avoid the homonym with "historic" as in "open historical map"). I suggest the following:
I'll list all the relevant messages from Overpass API in the wiki and give for each a short context. Where native (only British?) English speakers have a better wording, I'll change to that wording. Please note that, opposed to translation platforms, the wiki should encourage discussions.
Please have a look at http://wiki.openstreetmap.org/wiki/Overpass_API/Wording
@mmd-osm Sorry, I've already used
strip ../cgi-bin/interpreter
strings ../cgi-bin/interpreter | sort | uniq | awk '{ if (length($0) > 12) print; }' | grep -vE '^[0-9][0-9]' | grep -vE '^_' >_
strip ../bin/update_from_dir
strings ../bin/update_from_dir | sort | uniq | awk '{ if (length($0) > 12) print; }' | grep -vE '^[0-9][0-9]' | grep -vE '^_' >>_
cat _ | sort | uniq
as a starting point. But feel free to add the missing lines to the above mentioned wiki page.
I think most of the suggestions (if not all?) on the wiki page are incorporated in the meantime, see https://github.com/drolbr/Overpass-API/commit/e746a7e7a937fc48c9b89e120c0d12c699569918. If there's nothing left to do, let's close this one.
Ping @SomeoneElseOSM : see my comment above. Could you please close this issue? Thanks.
OK
I'd suggest instead "The server is too busy at this time".
For info the full text of the error visible to Overpass turbo is:
"An error occured during the execution of the overpass query! This is what overpass API returned: Error: runtime error: […] Probably the server is overcrowded."
I'm guessing that you might use some translation platform and therefore this issue might best be logged there, but I presume whoever reads this will know what that platform is and will be able to transfer it.