Quoting Frans Pop (email@example.com): > On Saturday 05 September 2009, Christian Perrier wrote: > > 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. Fomr MJ Ray's argument, we'd better create an "english" task with both iamerican and ibritish as at least en_AU and en_NZ need the two of them. Alternative: british: for en_GB, en_AU, en_NZ --> ibritish english: for en --> iamerican Thus, GB, NZ, AU would end up with both dictionaries and others only with iamerican. However nothing tells us that other places only use iamerican. Many of them being former British colonies, with a stronger British culture than USA, we can assume the opposite. So, it's highly probable that all countries but USA need both dictionaries and only USA strictly needs one. Si, would it really be a problem is en_US installs have both dictionaries? At this step of the discussion, I slightly favor dropping "british" for an "english" task that will install both dictionaries.
Description: Digital signature