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.
Currently has soft hyphens (hex AD) in the value for the tag "name" in "Hat-ton" and "Fos-ton".
The browse page renders the soft hyphen when it breaks the word there but not when it doesn't. I'd expect it to be consistent and always render a character even when the word isn't broken.
To reproduce, view that page and reduce the browser width until the text "(part of way Foston Hatton Hilton Bypass (202232241))" is split at "Hatton". It'll appear as:
Foston Hat-
ton Hilton
i.e. a hyphen character has appeared, but wasn't visible previously, and isn't visible when the word isn't broken.
In this particular case I believe that the fact that a name tag is even present (never mind with hex AD in it) is an error in the data, but apart from that I'd suggest that the browse page ought to render it consistently.
The OSM standard map, FWIW, always seems to render some sort of hyphen there.
The text was updated successfully, but these errors were encountered:
Author: TomH [Added to the original trac issue at 12.05am, Saturday, 16th February 2013]
BTW I do agree that it is completely bogus for the data to contain a soft hyphen there, but you should take that up with user Mauls who appears to have been responsible.
Reporter: SomeoneElse
[Submitted to the original trac issue database at 7.44pm, Friday, 15th February 2013]
This way:
http://www.openstreetmap.org/browse/way/202232243
Currently has soft hyphens (hex AD) in the value for the tag "name" in "Hat-ton" and "Fos-ton".
The browse page renders the soft hyphen when it breaks the word there but not when it doesn't. I'd expect it to be consistent and always render a character even when the word isn't broken.
To reproduce, view that page and reduce the browser width until the text "(part of way Foston Hatton Hilton Bypass (202232241))" is split at "Hatton". It'll appear as:
Foston Hat-
ton Hilton
i.e. a hyphen character has appeared, but wasn't visible previously, and isn't visible when the word isn't broken.
In this particular case I believe that the fact that a name tag is even present (never mind with hex AD in it) is an error in the data, but apart from that I'd suggest that the browse page ought to render it consistently.
The OSM standard map, FWIW, always seems to render some sort of hyphen there.
The text was updated successfully, but these errors were encountered: