I was looking into the translations of "Côte d'Ivoire" in the various languages, and I found a lot of inconsistencies, so I'd like to understand what's the best path forward.
As per [1]:
> [...], the government declared that Côte d'Ivoire ([...])
would be its formal name for the purposes of diplomatic protocol and
has since officially refused to recognize any translations from French
to other languages in its international dealings. Despite the Ivorian government's request, the English translation "Ivory Coast" ([...]) is still frequently used in English by various media outlets and publications.
So I checked how this is handled in CLDR data and from a cursory check the data is _really_ inconsistent.
As far as I can tell there are some broad categories:
1. "CI" maps to "Côte d'Ivoire", "CI-alt-variant" maps to the local translation (examples: vi, tr, pl, de)
2. "CI" maps to the local translation, "CI-alt-variant" maps to "Côte d'Ivoire" (examples: fi, eu(?), it)
3. both map to "Côte d'Ivoire" (examples: id, sv)
4. both map to a local translation (examples: is, hr, ga, mk)
5. "CI" maps to a translitteration of "Côte d'Ivoire", "CI-alt-variant" maps to the local translation (examples: ky, mn, tk)
6. something else (examples: sr, zu - although zu may be considered category 1)
This is... suboptimal. I'm especially unhappy with categories 1 and 2 both existing, because it means there is no consistent way to pick "always Côte d'Ivoire or a translitteration" nor "always the local name".
Is there a procedure to decide what's the best approach and then have the data converge to it?
I have a guest account for it/de/fur, so I can only suggest modifications for those, but I think this issue needs a broader approach.
Leonardo Taglialegne