Re: [PATCH] Automatize creation of DATA lists for Makefiles

On Wed, May 16, 2012 at 10:16 AM, Ingo Brückl <ib@wupperonline.de> wrote:
>
> Chris Leonard wrote on Tue, 15 May 2012 16:52:03 -0400:
>
>>>> ar_EG
>>>> ar_SA
>>>> de_AT
>>>> en_NZ
>>>> en_ZA
>>>> es_AR
>>>> es_IR
>>>> fr_BE
>>>> fr_CA
>>>> fr_CH
>>>
>>> There are no .po files for these in svn, i.e. they can't be removed
>>> because they don't exist for AbiWord.
>
>> However lines for these apparently exist in two of the Makefiles, and
>> it is from there that they should be removed to leave the code as
>> clean as possible.
>
>> user/wp/Makefile.am
>> user/wp/templates/Makefile.am
>
> These have a slightly different meaning, because they are more related to
> the user's locale which does not only include the language, but additional
> information. For example, in fr_CA the pagetype is letter and in fr_CH it
> is A4. (Same goes for units, cm vs. inch.)
>
> But we should reduce them and use generic ones, like cm (ISO standard) in
> system.profiles and inch in system.profile-en-US. We could then remove all
> system.profile-ll{-CC} that currently only define cm as well.
>
>>>> en_AU
>>>> en_CA
>>>> en_IE
>>>> es_MX

Ok, I'm getting a better picture of how country-specific locale info
is represented in AbiWord. I suspected it had to be a little
different because it doesn't directly use gettext, with preprocessing
to .strings files first. but I wasn't up-to-speed on the details.

>>> There are .po files in svn. What's wrong with these?
>
>> Simply because it is possible to make a distinction does not mean it is
>> worthwhile to do so. [..] the consensus is that for written Spanish, the
>> effort to maintain variants is not worth it.
>
> This is an interesting aspect. I agree that the language files should be
> considered to represent the written language.
>
> For language en, for example, we possibly could reduce to four files:
>
> po/en.po                       (generic)
> po/en-GB.po                    (country-specific)
> user/wp/system.profile         (generic, unit: cm)
> user/wp/system.en_US.profile   (inch instead of cm)
>
> (Using hyphen if focus is on language and underscore if focus is on locale.)
>
> The template files contain a "lang" property and I'm afraid we have to
> provide one for each locale we are supporting (for language en, for example):
>
> user/wp/templates/normal.awt         ("generic", locale en_US)
> user/wp/templates/normal.en_AU.awt   (locale-specific)
> user/wp/templates/normal.en_CA.awt   (locale-specific)
> user/wp/templates/normal.en_GB.awt   (locale-specific)
> user/wp/templates/normal.en_IE.awt   (locale-specific)
> user/wp/templates/normal.en_NZ.awt   (locale-specific)
> user/wp/templates/normal.en_ZA.awt   (locale-specific)
>
> If there is consensus that this is desirable and that we should reduce
> and remove language, system and template files were possible, I could
> realize that together with Chris.

I'm happy to collaborate on achieving the best i18n/L10n results for
AbiWord. I'm still learning about the specific quirks of AbiWord in
that regard, but I'm a fairly quick study and more than willing to
take on mundane clean-up tasks for the larger goals of better native
language user experiences and greater administrative efficiency in
providing it.

Regards,

cjl
Received on Wed May 16 18:01:07 2012