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

If I have to choose, keep old system where all dismissed errors are transfered to new branch.

4.2 branch l10n became active in november 2013. That is almost 6 months to date. Whoever wanted to translate it 100% and clear all errors, already did that. It's less damage to have same error re-appear in finished 4.2 with which most translators will have minimum contact with, then in 4.3 where you need to mark them all as NON error all over again.

Please don't force us to do meaningless work.
Here you can see what are those errors. 4.1 was 100% error free before 4.2 branch.

900 unchanged - we don't translate name, brands, and few english words like "Status" are spelled same in EN and HR 222 simple capitalization - Mostly Because Of Those New Found English Spelling Where You Capitalize Every First Letter In Sentence 136 acronyms - I think every ALL CAPITAL LETTER WORD is marked as acronym, like "OK" for example which we translate "U redu" and that's an error 101 punctuation spacing - this is trivial, if in EN you have "something (something)." and in HR it is "(something) something." it's an error
and so on...

Best regards,

Dana 2.5.2014 12:13, Christian Lohmaier je napisao:
Hi Andras, *,

On Friday, May 2, 2014, Andras Timar < <>> wrote:

    On Fri, May 2, 2014 at 11:49 AM, Christian Lohmaier
    < <javascript:;>> wrote:
    >> On 4.2 I have 100% translated strings and 0 errors. On 4.3
    there are
    > around 2500 errors present.
    > Ah, now I understand. Unfortunately that's not stored in the po
    files, so
    > would need digging deep in the database. So that's something for

    This is why we had libo_ui and libo_help projects without a version
    number, most of the work is done there. You can just create libo42_ui
    and libo42_help projects and move 4.2 files there, and update 4.3 in
    the unversioned project. This way the error status metadata is kept.

That way you loose the error-markings for the 4.2 branch. so everything has drawbacks.

Import is already running for many ours, so I don't really want to abort that just because of that.

Rather such a high number of errors indicate a poblem with the check itself, doesn't it?


To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.