Re: Weblate transition & integration for upstream projects

Daniel P. Berrangé <[email protected]>
Newsgroups gmane.linux.redhat.internationalization
Message-ID <[email protected]>
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....
> > 
> Hello Daniel,
> 
> 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

  https://bugzilla.redhat.com/enter_bug.cgi?product=Virtualization%20Tools

> I have a group of question for each repository:
> https://fedoraproject.org/w/index.php?title=L10N_Move_to_Weblate/Message_for_upstream_project&action=edit

So that I can gain a understanding of the weblate integration, lets start
with only the libvirt-glib project first

https://libvirt.org/git/?p=libvirt-glib.git;a=log
https://fedora.zanata.org/project/view/libvirt-glib/?dswid=478

 * 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 [2]

   As above, we can't have weblate directly accessing git

 * what is the license of translation? (please use a code from https://spdx.org/licenses/)

    LGPLv2-or-later

 * 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
   [email protected] mailing list. For further information
   consult https://libvirt.org

 * do you need us to activate any specific checks? (this is a setting per component [3])

   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)

   Nope



Regards,
Daniel
-- 
|: https://berrange.com      -o-    https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org         -o-            https://fstop138.berrange.com :|
|: https://entangle-photo.org    -o-    https://www.instagram.com/dberrange :|
_______________________________________________
trans mailing list -- [email protected]
To unsubscribe send an email to [email protected]
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.