Bug 1324569 - Libvirt zanata translations have not been updated for more than year
Summary: Libvirt zanata translations have not been updated for more than year
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-06 16:12 UTC by Yuri Chornoivan
Modified: 2016-04-20 14:30 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-20 14:30:06 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Yuri Chornoivan 2016-04-06 16:12:39 UTC
Description of problem:
Libvirt Zanata template has not been updated for more than year (17-03-2015).

Now "make update-po" shows for the raw uk.po file in repo

7813 translated messages, 751 fuzzy translations, 249 untranslated messages.

and

7900 translated messages, 751 fuzzy translations, 162 untranslated messages.

for "100%"-translated file from Zanata:

https://fedora.zanata.org/iteration/view/libvirt/master/languages/uk

Version-Release number of selected component (if applicable):
git/master

How reproducible:
Always

Steps to Reproduce:
./autogen.sh && cd /po && make update-po

Actual results:
rm -f uk.gmo && /usr/bin/msgfmt -c --statistics -o uk.gmo uk.po
7813 translated messages, 751 fuzzy translations, 249 untranslated messages.

Expected results:
rm -f uk.gmo && /usr/bin/msgfmt -c --statistics -o uk.gmo uk.po
8813 translated messages.

Additional info:
Many thanks from Fedora translators for uploading new template to Zanata and using our translations in the future releases.

Comment 1 Cole Robinson 2016-04-08 00:13:35 UTC
DV, do you have a 'zanata-cli push' call somewhere in your release process?

Comment 2 Yuri Chornoivan 2016-04-08 13:49:50 UTC
Thanks for updating template on Zanata. Now this bug can be closed.

However I'm not sure about the status of NEEDINFO request, so leave changing the status of bug for developers and maintainers consideration.

Comment 3 Cole Robinson 2016-04-20 14:26:09 UTC
Sounds like the root issue was fixed, so closing. I'll follow up with DV


Note You need to log in before you can comment on or make changes to this bug.