Zanata translations

Setroubleshoot translations currently live in the following locations:

• https://vendors.zanata.redhat.com/project/view/setroubleshoot (proprietary)

  • contains translations for stable branch (RHEL) only
  • maintains only a few languages
  • updated only by RH localization effort (e.g https://bugzilla.redhat.com/show_bug.cgi?id=1481227)
  • therefore usually does not contain latest translations

• https://fedora.zanata.org/project/view/setroubleshoot

  • contains translations for both stable (RHEL) and master (Fedora) branches
  • maintains large number of languages (several of which do not actually contain any translated strings)
  • updated by community and partially by RH localization effort (Updates from vendors.zanata are backported here, but not all strings match between "stable" and "master" branches)

• setroubleshoot source repositories (https://pagure.io/setroubleshoot and https://github.com/fedora-selinux/setroubleshoot)

  • is kept up-to-date with fedora.zanata

---

How to update source files on fedora.zanata:

$ git clone [email protected]:fedora-selinux/setroubleshoot.git
$ cd setroubleshoot/framework
###Update Makefile
$ dnf install dbus-glib-devel libnotify-devel dbus-devel gtk3 gtk3-devel libcap-ng-devel
$ ./autogen.sh
### Generate new potfile
$ cd po
$ make setroubleshoot.pot
### Repeat the process for plugins
### Push potfiles to zanata
$ zanata-cli push --push-type source

How to pull new translations from zanata:

$ git clone [email protected]:fedora-selinux/setroubleshoot.git
$ cd setroubleshoot
### Make sure "zanata.xml" file pointing to corresponding translations branch is present
### Optionally update source files on zanata
### Pull new translations from zanata
$ zanata-cli -e pull --pull-type trans

What do I have to do differently when dealing with vendors.zanata:

### Copy zanata.xml from distgit or download it from zanata
### "zanata-cli" commmands require 2 additional parameters (or corresponding info can be stored in ~/.config/zanata.ini)
### --username <username> --key <your API key>
### For more detail see http://docs.zanata.org/en/release/client/configuration/

How to sync-up fedora.zanata with vendors.zanata and vice versa:

### Make sure that both zanata repositories contain the same version of potfiles (otherwise some strings may not be properly transfered)
### Copy zanta.xml (vendors.zanata) into separate directory
$ mkdir zanata-setroubleshoot ; cd zanata-setroubleshoot
$ wget --no-check-certificate "https://pkgs.devel.redhat.com/cgit/rpms/setroubleshoot/plain/zanata.xml?h=rhel-<version>" -O zanata.xml
### Download translation files from vendors.zanata
$ zanata-cli pull --pull-type trans --username <username> --key <your API key>
### This should create directory tree as follows
       - zanata-setroubleshoot
              - zanata.xml
              - framework
                      - po (folder)
              - plugins
                      - po (folder)
### Replace zanata.xml with one from fedora branch (make sure it references the "stable" branch)
$ rm zanata.xml ; wget https://raw.githubusercontent.com/fedora-selinux/setroubleshoot/stable/zanata.xml
### Push translations to fedora.zanata
$ zanata-cli push --push-type trans
### Zanata will use the latest version of each string