> Being able to offer a choice of locales is something I thought of as well. > This could be implemented as wellif we were to use a table: > > Example of a table (1st value in 2nd field is default): > cy_GB:cy_GB.UTF-8 # only one option, so no choice > en_US:en_US|en_US.UTF8 > fr_FR:[EMAIL PROTECTED]|fr_FR.UTF8 # omitting the deprecated fr_FR > fr_CA:fr_CA|fr_CA.UTF8 > jp_JP:ja_JP.EUC-JP|ja_JP.UTF-8 > # > # For the Netherlands I'd personally like to see: > nl_NL:[EMAIL PROTECTED]|nl_NL.UTF8 > en_NL:en_US|en_US.ISO-8859-15|en_US.UTF8
Let me summarize your proposal to see if I understand it well. You suggest we build this table for the most widely used language_country combination...or more precisely, for all for which there's a potential problem. -Then, at the end of countrychooser postinst, we compare $LANGUAGE_$COUNTRY to this list. -If it matches one entry, we get the list of suggested locale -if the list has one entry, we use it and continue -if it has more than one entry, we ask the user for choosing and we default to the first entry. The question is then medium priority. Did I understand well? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
