-----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@turnovfree.net jabber: stybla@jabber.turnovfree.net -----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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 v2 after some feedback from people of Fedora Project. On 01/28/11 20:10, Zdenek Styblik wrote: [...] ~~~ DRAFTv2 ~~~ # 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: Become translator It's pointless to copy-paste how-to from Fedora Project. How to become translator is described here - http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/... This might take some time not only to read, but to get processed. 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 !!! 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. 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 ~~~ Z. - -- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla@turnovfree.net jabber: stybla@jabber.turnovfree.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk1O7+EACgkQ8MreUbSH7ilDiACfccJfBzU5AB+JT/nZakFc4TXF UNYAnR50eKzuj74Eds1vsHzPO0a27Ceo =jmhm -----END PGP SIGNATURE-----
On 07/02/2011, at 6:00 AM, Zdenek Styblik wrote: <snip>
We are glad you've decided to help with localization/internationalization of libvirt. Before you do anything else, stop!
Good intention, but the wording of "Before you do anything else, stop!" could put some people off. I'd just remove that phrase, as the next one "Please, pay attention ..." gives the warning of "this stuff is important to read" anyway.
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.
It's not bad, but still not 100% clear. Probably slightly clarify it to mention ".po" files in the *libvirt po/ source code directory* (etc) just so there's no doubt at all. Also with the wording "... little sense to start translating them." it probably needs the word "directly" just after the "them".
Here are two ways how you can translate and contribute:
## Optimal way
1st step: Become translator
"Become a translator"
It's pointless to copy-paste how-to from Fedora Project.
"... from the Fedora Project". (the "the" is needed)
How to become translator is described here -
"How to become a translator ..."
http://docs.fedoraproject.org/en-US/Fedora_Contributor_Documentation/1/html/...
This might take some time not only to read, but to get processed.
"get processed" is kind of unclear, because in English it has a few potential meanings, including "for the person reading to understand". (hard to describe) Might be better to say something like: "This might take some time to read, and then to complete all of the instructions." <snip>
4th step: Upload translated file
!!! This point is still a mystery !!! Upload modified file via web interface.
Same here. We need advice from someone who's done it. :) The rest of the draft from "Alternate way" onwards sounds workable as it is. :) Regards and best wishes, Justin Clift
Justin, On 02/07/2011 11:59 AM, Justin Clift wrote: [...] comments are great, still - why haven't you implemented all of them then? :) Shouldn't be README/page created at this point, or not until "upload" thing is cleared out? Anyway, I'm going to merge these later on, still I don't know where-to except sending v3 to the list. So any of you better think of more comments, before we get at "spam" level with this drafting ... and before I do send another version :)
<snip>
4th step: Upload translated file
!!! This point is still a mystery !!! Upload modified file via web interface.
Same here. We need advice from someone who's done it. :)
Well, I'm a bit surprised no one from this list has experience with this one. From FP how-to: ~~~ SNIP ~~~ Submit Use the up-arrow icon labeled Send a translation for po/ja.po in the option area of each project, and click the browse button to locate your translated file. Click the Send button to commit your translated file. Interface displays the message File submitted successfully. If you receive an error or some other message, please post it to the Fedora Localization Project mailing list so it can be addressed. ~~~ SNIP ~~~ So, I would assume "upload via web interface" is valid, and I would avoid exact description how, since web interface can change and it's in how-to. Z. -- Zdenek Styblik Net/Linux admin OS TurnovFree.net email: stybla@turnovfree.net jabber: stybla@jabber.turnovfree.net
-----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/... 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@turnovfree.net jabber: stybla@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-----
participants (2)
-
Justin Clift -
Zdenek Styblik