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


Hi Andras, *,

On Friday, May 2, 2014, Andras Timar <timar74@gmail.com> wrote:

On Fri, May 2, 2014 at 11:49 AM, Christian Lohmaier
<lohmaier@googlemail.com <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 later.

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?

ciao
Christain

-- 
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/l10n/
All messages sent to this list will be publicly archived and cannot be deleted

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.