-
Notifications
You must be signed in to change notification settings - Fork 170
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
Incorrect Korean address field translations #1435
Comments
Seeing the same when using Danish. Went to see if new translations from Transifex were included in the 2.31.0 update. They are not and instead a lot of these "Missing en translation" error messages all over. |
Required for openstreetmap/iD#10674, and partially addresses the issue reported in https://github.com/openstreetmap/iD/issues/10739
Required for openstreetmap/iD#10674, and partially addresses the issue reported in https://github.com/openstreetmap/iD/issues/10739
The missing translation bug is fixed with #1433. The translations will be updated with the upcoming release of the tagging-schema dataset (which is independent from the release of the iD codebase). You and expect it in the coming days. |
Is there any place which actually explains what |
|
Then I wonder why isn't it something like |
URL
https://www.openstreetmap.org/edit?way=223418692#map=19/37.567073/126.976577
How to reproduce the issue?
Screenshot(s) or anything else?
See also: #10674
When mapping addresses in Korea using iD Editor (in Korean), the address fields do not match the proper Korean administrative divisions. Each address field should use the standard Korean administrative division term. Currently, the UI shows something like:
addr:province
= '도'addr:city
→ '시·군·자치구' ❌ → "시·군"✅addr:district
→ '구'addr:town
→ 'Missing en translation' ❌ → "읍·면"✅addr:subdistrict
→ '하위 지구' ❌ → "동·리"✅Which deployed environments do you see the issue in?
Released version at openstreetmap.org/edit
What version numbers does this issue effect?
2.31.0
Which browsers are you seeing this problem on?
Chrome
The text was updated successfully, but these errors were encountered: