Re: AbiWord Windows builds and L10n workflow

On Mon, Jun 25, 2012 at 11:41 AM, Prashant Bafna <[email protected]> wrote:
>
> Hi Cjl,
>
> Can you please check if you included the localization files that
> Martin mentions about in the mail below for the Windows installers (he
> mentions a separate file not a po one)
>
> Thanks,
> Prashant
>
> On Mon, Jun 25, 2012 at 2:16 PM, Martin Srebotnjak <[email protected]> wrote:
>> These are almost all languages so I don't think their incompletness of
>> localization is the issue here. As far as I remember Slovenian is 100%
>> for this build, so ...
>>
>> Did you include localization files for the Windows installer, that is
>> a separate file, not a po one.

As for the Windows installers, I believe he may be referring to the
*.nsh files, which have not been set up for L10n in Pootle.  I will
look into how I might be able to do that, even if it is not an
automated commit, it should hopefully not change much once translated.

There are also the files in
/user/wp/templates/
that may be needed, but I would love confirmation of that.

There are possibly other places where the language list is enshrined,
for instance, language names are in the PO file itself, so I need to
check that list (and section of code) for completeness.

This is not an uncommon issue in my experience (touching multiple
points for language inclusion), there is a very obscure line in the
Sugar source code where you need to list the language codes or else
the language does not get built.  *sigh*

I would just like some feedback from those more familiar with the
AbiWord code than I am to make sure that we touch all the places
needed to get it done in one build instead of fumbling around with
incomplete builds until we find the right combination of changes to
include the new languages.

Regards,

cjl