-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, this is a draft of libvirt l10n/i18n translator's how-to. It is nowhere definite and it actually is meant ... It's practically summarized what we've talked about in last couple days. ~~~ DRAFT ~~~ # How-to libvirt l10n/i18n We are glad you've decided to help with localization/internationalization of libvirt. Before you do anything else, stop! Please, pay attention to following lines to save yourself from eventual pitfalls. '.po' files located in this directory are synchronized from Fedora Project[https://translate.fedoraproject.org/projects/p/libvirt/], thus it makes little sense to start translating them. Here are two ways how you can translate and contribute: ## Optimal way 1st step: Create a "Fedora Project" account: https://admin.fedoraproject.org/accounts/ (New Account, etc) 2nd step: Sign in to the libvirt transifex project https://translate.fedoraproject.org/projects/p/libvirt/ It uses the just created Fedora Project account 3rd step: "Request to be a translator" Once you've signed in with step 3, there's a button under the "Translation files" heading that says something like "Request to become a translator". Press that. This is going to take some time. 4th step: Download '.po' file '.po' file can be downloaded at https://translate.fedoraproject.org/projects/p/libvirt/ 5th step: Translate See translator's tools section. 6th step: Upload translated file !!! This point is still a mystery !!! Upload modified file via web interface. ## 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. ## 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 ~~~ Have a nice weekend, Z. - -- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla@xxxxxxxxxxxxxx jabber: stybla@xxxxxxxxxxxxxxxxxxxxx -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1DFJ4ACgkQ8MreUbSH7inLvQCeOg3CXKgxkdMz8EKlgQL8hSqK F6gAoI2LbWBPL2WQir0tW2wEjm5NeSlr =/2qM -----END PGP SIGNATURE----- -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list