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.
Reporter: chriscf [Submitted to the original trac issue database at 12.56pm, Friday, 11th December 2009]
Multiple values for a key are (supposed to be) delimited by semicolons. Where a "name" key has multiple value, the results are ugly. Many people have (incorrectly) applied the approach of mapping for the renderer, resulting in names of the forms "a (b)", "c - d", "e / f" etc. This is particularly problematic in the case of "c - d", since it causes confusion with hyphenated names of the form "g-h".
Where the name is "x;y", rather than rendering the name as "x;y", put in something like a newline or some other separator to make the correct form less ugly, and to discourage format proliferation.
Author: math1985 [Added to the original trac issue at 6.31pm, Tuesday, 10th June 2014]
I think we have no way to do this, because we can't automatically determine whether the ; is part of the name or not. I will therefore close this issue as wontfix.
Reporter: chriscf
[Submitted to the original trac issue database at 12.56pm, Friday, 11th December 2009]
Multiple values for a key are (supposed to be) delimited by semicolons. Where a "name" key has multiple value, the results are ugly. Many people have (incorrectly) applied the approach of mapping for the renderer, resulting in names of the forms "a (b)", "c - d", "e / f" etc. This is particularly problematic in the case of "c - d", since it causes confusion with hyphenated names of the form "g-h".
Where the name is "x;y", rather than rendering the name as "x;y", put in something like a newline or some other separator to make the correct form less ugly, and to discourage format proliferation.
See also #2550 for osmarender
The text was updated successfully, but these errors were encountered: