rather than saying the info was wrong, it would be helpful if you say what you fixed. like fixed alignment of the building. 👍
---

Published using OSMCha: https://osmcha.org/changesets/118015609

Thank you very much for pointing out the issue. I would like to rise two points here:

1. If you see the changeset details you would be able to see that I added the name and the wheelchair access tags via an app named StreetComplete which suggested the name and asked if it has wheelchair access so to which I responded accordingly. So for the name there was no way to specify `name` and `name:en` tag.

2. I am not sure if you are aware of the problem or not but text having Unicode character shows problem rendering in the OSM ecosystem and sometime makes the system unusable for the user. In OSM community, the OSM site; where we are talking, is regarded more as an open data source than tradition map utility for daily use. This site shows the Unicode texts perfectly but the wide range of application that people use as their daily driver takes that data from here and faces problem rendering it and the user end up with an unusable system. The link you provided does say that we should follow the convention you proposed but from the edit history it would seem that 'convention' was introduced to the OSM Wiki fairly recently and I suspect it was introduced without considering the use case I mentioned above. Each community fixes its own standard discussing with their fellow community mapper (see example of [India](osm.wiki/WikiProject_India#Naming_in_different_scripts_and_languages)) and to may knowledge I didn't see any discussion about this 'convention' that breaks the usability of user.