In data martedì 21 luglio 2020 17:52:37 CEST, Ming H. ha scritto:
------------------ Original ------------------
From: "Jwtiyar ali";<firstname.lastname@example.org>;
Send time: Tuesday, Jul 21, 2020 6:19 PM
Subject: [libreoffice-l10n] Adding translation to master and 7
As you know ckb is not yet available in stable release before i was adding
all translation to master branch, now we have master and 7 version, i have
to add translation to which one?
If you use Weblate's webpage-based editor to do the translating work, your
change in "UI - master" project will be automatically copied to "UI -7.0"
project, and similarly for "Help - master" and "Help - 7.0" as well,
assuming both strings are untranslated or translated the same way (so
changes to existing translations are copied, too). So there is no need to
worry or make a conscious choice.
It should work in this way. But unfortunately, as we are working "online", the
suggestions were not copied/moved to 7.0, so we have to re-check all strings
with suggestions "by hand".
Does anybody know a procedure to copy them automatically?
Open Source is better!
KDE neon: https://neon.kde.org/
La bici non consuma e non produce emissioni, non ingombra e non fa rumore:
è un mezzo ecologico per definizione e ad alta efficienza energetica.
La bicicletta migliora il traffico, l'ambiente, la salute e l'umore.
To unsubscribe e-mail to: email@example.com
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Impressum (Legal Info)
: 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