Hi!
The docs translation period starts in two months, it would be nice for the l10n teams with duplicate language resources on Transifex to have their resources justified.
From what requires action, the duplicate resources named as regional codes (like ru_RU or es_ES) hold our previous work. While the resources named as language identifiers (like ru or es) are out of sync or contain empty translations. It means that the project translators would lose progress if the project maintainers kill the duplicates now. The progressed modules need to be merged in the right place, where these would be available to the teams members afterwards. This is to be done by the l10n coordinators.
There's also a deadline to be set so we don't make the cleanup an endless process. August 15th, 2011, seems to be enough, in case someone's on vacation. That's 2 weeks before the docs translation period starts and about 1.5 month from now. Then we may ask the project maintainers to run a script to remove all those language resources.
If the Transifex stats [2] don't lie, the following teams are to be REMOVED: as_IN bg_BG bn_IN bs_BA ca_ES cz_CZ da_DK de_DE el_GR fa_IR fi_FI fr_FR gu_IN he_IL hi_IN hr_HR hu_HU id_ID is_IS it_IT jp_JP kn_IN ko_KR lt_LT lv_LV ml_IN ms_MY nb_NO nl_NL or_IN pa_IN pl_PL ru_RU sr_RS sr_RS@latin sk_SK sv_SE ta_IN te_IN uk_UA vi_VN
The following team is to be LEFT INTACT: zh_CN (as opposed to zh_TW and zh_HK)
The merging task can be accomplished by using the Transifex-client tool available in Fedora repository. You will need the language remapping capability introduced in version 0.5.2, which is currently in the testing repo. To use now, run: su -c "yum install transifex-client --enablerepo=*testing" or update using the testing repo: su -c "yum update transifex-client --enablerepo=*testing"
Please give the package transifex-client-0.5.2-1.fc15.noarch [1] good karma so it would land in the stable repo soon.
The procedure has been summarized before [3], there's also a complete manual to the tool [4]. It took me less time because I only downloaded one language I wanted. For instance, to update the Virtualization Guide I did:
1. configure the tool to use the chosen resource: a. create a folder, say, "transifex" in the home dir and cd into it b. [misha@pc transifex] $ tx init c. [misha@pc transifex] $ tx set --auto-remote https://www.transifex.net/projects/p/fedora-virtualization-guide/
2. pull the "ru_RU" translation modules: a. [misha@pc transifex] $ tx pull -l ru_RU
3. use language remapping to push the modules as "ru": a. remap the language by adding the line "lang_map = ru:ru_RU" to the main section of ~/transifex/.tx/config [5] b. [misha@pc transifex] $ tx push --translations -l ru
4. delete the local files
You may be able to do the whole docs collection at once using $ tx set --auto-remote https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ as soon as the corresponding ticket [6] is closed.
[1] https://admin.fedoraproject.org/updates/search/transifex [2] https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ [3] http://lists.fedoraproject.org/pipermail/docs/2011-June/013504.html [4] http://help.transifex.net/user-guide/client/devel.html#customizing-the-langu... [5] http://lists.fedoraproject.org/pipermail/docs/2011-June/013465.html [6] http://code.indifex.com/transifex-client/issue/17/broken-auto-remote-for-rel...
-- Best regards, Misha Shnurapet, Fedora Project Contributor Email: shnurapet AT fedoraproject.org, IRC: misha on freenode https://fedoraproject.org/wiki/shnurapet, GPG: 00217306
2011/7/1 Misha Shnurapet shnurapet@fedoraproject.org:
The procedure has been summarized before [3], there's also a complete manual to the tool [4]. It took me less time because I only downloaded one language I wanted. For instance, to update the Virtualization Guide I did:
- configure the tool to use the chosen resource:
... 4. delete the local files
You may be able to do the whole docs collection at once using $ tx set --auto-remote https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ as soon as the corresponding ticket [6] is closed. [6] http://code.indifex.com/transifex-client/issue/17/broken-auto-remote-for-rel...
Ticket fixed.
https://bitbucket.org/indifex/transifex-client/issue/17/broken-auto-remote-f...
To use, run the devel version or wait for the next stable one.
http://help.transifex.net/user-guide/client/index.html#development-version
Support for mass-deleting resources and translations of resources through the client should be available in the next release as well.
-d
Thanks Misha, this clears up a lot of the things we've been discussing over the past couple of weeks.
For guide maintainers: once we reach that August 15th deadline, we'll have two weeks to remap the language directories in the guide git repos to the new two-letter language identifiers used by Transifex.net. If I understand correctly, all we need to do is edit our .tx/config file as described in step 4 of Misha's list. Then, the next time we run 'tx pull', transifex-client should pull from the two-letter modules instead of the old four-letter ones (which probably won't be there anymore).
Regards, Nathan
On Sat, 2011-07-02 at 01:04 +0900, Misha Shnurapet wrote:
Hi!
The docs translation period starts in two months, it would be nice for the l10n teams with duplicate language resources on Transifex to have their resources justified.
From what requires action, the duplicate resources named as regional codes (like ru_RU or es_ES) hold our previous work. While the resources named as language identifiers (like ru or es) are out of sync or contain empty translations. It means that the project translators would lose progress if the project maintainers kill the duplicates now. The progressed modules need to be merged in the right place, where these would be available to the teams members afterwards. This is to be done by the l10n coordinators.
There's also a deadline to be set so we don't make the cleanup an endless process. August 15th, 2011, seems to be enough, in case someone's on vacation. That's 2 weeks before the docs translation period starts and about 1.5 month from now. Then we may ask the project maintainers to run a script to remove all those language resources.
If the Transifex stats [2] don't lie, the following teams are to be REMOVED: as_IN bg_BG bn_IN bs_BA ca_ES cz_CZ da_DK de_DE el_GR fa_IR fi_FI fr_FR gu_IN he_IL hi_IN hr_HR hu_HU id_ID is_IS it_IT jp_JP kn_IN ko_KR lt_LT lv_LV ml_IN ms_MY nb_NO nl_NL or_IN pa_IN pl_PL ru_RU sr_RS sr_RS@latin sk_SK sv_SE ta_IN te_IN uk_UA vi_VN
The following team is to be LEFT INTACT: zh_CN (as opposed to zh_TW and zh_HK)
The merging task can be accomplished by using the Transifex-client tool available in Fedora repository. You will need the language remapping capability introduced in version 0.5.2, which is currently in the testing repo. To use now, run: su -c "yum install transifex-client --enablerepo=*testing" or update using the testing repo: su -c "yum update transifex-client --enablerepo=*testing"
Please give the package transifex-client-0.5.2-1.fc15.noarch [1] good karma so it would land in the stable repo soon.
The procedure has been summarized before [3], there's also a complete manual to the tool [4]. It took me less time because I only downloaded one language I wanted. For instance, to update the Virtualization Guide I did:
- configure the tool to use the chosen resource:
a. create a folder, say, "transifex" in the home dir and cd into it b. [misha@pc transifex] $ tx init c. [misha@pc transifex] $ tx set --auto-remote https://www.transifex.net/projects/p/fedora-virtualization-guide/
- pull the "ru_RU" translation modules:
a. [misha@pc transifex] $ tx pull -l ru_RU
- use language remapping to push the modules as "ru":
a. remap the language by adding the line "lang_map = ru:ru_RU" to the main section of ~/transifex/.tx/config [5] b. [misha@pc transifex] $ tx push --translations -l ru
- delete the local files
You may be able to do the whole docs collection at once using $ tx set --auto-remote https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ as soon as the corresponding ticket [6] is closed.
[1] https://admin.fedoraproject.org/updates/search/transifex [2] https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ [3] http://lists.fedoraproject.org/pipermail/docs/2011-June/013504.html [4] http://help.transifex.net/user-guide/client/devel.html#customizing-the-langu... [5] http://lists.fedoraproject.org/pipermail/docs/2011-June/013465.html [6] http://code.indifex.com/transifex-client/issue/17/broken-auto-remote-for-rel...
-- Best regards, Misha Shnurapet, Fedora Project Contributor Email: shnurapet AT fedoraproject.org, IRC: misha on freenode https://fedoraproject.org/wiki/shnurapet, GPG: 00217306
On Wed, Jul 6, 2011 at 10:50 AM, Nathan Thomas nathan@afternoondust.co.uk wrote:
Thanks Misha, this clears up a lot of the things we've been discussing over the past couple of weeks.
For guide maintainers: once we reach that August 15th deadline, we'll have two weeks to remap the language directories in the guide git repos to the new two-letter language identifiers used by Transifex.net. If I understand correctly, all we need to do is edit our .tx/config file as described in step 4 of Misha's list. Then, the next time we run 'tx pull', transifex-client should pull from the two-letter modules instead of the old four-letter ones (which probably won't be there anymore).
Two clarifications: You'll need to delete the four-letter files from Tx. And, the next time you pull, the two-letter Tx files should be downloaded on top of the four-letter custom local names.
-d
Regards, Nathan
On Sat, 2011-07-02 at 01:04 +0900, Misha Shnurapet wrote:
Hi!
The docs translation period starts in two months, it would be nice for the l10n teams with duplicate language resources on Transifex to have their resources justified.
From what requires action, the duplicate resources named as regional codes
(like ru_RU or es_ES) hold our previous work. While the resources named as language identifiers (like ru or es) are out of sync or contain empty translations. It means that the project translators would lose progress if the project maintainers kill the duplicates now. The progressed modules need to be merged in the right place, where these would be available to the teams members afterwards. This is to be done by the l10n coordinators.
There's also a deadline to be set so we don't make the cleanup an endless process. August 15th, 2011, seems to be enough, in case someone's on vacation. That's 2 weeks before the docs translation period starts and about 1.5 month from now. Then we may ask the project maintainers to run a script to remove all those language resources.
If the Transifex stats [2] don't lie, the following teams are to be REMOVED: as_IN bg_BG bn_IN bs_BA ca_ES cz_CZ da_DK de_DE el_GR fa_IR fi_FI fr_FR gu_IN he_IL hi_IN hr_HR hu_HU id_ID is_IS it_IT jp_JP kn_IN ko_KR lt_LT lv_LV ml_IN ms_MY nb_NO nl_NL or_IN pa_IN pl_PL ru_RU sr_RS sr_RS@latin sk_SK sv_SE ta_IN te_IN uk_UA vi_VN
The following team is to be LEFT INTACT: zh_CN (as opposed to zh_TW and zh_HK)
The merging task can be accomplished by using the Transifex-client tool available in Fedora repository. You will need the language remapping capability introduced in version 0.5.2, which is currently in the testing repo. To use now, run: su -c "yum install transifex-client --enablerepo=*testing" or update using the testing repo: su -c "yum update transifex-client --enablerepo=*testing"
Please give the package transifex-client-0.5.2-1.fc15.noarch [1] good karma so it would land in the stable repo soon.
The procedure has been summarized before [3], there's also a complete manual to the tool [4]. It took me less time because I only downloaded one language I wanted. For instance, to update the Virtualization Guide I did:
- configure the tool to use the chosen resource:
a. create a folder, say, "transifex" in the home dir and cd into it b. [misha@pc transifex] $ tx init c. [misha@pc transifex] $ tx set --auto-remote https://www.transifex.net/projects/p/fedora-virtualization-guide/
- pull the "ru_RU" translation modules:
a. [misha@pc transifex] $ tx pull -l ru_RU
- use language remapping to push the modules as "ru":
a. remap the language by adding the line "lang_map = ru:ru_RU" to the main section of ~/transifex/.tx/config [5] b. [misha@pc transifex] $ tx push --translations -l ru
- delete the local files
You may be able to do the whole docs collection at once using $ tx set --auto-remote https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ as soon as the corresponding ticket [6] is closed.
[1] https://admin.fedoraproject.org/updates/search/transifex [2] https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ [3] http://lists.fedoraproject.org/pipermail/docs/2011-June/013504.html [4] http://help.transifex.net/user-guide/client/devel.html#customizing-the-langu... [5] http://lists.fedoraproject.org/pipermail/docs/2011-June/013465.html [6] http://code.indifex.com/transifex-client/issue/17/broken-auto-remote-for-rel...
-- Best regards, Misha Shnurapet, Fedora Project Contributor Email: shnurapet AT fedoraproject.org, IRC: misha on freenode https://fedoraproject.org/wiki/shnurapet, GPG: 00217306
-- docs mailing list docs@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
On Wed, 2011-07-06 at 11:17 +0300, Dimitris Glezos wrote:
On Wed, Jul 6, 2011 at 10:50 AM, Nathan Thomas nathan@afternoondust.co.uk wrote:
Thanks Misha, this clears up a lot of the things we've been discussing over the past couple of weeks.
For guide maintainers: once we reach that August 15th deadline, we'll have two weeks to remap the language directories in the guide git repos to the new two-letter language identifiers used by Transifex.net. If I understand correctly, all we need to do is edit our .tx/config file as described in step 4 of Misha's list. Then, the next time we run 'tx pull', transifex-client should pull from the two-letter modules instead of the old four-letter ones (which probably won't be there anymore).
Two clarifications: You'll need to delete the four-letter files from Tx.
That's using 'tx set --auto-remote' in the latest transifex-client, right?
Nathan
On শুক্রবার 01 জুলাই 2011 09:34 অপরাহ্ণ, Misha Shnurapet wrote:
The docs translation period starts in two months, it would be nice for the l10n teams with duplicate language resources on Transifex to have their resources justified.
...
If the Transifex stats [2] don't lie, the following teams are to be REMOVED:
��bn_IN
aka Bengali India is NOT to be removed. This is different from bn the same way pt_BR is different from pt.
Thanks Runa
same with ta_IN for Tamil India
Thanks and regards Richard Vijay pub 4096R/EE834823 2011-03-14 [expires: 2012-03-14] Key fingerprint = B02E D0DC 8689 CC3C 5D18 FD2E 9268 A3AF EE83 4823 sub 4096R/8CC5E914 2011-03-14 [expires: 2012-03-14] http://pgp.surfnet.nl:11371/pks/lookup?op=index&search=0xEE834823
On Wed, Jul 6, 2011 at 9:31 AM, Runa Bhattacharjee runab@fedoraproject.org wrote:
On শুক্রবার 01 জুলাই 2011 09:34 অপরাহ্ণ, Misha Shnurapet wrote:
The docs translation period starts in two months, it would be nice for the l10n teams with duplicate language resources on Transifex to have their resources justified.
...
If the Transifex stats [2] don't lie, the following teams are to be REMOVED:
��bn_IN
aka Bengali India is NOT to be removed. This is different from bn the same way pt_BR is different from pt.
Thanks Runa -- http://fedoraproject.org/wiki/User:Runab -- docs mailing list docs@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
On বুধবার 06 জুলাই 2011 02:32 অপরাহ্ণ, Richard Vijay wrote:
same with ta_IN for Tamil India
Please check with the Tamil coordinator for Fedora on this (Felix I).
https://www.transifex.net/projects/p/fedora/team/ta/
regards Runa
thanks Runa. I mailed ifelix few days back, yet to hear from him
Thanks and regards Richard Vijay pub 4096R/EE834823 2011-03-14 [expires: 2012-03-14] Key fingerprint = B02E D0DC 8689 CC3C 5D18 FD2E 9268 A3AF EE83 4823 sub 4096R/8CC5E914 2011-03-14 [expires: 2012-03-14] http://pgp.surfnet.nl:11371/pks/lookup?op=index&search=0xEE834823
On Wed, Jul 6, 2011 at 10:16 AM, Runa Bhattacharjee runab@fedoraproject.org wrote:
On বুধবার 06 জুলাই 2011 02:32 অপরাহ্ণ, Richard Vijay wrote:
same with ta_IN for Tamil India
Please check with the Tamil coordinator for Fedora on this (Felix I).
https://www.transifex.net/projects/p/fedora/team/ta/
regards Runa -- http://fedoraproject.org/wiki/User:Runab -- docs mailing list docs@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
2011/7/1 Misha Shnurapet shnurapet@fedoraproject.org:
Hi!
The docs translation period starts in two months, it would be nice for the l10n teams with duplicate language resources on Transifex to have their resources justified.
From what requires action, the duplicate resources named as regional codes (like ru_RU or es_ES) hold our previous work. While the resources named as language identifiers (like ru or es) are out of sync or contain empty translations. It means that the project translators would lose progress if the project maintainers kill the duplicates now. The progressed modules need to be merged in the right place, where these would be available to the teams members afterwards. This is to be done by the l10n coordinators.
There's also a deadline to be set so we don't make the cleanup an endless process. August 15th, 2011, seems to be enough, in case someone's on vacation. That's 2 weeks before the docs translation period starts and about 1.5 month from now. Then we may ask the project maintainers to run a script to remove all those language resources.
If the Transifex stats [2] don't lie, the following teams are to be REMOVED: as_IN bg_BG bn_IN bs_BA ca_ES cz_CZ da_DK de_DE el_GR fa_IR fi_FI fr_FR gu_IN he_IL hi_IN hr_HR hu_HU id_ID is_IS it_IT jp_JP kn_IN ko_KR lt_LT lv_LV ml_IN ms_MY nb_NO nl_NL or_IN pa_IN pl_PL ru_RU sr_RS sr_RS@latin sk_SK sv_SE ta_IN te_IN uk_UA vi_VN
The following team is to be LEFT INTACT: zh_CN (as opposed to zh_TW and zh_HK)
The merging task can be accomplished by using the Transifex-client tool available in Fedora repository. You will need the language remapping capability introduced in version 0.5.2, which is currently in the testing repo. To use now, run: su -c "yum install transifex-client --enablerepo=*testing" or update using the testing repo: su -c "yum update transifex-client --enablerepo=*testing"
Please give the package transifex-client-0.5.2-1.fc15.noarch [1] good karma so it would land in the stable repo soon.
The procedure has been summarized before [3], there's also a complete manual to the tool [4]. It took me less time because I only downloaded one language I wanted. For instance, to update the Virtualization Guide I did:
- configure the tool to use the chosen resource:
a. create a folder, say, "transifex" in the home dir and cd into it b. [misha@pc transifex] $ tx init c. [misha@pc transifex] $ tx set --auto-remote https://www.transifex.net/projects/p/fedora-virtualization-guide/
- pull the "ru_RU" translation modules:
a. [misha@pc transifex] $ tx pull -l ru_RU
- use language remapping to push the modules as "ru":
a. remap the language by adding the line "lang_map = ru:ru_RU" to the main section of ~/transifex/.tx/config [5] b. [misha@pc transifex] $ tx push --translations -l ru
- delete the local files
You may be able to do the whole docs collection at once using $ tx set --auto-remote https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ as soon as the corresponding ticket [6] is closed.
[1] https://admin.fedoraproject.org/updates/search/transifex [2] https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ [3] http://lists.fedoraproject.org/pipermail/docs/2011-June/013504.html [4] http://help.transifex.net/user-guide/client/devel.html#customizing-the-langu... [5] http://lists.fedoraproject.org/pipermail/docs/2011-June/013465.html [6] http://code.indifex.com/transifex-client/issue/17/broken-auto-remote-for-rel...
-- Best regards, Misha Shnurapet, Fedora Project Contributor Email: shnurapet AT fedoraproject.org, IRC: misha on freenode https://fedoraproject.org/wiki/shnurapet, GPG: 00217306
Hi, Thank you for this clear explanation. I've just done that for fr_FR who can be removed when you want (the fr team could not access it using transifex, no worries about further translations).
The updated tx client from the fedora repo was not able to download the whole project, I had to use the hg tree.
Kévin Raymond User:shaiton GPG-Key: A5BCB3A2
Hi.
This is to remind you about one week there's left for the L10N teams coordinators to sync the four-letter and the two-letter resources before the duplicate teams get removed from Transifex.
The transifex-client package to give the coordinators ability to remove the duplicate groups one by one isn't ready. AFAIK, most L10N teams coordinators have no *write* access to the duplicate teams because they have never been granted the coordinatorship. That means, should the tx-client package have arrived by August 15th, it would be useless without the project maintainers still involved. So let's just stick with the current deadline and then we can ask the project maintainers to remove all the duplicate teams at once.
According to the thread discussion, the following teams are to be REMOVED: as_IN bg_BG bs_BA ca_ES cz_CZ da_DK de_DE el_GR fa_IR fi_FI fr_FR gu_IN he_IL hi_IN hr_HR hu_HU id_ID is_IS it_IT jp_JP kn_IN ko_KR lt_LT lv_LV ml_IN ms_MY nb_NO nl_NL or_IN pa_IN pl_PL ru_RU sr_RS sr_RS@latin sk_SK sv_SE ta_IN te_IN uk_UA vi_VN
The following teams are to be LEFT INTACT: bn_IN (is different from bn) zh_CN (as opposed to zh_TW and zh_HK)
I hereby include the original message in case someone has been on vacation and missed it. There are step-by-step instructions given.
02.07.2011, 01:04, "Misha Shnurapet" shnurapet@fedoraproject.org:
Hi!
The docs translation period starts in two months, it would be nice for the l10n teams with duplicate language resources on Transifex to have their resources justified.
From what requires action, the duplicate resources named as regional codes (like ru_RU or es_ES) hold our previous work. While the resources named as language identifiers (like ru or es) are out of sync or contain empty translations. It means that the project translators would lose progress if the project maintainers kill the duplicates now. The progressed modules need to be merged in the right place, where these would be available to the teams members afterwards. This is to be done by the l10n coordinators.
There's also a deadline to be set so we don't make the cleanup an endless process. August 15th, 2011, seems to be enough, in case someone's on vacation. That's 2 weeks before the docs translation period starts and about 1.5 month from now. Then we may ask the project maintainers to run a script to remove all those language resources.
The merging task can be accomplished by using the Transifex-client tool available in Fedora repository. You will need the language remapping capability introduced in version 0.5.2, which is currently in the testing repo. To use now, run: su -c "yum install transifex-client --enablerepo=*testing" or update using the testing repo: su -c "yum update transifex-client --enablerepo=*testing"
Please give the package transifex-client-0.5.2-1.fc15.noarch [1] good karma so it would land in the stable repo soon.
The procedure has been summarized before [3], there's also a complete manual to the tool [4]. It took me less time because I only downloaded one language I wanted. For instance, to update the Virtualization Guide I did:
- configure the tool to use the chosen resource:
a. create a folder, say, "transifex" in the home dir and cd into it b. [misha@pc transifex] $ tx init c. [misha@pc transifex] $ tx set --auto-remote https://www.transifex.net/projects/p/fedora-virtualization-guide/
- pull the "ru_RU" translation modules:
a. [misha@pc transifex] $ tx pull -l ru_RU
- use language remapping to push the modules as "ru":
a. remap the language by adding the line "lang_map = ru:ru_RU" to the main section of ~/transifex/.tx/config [5] b. [misha@pc transifex] $ tx push --translations -l ru
- delete the local files
You may be able to do the whole docs collection at once using $ tx set --auto-remote https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ as soon as the corresponding ticket [6] is closed.
[1] https://admin.fedoraproject.org/updates/search/transifex [2] https://www.transifex.net/projects/p/fedora/r/fedora-15-docs/ [3] http://lists.fedoraproject.org/pipermail/docs/2011-June/013504.html [4] http://help.transifex.net/user-guide/client/devel.html#customizing-the-langu... [5] http://lists.fedoraproject.org/pipermail/docs/2011-June/013465.html [6] http://code.indifex.com/transifex-client/issue/17/broken-auto-remote-for-rel...
2011/8/9 Misha Shnurapet shnurapet@fedoraproject.org:
This is to remind you about one week there's left for the L10N teams coordinators to sync the four-letter and the two-letter resources before the duplicate teams get removed from Transifex.
There are a bunch of files on Tx which do not have a team associated with them. Here's a more accurate list of the actual teams which exist and will be removed.
as_IN bg_BG bs_BA ca_ES cz_CZ - TEAM EXISTS. TO BE REMOVED da_DK de_DE el_GR fa_IR - TEAM EXISTS. TO BE REMOVED fi_FI fr_FR gu_IN he_IL hi_IN hr_HR - hu_HU id_ID is_IS it_IT - TEAM EXISTS. TO BE REMOVED jp_JP - TEAM EXISTS. TO BE REMOVED kn_IN ko_KR lt_LT - TEAM EXISTS. TO BE REMOVED lv_LV - TEAM EXISTS. TO BE REMOVED ml_IN ms_MY nb_NO nl_NL or_IN pa_IN pl_PL ru_RU - TEAM EXISTS. TO BE REMOVED sr_RS sr_RS@latin sk_SK sv_SE ta_IN - TEAM EXISTS. TO BE REMOVED te_IN uk_UA - TEAM EXISTS. TO BE REMOVED vi_VN
To Docs owners:
Is it clear on what should be done from your side to correctly assign your files to the right translation teams?
We intentionally started this thread early so that there is enough time to make this actually work. Now is the time to ask questions and proceed in making your L10n work, not after the release is out.
-d
On Tue, 2011-08-09 at 10:00 +0300, Dimitris Glezos wrote:
2011/8/9 Misha Shnurapet shnurapet@fedoraproject.org:
This is to remind you about one week there's left for the L10N teams coordinators to sync the four-letter and the two-letter resources before the duplicate teams get removed from Transifex.
There are a bunch of files on Tx which do not have a team associated with them. Here's a more accurate list of the actual teams which exist and will be removed.
as_IN bg_BG bs_BA ca_ES cz_CZ - TEAM EXISTS. TO BE REMOVED da_DK de_DE el_GR fa_IR - TEAM EXISTS. TO BE REMOVED fi_FI fr_FR gu_IN he_IL hi_IN hr_HR - hu_HU id_ID is_IS it_IT - TEAM EXISTS. TO BE REMOVED jp_JP - TEAM EXISTS. TO BE REMOVED kn_IN ko_KR lt_LT - TEAM EXISTS. TO BE REMOVED lv_LV - TEAM EXISTS. TO BE REMOVED ml_IN ms_MY nb_NO nl_NL or_IN pa_IN pl_PL ru_RU - TEAM EXISTS. TO BE REMOVED sr_RS sr_RS@latin sk_SK sv_SE ta_IN - TEAM EXISTS. TO BE REMOVED te_IN uk_UA - TEAM EXISTS. TO BE REMOVED vi_VN
To Docs owners:
Is it clear on what should be done from your side to correctly assign your files to the right translation teams?
We intentionally started this thread early so that there is enough time to make this actually work. Now is the time to ask questions and proceed in making your L10n work, not after the release is out.
-d
I've been switching the Live Image Guide to track the two-letter teams as and when they appear, seems to be working ok. Is there anything you need us guide owners to do to remove the old four-letter teams?
Guide owners, if you don't think you're going to get round to looking at this before the 16th give me a shout - I have a little spare time over the next week, so should be able to give you a hand.
Nathan
On Wed, Aug 10, 2011 at 10:23 PM, Nathan Thomas nathan@afternoondust.co.uk wrote:
To Docs owners:
Is it clear on what should be done from your side to correctly assign your files to the right translation teams?
I've been switching the Live Image Guide to track the two-letter teams as and when they appear, seems to be working ok. Is there anything you need us guide owners to do to remove the old four-letter teams?
If you pushed your files to the correct two-letter teams, you can go on and delete the other ones. Click on the resource-language & there should be a 'Delete translations' button. Alternatively, you can use the devel version of the transifex client:
$ hg clone http://code.indifex.com/transifex-client $ cd transifex-client $ sudo python setup.py install $ tx delete --help $ tx delete -r project.resource -l <lang_code>
Guide owners, if you don't think you're going to get round to looking at this before the 16th give me a shout - I have a little spare time over the next week, so should be able to give you a hand.
Thanks Nathan!
-d
On Sat, 2011-08-13 at 01:20 +0300, Dimitris Glezos wrote:
On Wed, Aug 10, 2011 at 10:23 PM, Nathan Thomas nathan@afternoondust.co.uk wrote:
To Docs owners:
Is it clear on what should be done from your side to correctly assign your files to the right translation teams?
I've been switching the Live Image Guide to track the two-letter teams as and when they appear, seems to be working ok. Is there anything you need us guide owners to do to remove the old four-letter teams?
If you pushed your files to the correct two-letter teams, you can go on and delete the other ones. Click on the resource-language & there should be a 'Delete translations' button. Alternatively, you can use the devel version of the transifex client:
$ hg clone http://code.indifex.com/transifex-client $ cd transifex-client $ sudo python setup.py install $ tx delete --help $ tx delete -r project.resource -l <lang_code>
If I click on a resource-language in the 'Translation Statistics' list on https://www.transifex.net/projects/p/fedora-readme-live-images/r/all-resourc... , I don't see an option to delete translations. Am I looking in the wrong place? Does it matter that access control is outsourced and that the project is re-using Fedora Project teams instead of having its own teams?
Thanks, Nathan
On Sun, Aug 14, 2011 at 3:09 PM, Nathan Thomas nathan@afternoondust.co.uk wrote:
On Sat, 2011-08-13 at 01:20 +0300, Dimitris Glezos wrote:
On Wed, Aug 10, 2011 at 10:23 PM, Nathan Thomas nathan@afternoondust.co.uk wrote:
To Docs owners:
Is it clear on what should be done from your side to correctly assign your files to the right translation teams?
I've been switching the Live Image Guide to track the two-letter teams as and when they appear, seems to be working ok. Is there anything you need us guide owners to do to remove the old four-letter teams?
If you pushed your files to the correct two-letter teams, you can go on and delete the other ones. Click on the resource-language & there should be a 'Delete translations' button. Alternatively, you can use the devel version of the transifex client:
$ hg clone http://code.indifex.com/transifex-client $ cd transifex-client $ sudo python setup.py install $ tx delete --help $ tx delete -r project.resource -l <lang_code>
If I click on a resource-language in the 'Translation Statistics' list on https://www.transifex.net/projects/p/fedora-readme-live-images/r/all-resourc... , I don't see an option to delete translations. Am I looking in the wrong place? Does it matter that access control is outsourced and that the project is re-using Fedora Project teams instead of having its own teams?
You should be able to see "Delete translations" in the popup when you click on a resource-language, ie. any row of this table for example:
https://www.transifex.net/projects/p/fedora-readme-live-images/r/all-resourc...
-d
23.08.2011, 17:22, "Dimitris Glezos" glezos@indifex.com:
You should be able to see "Delete translations" in the popup when you click on a resource-language, ie. any row of this table for example:
https://www.transifex.net/projects/p/fedora-readme-live-images/r/all-resourc...
I'm sorry, but I don't see: http://shnurapet.fedorapeople.org/txdelete.png
2011/8/23 Misha Shnurapet shnurapet@fedoraproject.org:
23.08.2011, 17:22, "Dimitris Glezos" glezos@indifex.com:
You should be able to see "Delete translations" in the popup when you click on a resource-language, ie. any row of this table for example:
https://www.transifex.net/projects/p/fedora-readme-live-images/r/all-resourc...
I'm sorry, but I don't see: http://shnurapet.fedorapeople.org/txdelete.png
Only team members & maintainers can see it. ru_RU team has been removed. =)
-d
You should be able to see "Delete translations" in the popup when you click on a resource-language, ie. any row of this table for example:
https://www.transifex.net/projects/p/fedora-readme-live-images/r/all-resourc...
-d
Ok, so I just delete the resources for the old four-letter teams on Transifex.net, I don't delete anything from my guide git repo?
Sorry to be so slow on the uptake here, but I don't want to mess up anyone's translations!
Thanks, Nathan
On Fri, Aug 26, 2011 at 8:50 PM, Nathan Thomas nathan@afternoondust.co.uk wrote:
You should be able to see "Delete translations" in the popup when you click on a resource-language, ie. any row of this table for example:
https://www.transifex.net/projects/p/fedora-readme-live-images/r/all-resourc...
Ok, so I just delete the resources for the old four-letter teams on Transifex.net, I don't delete anything from my guide git repo?
Yup. Files on Transifex should match teams. You can have any files you want locally, and, if you have setup correctly your Transifex client, the next time you pull/push, the client will "rename" (map) local files (eg. it_IT) to remote ones (eg. it).
-d
Ok this is done now for the Live Image Guide and the Release Notes.
Nathan
-
Dimitris Glezos -
Kévin Raymond -
Misha Shnurapet -
Nathan Thomas -
Richard Vijay -
Runa Bhattacharjee