Re: how to translate the windows installer

On 8/26/08, mikel paskual <mikel.paskual@gmail.com> wrote:
>
> Hi!
>
> I'm working on the Basque (eu) translation of Abiword (Only 3 fuzzy
> strings to go for the 100%).
> I also have to review all the previous translations (there are lots
> and incoherences) and test it all again and again, but I would also
> want to translate the Windows installer.
>
> I saw some nsh files in the source code, but those are not all the
> sentences in the installer.
>
> How could I translate the Windows installer?
>

To translate the installer you need to provide the translation file
and update the list of available languages. There are additional
steps if NSIS does not yet support the language.

0) the 1st and 2nd steps should already be done if you are updating an
existing translation.

1st) add a line to abi_lng_lst.nsh to include the AbiWord specific
translated strings, e.g.
${LANG_LOAD} "MyLang"
The new line should be placed approx alphabetical in the list and try
to avoid any fancy characters as this name corresponds to both the
filename used in the next step and the name NSIS uses to refer to the
language (see NSIS documentation / forums if you are unsure of your
language's name as used by NSIS and/or to get it added to NSIS).

2nd) copy lang/English.nsh to lang/MyLang.nsh
where MyLang should be the appropriate language name as used in the
previous step.

3rd) replace all the english text with appropriately translated text.
If the file already exists you may need to copy the new lines from
lang/English.nsh.
lang/English.nsh should always have all the strings used by the
installer not already translated by NSIS, the installer files will
actually fall back to using these strings if they are not provided in
the translated file (which is why many of the files do not contain any
translated text yet still work)
For each translated string in these files the format is
${LSTR} NSIS_IDENTIFIER "quoted text for the translated text"
(all the lines beginning with semicolons are comments and ignored)
for example:
${LSTR} TITLE_ssection_core "Abiword core components"

4th) test by running NSIS to build a new installer, see other
documents for setting up an appropriate environment for this task.

5th) send/commit patches and enjoy the new translations during installation

If your language is not already supported by NSIS or requires Unicode,
then translating the installer becomes more work as for proper support
the NSIS project must be updated to recognize the language and then
all of its standard translations (things like Next) will be needed;
there are others that have done these things in the past that can be
of better help if this is needed than myself. The AbiWord Windows
installer translations rely on the standard NSIS translation support
as much as possible to prevent duplicate translation work among NSIS
using software. Although the AbiWord specific strings are not stored
in a .po file (or other easier on translator format), we tried to make
the translatable text easy to provide/update.

Jeremy
Received on Fri Aug 29 05:07:30 2008