Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


2011/9/10 Miklos Vajna <vmiklos@frugalware.org>:
On Fri, Sep 09, 2011 at 10:40:54AM +0200, Andras Timar <timar74@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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.