On Mon, Dec 09, 2019 at 09:11:35PM +0100, Jean-Baptiste wrote:
Le 05/11/2019 à 12:15, Daniel P. Berrangé a écrit :
> Next, and more importantly, I'm trying to understand how we will integrate
> with Weblate....
let's integrate your projects to the new translation platform.
where are the public bug trackers of your projects?
For libvirt related projects currently we use
So that I can gain a understanding of the weblate integration, lets start
with only the libvirt-glib project first
* which branch is your development branch?
master, but note weblate won't be allowed to either push or pull,
we must manually upload & download .pot/.po files
* have you merged latest translation from Zanata and locked the project?
I've hit the "make this project readonly" assuming that's what
you mean by 'locked'.
* Weblate will handle updates when pot file changes, don't edit po files for this
As above, we can't have weblate directly accessing git
* what is the license of translation? (please use a code from
* do you have any announcement/warning you would like to display to the translators? (it
will be displayed in Weblate)
Questions/clarifications about translations should be sent to the
libvir-list(a)redhat.com mailing list. For further information
* do you need us to activate any specific checks? (this is a setting per component )
Any .po file validation rules relevant to the C language.
Especially validating that printf format specifiers have
not been re-ordered/removed/changed, since we see that
screw up alot.
* do you need us to automatically detect new translation files? (typical usecase: website
translation with one translation file per page)