[libvirt] draft ~ l10n/i18n

[Zdenek Styblik]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

v3 with comments and fixes from Justin.

Justin, please, check it.

On 02/06/11 20:00, Zdenek Styblik wrote:
[...]

~~~ DRAFTv2 ~~~
# How-to libvirt l10n/i18n

We are glad you've decided to help with
localization/internationalization of libvirt. Please, pay attention to
following lines to save yourself from eventual
pitfalls.

'.po' files located in '<libvirt-source>/po' directory are synchronized
from Fedora
Project[https://translate.fedoraproject.org/projects/p/libvirt/], thus
there is little sense to start translating them directly.

Here are two ways how you can translate and contribute:

## Optimal way

1st step: Become a translator

  It's pointless to copy-paste how-to from Fedora Project.
  How to become a translator is described here -

http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/Translation_Quick_Start_Guide/index.html

  Reading the guide, completing all instructions and getting an approval
to translate libvirt is going to take some time. Be prepared for it!

  In a short:
  * register with Fedora Project
  * create page about yourself and introduce yourself around
  * ask to be a translator
  * and you should be done

2nd step: Download '.po' file

  '.po' file can be downloaded at
https://translate.fedoraproject.org/projects/p/libvirt/


3rd step: Translate

   See translator's tools section.


4th step: Upload translated file

  Upload modified file via web interface at Fedora Project site.
  Exactly how to upload modified .po file is described in Quick Start
Guide mentioned above.


## Alternate way

If for some reason you don't want to or can't register at Fedora
Project, you still can translate and contribute to libvirt.

1st step: Get '.po' file

  Download '.po' file from
https://translate.fedoraproject.org/projects/p/libvirt/ with language
you're going to translate to.
  Make a backup copy of it

2nd step: Translate

  See translator's tools section.

3rd step: Make a diff

  Make a % diff; of the original file and the one you've translated.

  eg. % diff -urN lang.po.org lang.po > lang.po.patch;

  Send patch file back to mailing-list and somebody from the team
  is going to push it at Fedora Project.

  Why diff? Because it's easier to validate the work you've done,
  solve eventual conflicts etc.

However, this approach has its downsides. First is it brings more
workload to libvirt team, second is '.po' file can change in the
meantime, because you are not able to "lock it" while you're working at
translations. Also, be prepared for rejection doing things this way.


## Translator's tools

  * KAider KDE4 ~ seems to be dead
  * gtranslator ~ http://projects.gnome.org/gtranslator/
  * poedit ~ http://www.poedit.net/

In case '.po' file in upstream got changed and you need to sync your
current work with upstream, you can try your luck with tool written in
Perl > http://www.zeratul.org/git/?p=scripts/perl/po-sync/.git;a=summary

~~~ DRAFT ~~~

Mistakes/ideas:
~~~
1st step: Become a translator *with Fedora Project* ? ~~~ well, it's
translator with FPj after all

getting an approval ? ~~~ an ?

Exactly how to upload modified .po file is described in Quick Start
Guide mentioned above. ~~~ better wording is required?
~~~

Implement/fix these without issuing another version of this draft :)

Regards,
Zdenek

- -- 
Zdenek Styblik
Net/Linux admin
OS TurnovFree.net
email: stybla at turnovfree.net
jabber: stybla at jabber.turnovfree.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk1QSDMACgkQ8MreUbSH7ikWbwCeIvYt0qpbn9IpmIg8y6gdja3s
o4wAmgIaH8JacXPism4lFpyz1G389lf/
=AxmZ
-----END PGP SIGNATURE-----