Closed cooljeanius closed 1 month ago
The split sounds reasonable to me
The split sounds reasonable to me
...so, to be clear, that's the latter of the two options, correct?
A separate en_US
which is based on the current en
seems reasonable to me.
As you already found this will ensure that no existing translations need updates to match the new msgids.
Both options suit me.
OK, I'll start working on a separate en_US
translation for the 1.8.0 release; I want to get 1.7.0 out the door first, though...
OK, I'll start working on a separate
en_US
translation for the 1.8.0 release; I want to get 1.7.0 out the door first, though...
Update: I opened #217 for this.
whichever of my spellcheckers that
wmllint
is using (it looks like it might have changed from AppleSpell to Aspell?) has started complaining about various British spellings used in the add-on:Should I replace them with their American spellings in the source strings (breaking translations in the process), or create a separate
en_US
translation that uses American spellings?