Quoting Frans Pop (firstname.lastname@example.org): > > A compromise seems to be adding an "english" task with > > "iamerican" so that *all* en_* installs have iamerican, ispell and d-c > > (en_GB would then have ibritish and iamerican). > > > > Another option would be dropping the british task and use "iamerican" > > and "ibritish" in a general "english" task (after all, is it correct > > to only have iamerican for en_IN, en_AU or en_ZA?) > > Or keeping the en_GB task and adding an en task alongside that that is > used as default for any en_* locale that does not have a country-specific > task. That seems to me to be most in line with the general localization > rules: use a language task, unless a more specific language_country task > is available. Yes, that solution is apparently what I proposed in my first paragraph above (but I didn't make it clear that the proposal was keeping "british").
Description: Digital signature