tor 2002-08-01 klockan 17.36 skrev Olivier Jousselin:
Comme je le vois, il y a 2 possibilités : soit "fr" est l'acronyme de "file-roller" et "FR" est là pour "Français", soit la convention est la même que pour les Locales, et "fr_FR" correspond bien au Français de France, celui où il n'y a ni "septante", ni "môdit Français" dans le dictionnaire ...
Toutes mes excuses aux Français d'ailleurs, naturellement.
Sorry, my French is lousy, but I'll try to answer anyway.
Including random abbreviations in translation file names is highly broken. The two letters before the underscore should always be a valid iso-639-2 language code, and the second two letters after the underscore should be a regional code (country code) if, and only if, the translation is specific to a specific territory or country and not only language. So if anyone thinks "fr" or "FR" stands for anything but French or France, he or she is highly mistaken.
My question was why this translation includes the country code. Unless this particular translation includes stuff that is specific to France and not any other French-speaking territory then this is very broken -- users not situated in France won't get any French translation at all.
Christian
Afficher les réponses par date
Le Thu, Aug 01, 2002 at 05:52:20PM +0200, Christian Rose a écrit:
My question was why this translation includes the country code. Unless this particular translation includes stuff that is specific to France and not any other French-speaking territory then this is very broken -- users not situated in France won't get any French translation at all.
This is the standard, as there is some differences (mentioned by Olivier) between France french and Canadian french, for example. For your particular problem, locales (libc) are supposed to be kind enough to choose the nearest translation if the specific one can't be found.
Arnaud.
This is the standard, as there is some differences (mentioned by Olivier) between France french and Canadian french, for example. For your particular problem, locales (libc) are supposed to be kind enough to choose the nearest translation if the specific one can't be found.
Sure there are differences between France French and Canadian French. But as long as we don't have separate translations for those two variants, there is no point in naming the French po file as fr_FR and risking to break systems from Quebec for example which are misconfigured. As soon as we've got fr_CA, fr_BE po files, then fr to fr_FR can be renamed if necessary (as a sidenote, I think the portuguese team names its files pt.po instead of pt_PT.po even if there is also a pt_BR team). Moreover, for me, a file with a suffix means "this translation is only for people from France, not for people speaking French in other countries", which is not a really good thing... So I'm all in favour of renaming it to fr.po, and maybe rerename it to fr_FR if one day we've got a po file for all French variants.
Christophe
PS: I'd like to have the opinions of Jean-Michel Ardantz or Roland Baudin on whether the naming of the file was intentional or if it can be changed.
Arnaud.
Nous avons toute la vie pour nous amuser, nous avons toute la mort pour nous reposer !
Gnomefr mailing list Gnomefr@traduc.org http://traduc.org/mailman/listinfo/gnomefr
tor 2002-08-01 klockan 18.29 skrev Arnaud Launay:
My question was why this translation includes the country code. Unless this particular translation includes stuff that is specific to France and not any other French-speaking territory then this is very broken -- users not situated in France won't get any French translation at all.
This is the standard, as there is some differences (mentioned by Olivier) between France french and Canadian french, for example.
Canadian French should use fr_CA, but only if it contains Canadian French or other stuff particular to Canada. There is no "standard" that says that French should always be specified as fr_FR.
For your particular problem, locales (libc) are supposed to be kind enough to choose the nearest translation if the specific one can't be found.
If I remember correctly; that's not true if you specify country code in the translation domain. A fr_CA users' system will do this if the only translation is fr_FR:
1) look for "fr_CA" translation -> not found 2) look for "fr" translation -> not found 3) use C translation
It could of course be that things have changed lately, but this is besides the point. The point is that we have a French translation team in GNOME, not a France French one nor a Canadian French one. As long as this team produces French translations, it should use the "fr" code, not anything else.
This is also what has been done in the past (I've yet to find another fr_FR.po in cvs), so why you call this a "standard" puzzles me.
Cheers, Christian
-
Arnaud Launay -
Christian Rose -
Christophe Fergeau