Bug 859783 - firstboot translation update
Summary: firstboot translation update
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: i18n
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: i18n Engineering List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-24 02:51 UTC by Dave Young
Modified: 2013-01-22 06:42 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-22 06:42:28 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dave Young 2012-09-24 02:51:14 UTC
Description of problem:

firstboot_kdump.py changes a lot, so the translations need update as well.

I have pinged transifex people, also requested to create a zanata project, there's still no feedback.

This bus is for tracking the translation issue.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Dave Young 2012-10-23 06:07:16 UTC
Hi, Martin

I have created a zanata project:
https://translate.zanata.org/zanata/project/view/kexec-tools

But I have no idea what's the process of translation issues. Can you help?

Comment 2 Runa Bhattacharjee 2012-11-06 06:20:42 UTC
Hello Dave, Martin,

Are there any specific issues you anticipate? You can check the document below to see if this answers your query:

https://github.com/zanata/zanata/wiki/Opening-a-Translation-Project

You can also find help on the zanata-users mailing list.

https://www.redhat.com/mailman/listinfo/zanata-users

Thanks
Runa

Comment 3 Dave Young 2012-11-06 06:38:09 UTC
Hi,Runa

Thanks for reply.

Currently we have below po files which are saved on dist-git server as kexec-tools-po.tar.gz

[dave@localhost kexec-tools-po]$ ls
ar.po     bs.po  de.po     fa.po  hi.po  is.po            kn.po  Makefile  my.po  pl.po     sk.po       sv.po  ur.po
as.po     ca.po  el.po     fi.po  hr.po  it.po            ko.po  mk.po     nb.po  pt_BR.po  sl.po       ta.po  vi.po
bg.po     cs.po  en_GB.po  fr.po  hu.po  ja.po            ku.po  ml.po     nl.po  pt.po     sq.po       te.po  zh_CN.po
bn_IN.po  cy.po  es.po     gu.po  hy.po  ka.po            lo.po  mr.po     or.po  ru.po     sr  tr.po  zh_TW.po
bn.po     da.po  et.po     he.po  id.po  kexec-tools.pot  lv.po  ms.po     pa.po  si.po     sr.po       uk.po


I'm not sure which one is translated, because code changes the pot file will also change. For this case, what should I do?

I will read the docs if I got time, but if you can help to guide me I will appreciate.

What I want to know is below:
Should I upload pot file to somewhere?
For the old po files, should I upload them as well? one by one?
Is there a quick way for this?

--
Thanks
Dave

Comment 4 Runa Bhattacharjee 2012-11-06 09:02:54 UTC
Hi Dave,
You can very easily upload the files (po and .pot) to the server using the Zanata clients. It is recommended to use the Maven client at present. You'll need to have a configuration file pom.xml in your local repository. The details on how to use the maven client and a sample pom.xml file is at:

https://github.com/zanata/zanata/wiki/Zanata-Maven-Integration


More information about the clients is here: https://github.com/zanata/zanata/wiki/Client-Configuration

Thanks
Runa

Comment 5 Dave Young 2012-11-30 06:11:35 UTC
The kexec-tools git tree see below url:

http://pkgs.fedoraproject.org/cgit/kexec-tools.git/

Comment 6 Dave Young 2012-11-30 06:25:00 UTC
Per runa's suggestion, I will firstly update kexec-tools repo, to make it into the conventional mode available for zanata translating process.

That means update latest po/*.po and merge them with old translated po files.

Comment 7 Dave Young 2012-12-05 02:10:37 UTC
I have pushed all the po files to zanata server for translation except for a few languages which are not availabe on zanata language list. I have checked there was no translation previously for these exception languages, so I think we can ignore them for now.

Comment 8 Jens Petersen 2013-01-22 06:42:28 UTC
I believe this can be closed now.


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