Bug#266226: locales: @euro support should again be supported for _all_ euro countries
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Christian,
First of all, I'm very happy that you've started work on this. I was thinking
of giving this a go myself.
I think your proposal should work, so please go ahead if you prefer that.
I'd just like to add some of my thoughts.
On Tuesday 17 August 2004 08:58, Christian Perrier wrote:
> Maintaining a table in countrychooser for the special @euro case is
> not really satisfactory for me. I'd prefer adding a medium priority
> question about modifiers when there are different modifiers
> possibilities for a given locale:
>
> -at the end of countrychooser we have xx_YY as LOCALE
> -we grep SUPPORTED for all supported locales with this
> -if there are two or more of these, we prompt (medium prio) about the
> one to choose, defaulting to the one with the modifier
The downside for this is that this would probably result in a prompt for most
locales as most have a "standard" locale and an UTF variant.
Personally I don't mind this (as you say: at medium or low priority).
Two remarks:
- - IMHO it's very important to get the default right; taking a default
modifier from languagelist has obvious limitations.
For instance, suppose that an English speaking country YY would like
their default to be en_YY.UTF8. As en_US does not have the .UTF8 modifier,
this would be difficult in your proposal.
- - Using ALL supported locales to generate the list for the dialog means we
will also offer the deprecated nl_NL and fr_FR locales for new
installations.
That's what gave me the idea of putting the defaults in a separate table as
maybe the most flexible solution for the long run (and not only for @euro,
but for all special wishes regarding locales, see below).
Of course the downside is that you still have to provide defaults for
combinations not in the table and that you'll have to maintain the table.
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:fr_FR@euro|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:nl_NL@euro|nl_NL.UTF8
en_NL:en_US|en_US.ISO-8859-15|en_US.UTF8
If I can help by reviewing/testing your changes, please let me know.
Cheers,
FJP
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFBIlLQgm/Kwh6ICoQRAmBNAKDTuisYIddE6vJfCYgNf8Ryj3cCzACcDdgV
HdoFyj53uoaWyGNODfgOqBs=
=rR36
-----END PGP SIGNATURE-----
Reply to: