[Tickets #8816] Re: includes a fr_FR.po translation instead of fr.po

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/8816
------------------------------------------------------------------------------
  Ticket             | 8816
  Updated By         | math.parent at gmail.com
  Summary            | includes a fr_FR.po translation instead of fr.po
  Queue              | Horde Base
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


math.parent at gmail.com (2010-01-05 13:06) wrote:

>> 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