-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Separate synonyms from search terms #3
Comments
You are so fast! I have a few concerns:
An example for point 3: |
|
Another thing. This is probably blue-sky. Since the order of synonyms matter and should matter (a more likely synonym should be shown before some weird but possible phrasing), there could be some way to resolve disagreement amongst translators which word is the more used one. For https://github.com/westnordost/tagdictionary I actually wrote two python scripts that would add a comment for each translated word on how many results there were for this word in a google search. This, to give a rough estimation on how well used this word is. So maybe one step towards this kind of thing would be to not use "," to separate the synonyms but a return ("\n"). Using a "#" for example, translators could add comments to each translation. This could be used to mark f.e. the number of results... amenity=atm:
- Geldautomat # found 2200k times
- Bankomat # found 230k times or to make comments on certain words craft=plumber:
- Sanitärbetrieb
- Anlagenmechaniker für Sanitär-, Heizungs- und Klimatechnik # official but awkwardly long job title
- Klempner # factually wrong job title (a Klempner is a tinsmith) but used in colloquial language, only in de-DE |
I didn't realize you could add carriage returns on transifex, but that seems like a good idea. I'll try it. |
Strip whitespace between search terms
Re: openstreetmap/iD#6139
Essentially the idea is that we're putting synonyms into the
terms
property along with other related search words. But if we knew what terms were direct synonyms, and also made them display-ready, then we could improve the preset search experience.The text was updated successfully, but these errors were encountered: