You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
these objects are not numerous, other names are rendered correctly; mapnik renders these names correctly; deleting and then re-adding name (to ensure there're no strange symbols) doesn't affect the problem.
The nature of corruption is that utf-8 string containing name is converted from iso8859-1 to utf-8, thus
" "
becomes
" "
and that's what is rendered on map.
The text was updated successfully, but these errors were encountered:
Author: osm[at]petschge.de [Added to the original trac issue at 2.09pm, Wednesday, 9th June 2010]
This happened due to the change in multipolygon handling in r21278. Bascially the copying of tags from ways to relations is not UTF-8 safe. Finding this did cost me several days of hard work. There are two fixes for this: Tag the relation instead of the way, or wait till I submit the patch to osmarender.
I do have a working patch but that makes the code look quite horrible. I'll try to come up with a nicer way or applied the ugly patch if it takes too long.
Reporter: AMDmi3
[Submitted to the original trac issue database at 7.27am, Wednesday, 2nd June 2010]
Some objects with russian names are rendered with broken unicode in osmarender.
Examples (see in osmarender):
http://www.openstreetmap.org/browse/way/23456790
http://www.openstreetmap.org/browse/way/42239344
http://www.openstreetmap.org/browse/way/44142114
these objects are not numerous, other names are rendered correctly; mapnik renders these names correctly; deleting and then re-adding name (to ensure there're no strange symbols) doesn't affect the problem.
The nature of corruption is that utf-8 string containing name is converted from iso8859-1 to utf-8, thus
" "
becomes
" "
and that's what is rendered on map.
The text was updated successfully, but these errors were encountered: