Re: [Tagging] Feature Proposal - Voting - Default Language Format

Excuse me if I didn't make myself clear, English is not my native language. In OSM the name of a place is usually, but not always the name on the sign. If the sign only had space for 5 characters, it will in many cases contain the short_name, not the name. In some cases, a venue would erect

Re: [Tagging] Feature Proposal - Voting - Default Language Format

sent from a phone > On 19. Oct 2018, at 20:14, bkil wrote: > > So this should usually be very close to the official name. In a few > cases, I have seen that the printer produced old_name. In other cases, > everyone knows the place by its short_name and it is the one usually > advertised on

Re: [Tagging] Feature Proposal - Voting - Default Language Format

Receipts in Hungary are required by law to include various metadata, they usually indicate at least the following: * ref:vatin:hu * operator * operator:addr * name * addr Some of the receipts I have reviewed also indicate the branch, while at other times it can be deduced from the website/ref

Re: [Tagging] Feature Proposal - Voting - Default Language Format

By “map users” I meant database users and map renderers, sorry On Fri, Oct 19, 2018 at 7:59 AM Joseph Eisenberg wrote: > Map users could guess that the first language should be shown first; for > example, if default:language=fr;nl you can show name:fr= first, then > name:nl= , and fall back on

Re: [Tagging] Feature Proposal - Voting - Default Language Format

Map users could guess that the first language should be shown first; for example, if default:language=fr;nl you can show name:fr= first, then name:nl= , and fall back on name= if neither language-specific tags exist. In Brussels the order of names shown on signs actually alternates; one sign is:

Re: [Tagging] Feature Proposal - Voting - Default Language Format

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,

Re: [Tagging] Feature Proposal - Voting - Default Language Format

sent from a phone > On 18. Oct 2018, at 19:33, bkil wrote: > > The name field can be easily read from the receipt, signs on premise, > the menu or from the local authority's company registry. I agree for signs and similar, but on the receipt and from the company registry you don’t get the

Re: [Tagging] Feature Proposal - Voting - Default Language Format

sent from a phone > On 17. Oct 2018, at 06:28, Joseph Eisenberg > 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

Re: [Tagging] Feature Proposal - Voting - Default Language Format

sent from a phone > On 17. Oct 2018, at 06:28, Joseph Eisenberg > wrote: > > The tag default:language=fr;nl should prompt a map renderer or database user > to find both name:fr and name:nl. It is up to the map renderer to decide how > to display the two names, if they wish. this is a

Re: [Tagging] Feature Proposal - Voting - Default Language Format

The name field can be easily read from the receipt, signs on premise, the menu or from the local authority's company registry. For example, based on our local registry, "KFC Gyorsétterem" is the official name of the following venue, and I've added some further properties as illustration:

Re: [Tagging] Feature Proposal - Voting - Default Language Format

17. Oct 2018 11:45 by joseph.eisenb...@gmail.com : > name=McDonalds isn’t really right, it should probably just be brand=McDonalds > unless the specific location has a real name. I disagree with that. In that case that fast food has both name and brand.

Re: [Tagging] Feature Proposal - Voting - Default Language Format

As we discussed last month, brands are not necessarily in a particular language. Name=McDonalds isn’t really right, it should probably just be brand=McDonalds unless the specific location has a real name. And what language is “IKEA”? But at any rate, it’s fine to just use name= for a chain

Re: [Tagging] Feature Proposal - Voting - Default Language Format

> Are there lots of POIs in Brussels that have a name in both > languages in the database <...>? what's Marc G. mean is that a Mc Donalds in Brussels (as nearly everywhere) nearly never have a name:fr nor a name:nl only a name=Mc Donald (bad ex, it's a brand, but I still use this one).

Re: [Tagging] Feature Proposal - Voting - Default Language Format

16. Oct 2018 14:54 by joseph.eisenb...@gmail.com : > Are there lots of POIs in Brussels that have a name in both languages in the > database but should only be displayed in one language? Depends on what map maker wants to show on her/his map.

Re: [Tagging] Feature Proposal - Voting - Default Language Format

On Tue, Oct 16, 2018 at 10:55 PM Marc Gemis wrote: > > Are there lots of POIs in Brussels that have a name in both languages in > the database but should only be displayed in one language? > > I don't understand this. Where should the POI be displayed in 1 > language ? That all depends on the

Re: [Tagging] Feature Proposal - Voting - Default Language Format

> Are there lots of POIs in Brussels that have a name in both languages in the > database but should only be displayed in one language? I don't understand this. Where should the POI be displayed in 1 language ? That all depends on the maker of the map, not ? If you make a map in Dutch, you first

Re: [Tagging] Feature Proposal - Voting - Default Language Format

Typically restaurants, shops, etc only have the name-field set, never (*) name:fr or name:nl Those are only set for POIs that have both a French and a Dutch name (government offices, big tourist attractions, streets, villages). m. (*) never say never, but in general we do not duplicate name into

Re: [Tagging] Feature Proposal - Voting - Default Language Format

If the POI has only one name, it won’t be a problem. For example, a business or amenity with a name:fr=x and no name:nl would not need an additional tag. Are there lots of POIs in Brussels that have a name in both languages in the database but should only be displayed in one language? Joseph On

Re: [Tagging] Feature Proposal - Voting - Default Language Format

I'm tempted to vote against the proposal, as it only works for a subset of the name fields in Brussels (and probably other places as well) Only "official names" follow the rule fr;nl. "official names" are names of villages, street names, government offices and the like. For all the other POIs the

[Tagging] Feature Proposal - Voting - Default Language Format

The proposal for a default:language= tag has been discussed for the past 3 weeks. There have been no new comments this week, and I hope the proposal is ready for approval. Thank you for all of your ideas and suggestions Please go to the proposal page and read the discussion on the talk page: