From Fedora Project Wiki
(New page: = L10n Standard Operation Procedures = This page holds some SOPs and common processes the FLP uses. == Adding a project on Tx == * See: http://fedoraproject.org/wiki/L10N/FAQ#add-transi...)
 
No edit summary
Line 20: Line 20:


See: https://bugzilla.redhat.com/show_bug.cgi?id=454222#c1
See: https://bugzilla.redhat.com/show_bug.cgi?id=454222#c1
== String freeze break ==
1. Make sure it's a break. Go to the VCS, po directory, history (git) to see the history of the po directory. Somewhere there should be a commit that changed POT and/or the PO files.
1. Get the commit that changed the POT file, click on commitdiff. Check that strings have actually been added or existting strings have changed. If strings were just dropped, it's OK. If not, get the committer's contact info from the commit header.
1. Prepare the link for inclusion in the email. If the commit contains a lot of altered files, you can be more specific and link to one of the patches; eg. append #patch1 at the end of the file. ([http://git.fedorahosted.org/git/anaconda.git?p=anaconda.git;a=commit;h=ceab9f3c75df694ae6d7d2721c970bba8c359c61 example])
1. Write a [https://www.redhat.com/archives/fedora-trans-list/2008-October/msg00102.html string freeze break email]. It should include 1. a link to the commit message; 2. an example of string change; 3. the committer's contact info.

Revision as of 12:22, 15 October 2008

L10n Standard Operation Procedures

This page holds some SOPs and common processes the FLP uses.

Adding a project on Tx

Dummy commit, testing Transifex

Module home on Tx:
https://translate.fedoraproject.org/submit/module/MODULE_NAME


Problems with a module's i18n support

See: https://bugzilla.redhat.com/show_bug.cgi?id=454222#c1

String freeze break

1. Make sure it's a break. Go to the VCS, po directory, history (git) to see the history of the po directory. Somewhere there should be a commit that changed POT and/or the PO files.
1. Get the commit that changed the POT file, click on commitdiff. Check that strings have actually been added or existting strings have changed. If strings were just dropped, it's OK. If not, get the committer's contact info from the commit header.
1. Prepare the link for inclusion in the email. If the commit contains a lot of altered files, you can be more specific and link to one of the patches; eg. append #patch1 at the end of the file. (example)
1. Write a string freeze break email. It should include 1. a link to the commit message; 2. an example of string change; 3. the committer's contact info.