The renderers and ALL data consumers would then have to take that into
Tagging for the renderer means: Using a inappropriate tag on an object such
that it renders in a colour or style the mapper prefers over correctly
tagging an object.
Putting 2 names in a name field where those 2 names have equal standing is
not mapping for the renderer. That is mere pragmatism while mapping, and
yes, we like to get our stuff rendered. Outsiders should already be glad we
were able to agree on a consistent ordering for those names. The normal
Belgian compromise for resolving this would be: make sure that fr - nl and
nl - fr are equally distributed in name tags, at all times...
The reason for not choosing Brussel/Bruxelles is that Brussel - Bruxelles
clearly shows that there are 2 names in there. Instead of one long glued
together string of characters. And of course, there are place names which
have - in them, Sint-Agatha-Berchem - Berchem-Sainte-Agathe, for example.
(When I write them, I put nl first, obviously, that's my first language,
and incidentally also the language that place was known as, until maybe 200
years ago, before it became officially bilingual)
Op vr 10 aug. 2018 om 12:12 schreef SelfishSeahorse <
> Maybe a possible solution to get rid of name=* tags containing names
> in multiple languages would be to add the information about which
> languages are spoken in a particular region to its boundary relation
> (e.g. spoken_languages=de;fr to the municipality boundary of
> Biel/Bienne). However, the renderers would then have to take these
> relations into account.
> On Thu, 9 Aug 2018 at 13:25, Marc Gemis <marc.ge...@gmail.com> wrote:
> > ]
> > > > p.s. It is not the first time this question pops up.
> > >
> > > That can be a sign that something is amiss.
> > the previous times it popped up was not for consistency reasons, but
> > to do something on carto-css for osm.org
> > We do have multiple local tile sets for Belgium, where we do not have
> > that problem at all.
> > As a Flemish person it's even annoying that software like OsmAnd
> > announces the name field and not name:nl
> > Nobody uses the composed FR-NL name in real live. You always use one
> > of the two depending on preference or situation.
> > As someone suggested before, perhaps we should get rid of the usage of
> > name field for the default osm.org map and let the renderer decide
> > what (and how) to display names in multi-language areas based on
> > name:xx fields.
> > Let the local community assist in setting up those rules for carto-css
> > (e.g. French before Dutch), but the separator is decided by the map
> > maker.
> > All that seems better than starting to change the name (and
> > addr:street) field of tens of thousands of objects just because
> > someone does not like the rendering on the default osm.org map.
> > m.
> > _______________________________________________
> > Tagging mailing list
> > Tagging@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/tagging
> Tagging mailing list
Tagging mailing list