Since not every feature has a name in both languages, database users should consider =fr;nl to mean “French name, Dutch name, or both”; so it’s an AND/OR operation.
This way there is no need to add a separate default:language tag for any feature that have either a name:fr= tag or a name:nl= tag, or both. I believe this should work for a large majority of named features even in a multilingual, cosmopolitan city like Brussels. In most places it will be much simpler. On Fri, Oct 19, 2018 at 6:09 AM Martin Koppenhoefer <[email protected]> wrote: > > > sent from a phone > > > On 17. Oct 2018, at 06:28, Joseph Eisenberg <[email protected]> > wrote: > > > > This would certainly be a mistake. However, the default:language tag for > Brussels would only be on the administrative boundary, not on individual > features. Only individual features with a name in a foreign language would > need a default:language tag. > > > I would have thought all features whose name isn’t like the default. If > the default is “fr:nl” but the name is French or Dutch but not both, you’d > have to individually override the default name tag from the surrounding > admin boundary. > > > Cheers, Martin > _______________________________________________ > Tagging mailing list > [email protected] > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list [email protected] https://lists.openstreetmap.org/listinfo/tagging
