Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flag preset names are unlocalized #5982

Open
1ec5 opened this issue Jan 2, 2022 · 3 comments
Open

Flag preset names are unlocalized #5982

1ec5 opened this issue Jan 2, 2022 · 3 comments
Labels
i dont know ¯\_(ツ)_/¯

Comments

@1ec5
Copy link
Member

1ec5 commented Jan 2, 2022

The flags tree has displayNames in English only. This results in a suboptimal experience for users of languages other than English, who have to know the name of the flag in English (or the ISO country code of a national flag). Unlike a brand or operator, a localized flag name is the norm, not the exception.

The way NSI is currently set up, we would basically need to multiply the number of man_made/flagpole entries by the number of supported languages. That would cause every user to see the name of a given flag in every language all at once, because there’s no way to filter an entry by user language, only by geography.

Maybe the project could instead pull the names automatically from the associated flag:wikidata or subject:wikidata QID as an occasional build step, and a data consumer could display only the name that matches the user language? Alternatively, NSI could adopt a localization system similar to the one used by id-tagging-schema – that is, as part of the iD project. But that would be unnecessarily complicated for the other trees, and it’d be busywork for iD translators to retranslate basic things like country names that are already available elsewhere.

/ref #5960 (comment)

@bhousel
Copy link
Member

bhousel commented Jan 2, 2022

I dunno, I just said I don't want to introduce localization here.
Multiplying the current 384 flags * the current 90ish languages = translation of 34k+ strings, and we're nowhere close to tracking all the flags that people might want to map.

@1ec5
Copy link
Member Author

1ec5 commented Jan 2, 2022

Right, I agree with you that introducing localization here isn’t great. So how do we solve this problem, either here or in some other project? Should flags move to id-tagging-schema?

@bhousel
Copy link
Member

bhousel commented Jan 2, 2022

I dont know, there might not be a solution for this. I agree that leveraging the existing translations in Wikidata is the way to go.

Also I dont really have any authority over those other projects anymore, so I think it's time to move on and not think about solving problems there.. I need some time to think about it. (Put another way, it seems pretty clear to me that dumping a load of flags into id-tagging-schema and asking people to translate them all is not the answer).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
i dont know ¯\_(ツ)_/¯
Projects
None yet
Development

No branches or pull requests

2 participants