[#8816] includes a fr_FR.po translation instead of fr.po
Summary includes a fr_FR.po translation instead of fr.po
Queue Horde Base
Queue Version Git master
Type Bug
State Feedback
Priority 1. Low
Owners
Requester math (dot) parent (at) gmail (dot) com
Created 01/05/10 (70 days ago)
Due
Updated 01/05/10 (70 days ago)
Assigned 01/05/10 (70 days ago)
Resolved
Attachments
Milestone
Patch No

History
01/05/10 math (dot) parent (at) gmail (dot) com Comment #3 Reply to this comment
Using a country part in a translation file is a discouraged practice
except in very few cases (such as pt_BR).
Discouraged by whom?
Quoting again (from the same bug):
<quote>
For the vast majority of languages, using a country
part is irrelevant. Canadians speaks French the same way than French
do....or Austrians speak German the same way you do (or so closely
that having separate translations is irrelevant).

Less than a rule, this is general common practice. This does not
prevent people to use more specialized translations when they feel
it's appropriate.

</quote>

Also, using country part only when relevant avoid the use of aliases 
like in nls.php and don't attach a language to a country.
Using a fr_FR.po file instead of a fr.po file prevents users of fr_CA,
fr_BE, fr_LU, fr_CH and all other existing and future locales for
French to benefit from the French translation of the program.
The Horde NLS class is taking care of this already.
I didn't know that. This bug is then less relevant, it is just to 
remove the need to maintain $nls['aliases'].
The language does not vary among countries and, again, this is not the
general practice for programs localization.
But it may vary. There's different wordings between Swiss, Austrian, 
and German German for example, or probably between the Iberian 
Spanish and South American Spanish, let alone the different spelling 
between British and American English.
Including the country name right from the start we are prepared for 
adding country-specific alternate translations, and don't have to 
rename the general-purpose translation when we add one.
Yes, but with the no-country-by-default way of doing, you can put only 
certain strings in the country specific po.

Quoting again (from the same bug):
<quote>
For instance, the software can have a fr.po file which will be used as
a general French translation....and a few fr_XX files for more
specialized translations. But the common practice is first having a
fr.po file (and, more important, a fr.mo file after build) before more
specialized files.
</quote>

Regards

Mathieu

01/05/10 Jan Schneider Comment #2
State ⇒ Feedback		 Reply to this comment
Using a country part in a translation file is a discouraged practice
except in very few cases (such as pt_BR).
Discouraged by whom?
Using a fr_FR.po file instead of a fr.po file prevents users of fr_CA,
fr_BE, fr_LU, fr_CH and all other existing and future locales for
French to benefit from the French translation of the program.
The Horde NLS class is taking care of this already.
The language does not vary among countries and, again, this is not the
general practice for programs localization.
But it may vary. There's different wordings between Swiss, Austrian, 
and German German for example, or probably between the Iberian Spanish 
and South American Spanish, let alone the different spelling between 
British and American English.
Including the country name right from the start we are prepared for 
adding country-specific alternate translations, and don't have to 
rename the general-purpose translation when we add one.
01/05/10 math (dot) parent (at) gmail (dot) com Comment #1
State ⇒ Unconfirmed
Patch ⇒
Milestone ⇒
Queue ⇒ Horde Base
Summary ⇒ includes a fr_FR.po translation instead of fr.po
Type ⇒ Bug
Priority ⇒ 1. Low		 Reply to this comment
Using a country part in a translation file is a discouraged practice
except in very few cases (such as pt_BR).

Using a fr_FR.po file instead of a fr.po file prevents users of fr_CA,
fr_BE, fr_LU, fr_CH and all other existing and future locales for
French to benefit from the French translation of the program.

The language does not vary among countries and, again, this is not the
general practice for programs localization.

The bug also occurs for other translations. In general PO files should
only be named after the ISO_639 code of the given language and
should not use a country part with a ISO-3166 code. The only
accepted exceptions to this are:

-pt_BR for Brazilian Portuguese and pt alone for "standard Portuguese"
-zh_CN for "Simplified Chinese" use in mailand China and Singapore
-zh_TW for "Traditional Chinese" used in Taiwan

Lat both are different ways of wrinting Chinese, not to be confused
with Mandarin/Cantonese which are different ways of *speaking*
Chinese....both being written the same way.

regards

Mathieu P

(Wordings taken from http://bugs.debian.org/336798)

References:
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336812
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336815
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336818
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336824
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336798
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336800
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336819
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336820
- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=336821