Skip to content

Latest commit

 

History

History
39 lines (21 loc) · 2.03 KB

Demo-Zanata-Publican.md

File metadata and controls

39 lines (21 loc) · 2.03 KB

Demonstration of working on publican standardized document sources with Zanata.

Introduction

This page demonstrates how localization teams works on publican standardized document sources with Zanata. The directory locations and other parameters are specified to author's development environment. Please customize it if needed.

For how to test on local JBoss server, please check out [[How to Test on Local JBoss|HowToTestOnLocalJboss]].

For how to build a document, please check out Publican User Guide.

Preparation

  1. Make sure a translator has his/her Zanata account created and has joined corresponding "Language team" (ja-JP / Japanese-Japan in this case).

  2. Download and install zanata-python-client client package:

    $ rpm -Uvh zanata-python-client-[ver-rel].rpm

  3. Check out publican standardized document sources from repository:

    $ svn co http://svn.fedorahosted.org/svn/publican/trunk/publican/Users_Guide

  4. Create POT files from Publican XML files:

    $ publican update_pot

  5. Update any existing PO files from Publican XML files:

    $ publican update_po --langs=ja-JP

  6. Import PO/POT files to Flies (Add --importpo to import existing translations from PO files. CAUTION: this may overwrite/delete translations stored in Zanata! Don't use --importpo if Zanata translation work has started):

    $ flies-publican upload --user admin --key 12345678901234567890123456789012 --src ./ --dst http://localhost:8080/flies/seam/resource/restv1/projects/p/sample-project/iterations/i/1.1/documents

  7. Translators open a document in Zanata and translate.

  8. Export PO/POT files from Zanata (Add --exportpot if POT files are needed):

    $ flies-publican download --user admin --key 12345678901234567890123456789012 --src http://localhost:8080/flies/seam/resource/restv1/projects/p/sample-project/iterations/i/1.1/documents --dst ./

Note that you will probably need to change the API key and Zanata URLs given above!