Hi Sveinn,
Le 20/11/2019 à 09:30, Sveinn í Felli a écrit :
Since Weblate 3.9 seems to address downloading of multiple files and
work is in progress for grouping files (aka. being able to see our
branches more like a folder-like structure, not a list with all
individual files, right?), then I'm optimistic for the future.
:-)
Nevertheless, testing should be thorough before we depend solely on this
tool, and some kind of statistics would be nice to have when assessing
the impact of such a migration. For example, comparing translation
percentages of LibreOffice 6.3 and the next release (7.0) would give us
some indication, even if it's not really comparable.
I agree with you, that's why we need feedback either from those who
already use Weblate or from those discovering it (BTW there is no 7.0
yet ;) Sharing is important here.
Cheers
Sophie
--
Sophie Gautier sophie.gautier@documentfoundation.org
GSM: +33683901545
IRC: sophi
Foundation coordinator
The Document Foundation
--
To unsubscribe e-mail to: l10n+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/l10n/
Privacy Policy: https://www.documentfoundation.org/privacy
Context
Re: [libreoffice-l10n] Weblate, where we stand currently · Sveinn í Felli
Re: [libreoffice-l10n] Weblate, where we stand currently · kees538
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.