On 01/31/2018 08:09 PM, Matej Lieskovský wrote:
> @Marc:
> Nominatim handles nbsp well.
> Renderers seem to either ignore it or make use of it.
> Most editors seem to handle it well, but whitespace highlighting would
> be welcome.
> Overpass... theoretically, it is doing exactly what it should
On Wed, Jan 31, 2018 at 6:49 PM, marc marc
wrote:
> I remain convinced that spelling rules have no place in osm tags
> even if it would be convenient.
>
They are not spelling rules. And your comment implies that people
shouldn't try to spell names
correctly. If
@Marc:
Nominatim handles nbsp well.
Renderers seem to either ignore it or make use of it.
Most editors seem to handle it well, but whitespace highlighting would
be welcome.
Overpass... theoretically, it is doing exactly what it should be
doing. Somehow making it simpler to create a regex that does
Marc, I think that spelling rules is part of the specific language's
rules/naming, and should be allowed in tags. If some tool does not
normalize unicode for searching, the tool should be fixed (shouldn't be too
hard in most cases). Most search engines do these kinds of normalizations
before
Am 31.01.2018 um 19:33 schrieb Simon Poole:
> IMHO we should in general treat all unicode space variants as a nomal
that should have been "normal"
signature.asc
Description: OpenPGP digital signature
___
Tagging mailing list
I remain convinced that spelling rules have no place in osm tags
even if it would be convenient.
If they are to be added, the primary tools should first be asked to
manage them before considering their use. otherwise the slightest search
on a street name can fail, it's worse than having an
IMHO we should in general treat all unicode space variants as a nomal
ASCII space for processing and comparision purposes and leave it at that.
And we don't have the issues just in name tags, see
SKIP :
{
"\r"
| "\n"
| " "
| "\t"
| "\u200A"
| "\u2009"
| "\u00A0"
| "\u2008"
| "\u2002"
|
So... can we reach some conclusion?
I have a particular situation I need to resolve - some streets consist
of ways that (among other, meaningful differences) vary in their usage
of non-breakable spaces. Here are the possible solutions:
1) Start removing nbsp from local data
2) In case of
W dniu 31.01.2018 o 09:51, Janko Mihelić pisze:
On Sun, Jan 28, 2018, 10:50 Tom Pfeifer > wrote:
So, how does "exhibit=artwork" work for you?
+1
I like that key because it could have lots of useful values, like
exhibit=animal,
On Sun, Jan 28, 2018, 10:50 Tom Pfeifer wrote:
>
> So, how does "exhibit=artwork" work for you?
>
+1
I like that key because it could have lots of useful values, like
exhibit=animal, exhibit=car, exhibit=moon_rock, etc.
Janko
>
10 matches
Mail list logo