change ar-AR to ar-JO for more accurate locale

[James Fournie]

the ar-AR locale is probably not right. ar-AR is technically "Arabic (Argentina)". It is reported as such in the staff client. I would imagine that if someone is working on an Arabic translation, we'd want to use ar_SA or something?

[Dan Scott (denials)]

You're correct. The problem is that our locale handling absolutely requires region codes. For Arabic, I didn't know what region code to apply to the "ar" language (as Launchpad doesn't tell us what region the Arabic translation was performed for, and not knowing the translator who provided the Arabic translations that we have) - so we just reused the language code for the required region code.

ar-ZZ maybe?

[Jason Stephenson (jstephenson)]

I think we should just remove the ar-AR translations.

Only ten strings are translated in this language, and one of those is simply a copy of the format string from the msgid.

We also don't know who the translator was.

[Ben Shum (bshum)]

Based on new support for Arabic strings being added to the translation source from folks in Jordan, suggesting for this bug that we change it from ar-AR to ar-JO, for Arabic (Jordan). Implementation to come later.

[Ben Shum (bshum)]

Did a move in git for all the ar-AR.po files and made them into ar-JO.po files. Updated the script for update_pofiles as well, to use ar-JO for the locale for ar (arabic). Will test further during the 2.12 beta series to see how this change affects the language build.