mojito
mojito copied to clipboard
box
First pass for adding North American indigenous locales
Gitter chat context: https://gitter.im/box/mojito?at=5eed1a307ba3965373b936c1
Hey @aurambaj! No pressure to work with this PR if it's stepping on your toes, but I was eager to give it a shot!
Any thoughts on reviewing this? (I'm sure there are things wrong with this approach, but thought it better to have something to talk over 🙂 )
And FYI, I'm attempting to use UN M49 Standard Country or Area Codes "representing geographical (continental and sub-continental) supranational regions" (e.g., nv-003) as opposed to nation-state boundaries that may be disputed by the nations speaking the language (e.g. nv-US). This is consistent with es-419 (latin american spanish), which also uses one of these codes.
I tried to choose the best of either 003 (North America, including Mexico and Central America) or 021 (Northern America, which excludes Mexico and below), based on where traditional territories seemed to be. A native speaker may be able to offer more input on how best to handle this.
Other options would be to use 000 for "missing data", or 019 for "Americas", or perhaps something odd like 778 for "Transition countries" (though I think that has a specific meaning). Anyhow, the point is that I would defer to considering whatever native speakers might want to advocate for.
No hey, not the weeds at all. At some level, this is important. As I understand, the changes are larger than this specific project, which is just parrotting the terms used from the international language standards.
This drove me down a rabbithole into the CLDR issue queue. Seems they're about to cut their yearly release. The process seems to involve changes having "vetters", of which "guest vetters" have a single vote count. From what I gather, a proposal for changes/additions requires 8 votes.
https://unicode-org.atlassian.net/
So any changes that you feel should be merged into the standard can perhaps get into the queue with enough non-insiders registering for their system and vouching for any changes.
No hey, not the weeds at all. At some level, this is important. As I understand, the changes are larger than this specific project, which is just parrotting the terms used from the international language standards.
This drove me down a rabbithole into the CLDR issue queue. Seems they're about to cut their yearly release. The process seems to involve changes having "vetters", of which "guest vetters" have a single vote count. From what I gather, a proposal for changes/additions requires 8 votes.
https://unicode-org.atlassian.net/
So any changes that you feel should be merged into the standard can perhaps get into the queue with enough non-insiders registering for their system and vouching for any changes.
We can take this offline but I am not understanding how to be an outside vetter. Let me know on Slack and we can take it from there.
