[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[libreoffice-l10n] New branches and translation across components


Hi all,

Christian has created the 6.4 project in Weblate, therefore master is
now the next 6.5.

He has migrated 6.3 project. (Do not forget to managed your watched
project if you want to have them in your Dashboard).

He has also activated translation across project. It is based on a hash
that Weblate creates based on context and the source string. He limited
the translation to match components of the same name.
In short that means that strings that have the same context will be
translated for all branches at once.

Then he sets priorities for the components (Weblate will decide from
that what end's up in "suggested translations") as follow:
- Help Master: lowest priority
- Help Release branch: low priority
- UI Master: low priority
- UI Release branch: high priority.

Oh and maybe I didn't say: we are running Weblate 3.9.1 now

As usual, feedback and advices are welcome :)
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

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.