[Libreoffice] [PUSHED] speed up localized builds by introducing po2lo

Andras Timar timar74 at gmail.com
Thu Sep 15 02:29:28 PDT 2011


2011/9/10 Miklos Vajna <vmiklos at frugalware.org>:
> On Fri, Sep 09, 2011 at 10:40:54AM +0200, Andras Timar <timar74 at gmail.com> wrote:
>> There are 2 minor issues.
>> 1. When the English string contains \n and translation does not
>> contain \n, the script outputs the English string instead of the
>> translation. See for example this line:
>> basctl        source\basicide\basidesh.src    0       string  RID_STR_SOURCETOBIG                             15504   sd      The
>> source text is too large and can be neither compiled nor
>> saved.\nDelete some of the comments or transfer some methods into
>> another module.
>>
>> 2. Your script produces sdf lines even when the corresponding po file
>> does not exist at all. For example many languages do not have help
>> translations at all, but your script copies English heIp lines to
>> localized sdf files in this case.
>
> I'm attaching newer versions of both patches:
>
> - the translations one is fixed wrt python (see
>  82f6c0502e51afbc25e5bf0fcee7914a1a5b3f28, the patch had the same
>  problem)
> - the core one should be fixed wrt the above two issues
>
>  [ The newline issue was a bug in the po parser, handling multiline
>  msgid/msgstr entires, the second problem is simply fixed by checking
>  if the relevant po file exists or not. ]
>
> This time I tested it with not only "hu", but "af" and "sd" locales as
> well.
>
> Miklos
>

Pushed both patches.

Best regards,
Andras


More information about the LibreOffice mailing list