search

dr5hn / countries-states-cities-database

🌍 Discover our global repository of countries, states, and cities! 🏙️ Get comprehensive data in JSON, SQL, PSQL, XML, YAML, and CSV formats. Access ISO2, ISO3 codes, country code, capital, native language, timezones (for countries), and more. #countries #states #cities
https://dr5hn.github.io/countries-states-cities-database/
Open Data Commons Open Database License v1.0
7.29k stars 2.54k forks source link

Translations of subregions using language name instead of code #854

Open mtsfer opened 1 week ago

mtsfer commented 1 week ago

The languages in the subregions translations object is using the language name while in regions, countries, states and cities the language code is being used.

subregions.json:

"translations": {
            "korean": "오스트랄라시아",
            "portuguese": "Australásia",
            "dutch": "Australazië",
}

countries.json:

"translations": {
            "kr": "아프가니스탄",
            "pt-BR": "Afeganistão",
            "pt": "Afeganistão",
}
dosubot[bot] commented 1 week ago

Hey @mtsfer, I'm here to help you with any bugs, questions, or contributions you have. Let's tackle this translation issue together!

The subregions translations are indeed using language names instead of language codes, unlike the regions, countries, states, and cities translations. For example, in subregions.json:

"translations": {
    "korean": "오스트랄라시아",
    "portuguese": "Australásia",
    "dutch": "Australazië"
}

In contrast, countries.json uses language codes:

"translations": {
    "kr": "아프가니스탄",
    "pt-BR": "Afeganistão",
    "pt": "Afeganistão"
}

This discrepancy is due to the structure of the translations object in the subregions data, where each translation is keyed by the language name [1][2].

To continue talking to Dosu, mention @dosu.