Hi there,
Since our migration to transifex.net, some teams have lost their translations because a new team was created (thanks to language mapping in transifex.net).
There are still some project that need to be merged. I've written a script[1] used to parse all guides at TXN, and print the language code which have translations but are not associated to any teams. Please find attached the results. Limitations: - it was against the fedora-docs release only, not against all docs! I could have used an other script for that. I have it around but I would prefer our guides to be on the fedora-docs release. This refers to[3]. Should I add all in this fedora-docs release? I think so, but we never finished that…
Should I add all in this fedora-docs release? I think so, but we never finished that…
There could be an other way, but I think that I've more than needed. This list should be checked with the Misha's one[2].
we really need the maintainers to act! Some guides are completly translated but using the wrong language code, we can't publish nor re-use translations.
I think we need a clear list of which l_code have to be merged in which one, the thread [2] should helps.
@maintainers, please ask if you need help for that!
[1] https://gitorious.org/tiny-scripts/transifex/trees/master/check_teams [2] http://lists.fedoraproject.org/pipermail/docs/2011-August/013611.html [3] http://lists.fedoraproject.org/pipermail/docs/2012-March/014116.html
Potentially useful:
Transifex Python library: https://github.com/transifex/transifex-python-library
-d
On Fri, May 18, 2012 at 3:14 PM, Kévin Raymond shaiton@fedoraproject.org wrote:
Hi there,
Since our migration to transifex.net, some teams have lost their translations because a new team was created (thanks to language mapping in transifex.net).
There are still some project that need to be merged. I've written a script[1] used to parse all guides at TXN, and print the language code which have translations but are not associated to any teams. Please find attached the results. Limitations: - it was against the fedora-docs release only, not against all docs! I could have used an other script for that. I have it around but I would prefer our guides to be on the fedora-docs release. This refers to[3]. Should I add all in this fedora-docs release? I think so, but we never finished that…
Should I add all in this fedora-docs release? I think so, but we never finished that…
There could be an other way, but I think that I've more than needed. This list should be checked with the Misha's one[2].
we really need the maintainers to act! Some guides are completly translated but using the wrong language code, we can't publish nor re-use translations.
I think we need a clear list of which l_code have to be merged in which one, the thread [2] should helps.
@maintainers, please ask if you need help for that!
[1] https://gitorious.org/tiny-scripts/transifex/trees/master/check_teams [2] http://lists.fedoraproject.org/pipermail/docs/2011-August/013611.html [3] http://lists.fedoraproject.org/pipermail/docs/2012-March/014116.html
-- Kévin Raymond (Shaiton)
-- trans mailing list trans@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/trans
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi:
I have attempted to do this for the Musicians' Guide for the Fedora 16 revision.[1] I will not publish this Guide in English for Fedora 17 because I haven't made many changes.
Could somebody please confirm that everything is correct?
Thanks, Christopher.
[1] https://fedora.transifex.net/projects/p/fedora-musicians-guide/
On 05/18/2012 06:14 PM, Kévin Raymond wrote:
Hi there,
Since our migration to transifex.net, some teams have lost their translations because a new team was created (thanks to language mapping in transifex.net).
There are still some project that need to be merged. I've written a script[1] used to parse all guides at TXN, and print the language code which have translations but are not associated to any teams. Please find attached the results. Limitations: - it was against the fedora-docs release only, not against all docs! I could have used an other script for that. I have it around but I would prefer our guides to be on the fedora-docs release. This refers to[3]. Should I add all in this fedora-docs release? I think so, but we never finished that…
Should I add all in this fedora-docs release? I think so, but we never finished that…
There could be an other way, but I think that I've more than needed. This list should be checked with the Misha's one[2].
we really need the maintainers to act! Some guides are completly translated but using the wrong language code, we can't publish nor re-use translations.
I think we need a clear list of which l_code have to be merged in which one, the thread [2] should helps.
@maintainers, please ask if you need help for that!
[1] https://gitorious.org/tiny-scripts/transifex/trees/master/check_teams
[2] http://lists.fedoraproject.org/pipermail/docs/2011-August/013611.html
[3] http://lists.fedoraproject.org/pipermail/docs/2012-March/014116.html
Hi Christopher,
On Sat, 19 May 2012 18:31:27 -0400 "Christopher R. Antila" crantila@fedoraproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi:
I have attempted to do this for the Musicians' Guide for the Fedora 16 revision.[1] I will not publish this Guide in English for Fedora 17 because I haven't made many changes.
Could somebody please confirm that everything is correct?
Thanks, Christopher.
[1] https://fedora.transifex.net/projects/p/fedora-musicians-guide/
When you look at the list of languages, you can see that many of them have "(no team yet)". Basically, these are the duplicated lang codes that should be merged into the correct ones.
For your guide, this should mean just merging Japanese, Dutch, Russian and Ukrainian, and delete the rest of the lang codes as there are apparently no translations into other languages available for your guide.
As I said during today's meeting, feel free to ping me on #fedora-docs if you need any help.
Cheers,
For your guide, this should mean just merging Japanese, Dutch, Russian and Ukrainian, and delete the rest of the lang codes as there are apparently no translations into other languages available for your guide.
The only way to delete a language team, is to use the transifex-client, on each projects. tx delete -l <lang>
There is no way back, only on your repo… We need to do it on each merged projects… Maintainers… be happy :)
Op 19-05-12 00:14, Kévin Raymond schreef:
Hi there,
Since our migration to transifex.net, some teams have lost their translations because a new team was created (thanks to language mapping in transifex.net).
There are still some project that need to be merged. I've written a script[1] used to parse all guides at TXN, and print the language code which have translations but are not associated to any teams. Please find attached the results. Limitations:
it was against the fedora-docs release only, not against all docs! I could have used an other script for that. I have it around but I would prefer our guides to be on the fedora-docs release. This refers to[3]. Should I add all in this fedora-docs release? I think so, but we never finished that…
Should I add all in this fedora-docs release? I think so, but we never finished that…
There could be an other way, but I think that I've more than needed. This list should be checked with the Misha's one[2].
we really need the maintainers to act! Some guides are completly translated but using the wrong language code, we can't publish nor re-use translations.
I think we need a clear list of which l_code have to be merged in which one, the thread [2] should helps.
@maintainers, please ask if you need help for that!
[1] https://gitorious.org/tiny-scripts/transifex/trees/master/check_teams [2] http://lists.fedoraproject.org/pipermail/docs/2011-August/013611.html [3] http://lists.fedoraproject.org/pipermail/docs/2012-March/014116.html
What about the Security Guide? Still actual info, imho.
regards Richard
Hi all,
I told you by Saturday, here we are! (At least in my timezone)
I've updated my script[1] (thanks for your link Glezos, will use it next time!), in order to give you more precise info. Moreover, it parses now all guides outsourcing the Fedora Hub (and not only the fedora-docs release which is incomplete).
@translators, - please check that what I am telling is the true concerning your language (the one that needs to be merged on which one). - do sr@latin has to be merged in sr-Latn-RS? - I found the team ms_MY with some translations (look for [EE] entries), on which team should it be merged? ms appear to not exist yet. - Once merged, the old teams would be removed.
@maintainers, - check your guide, and please merge the language code on the left side, to the one on the right side, which is used by our translators. (If nothing is written bellow your guide, that means everything alright from my side). The steps are described at the end of the README file at[2].
Bellow is the output. Read it the following way: "pt_PT:pt 84% > 0% NEED merge" means that the language code pt_PT is translated at 84% for one file (not the whole guide, I am checking only the first file with more translations than the right team), and I request a merge on the team pt, where the same file is currently translated at 0%.
=== fedora-musicians-guide nl_NL:nl 100% > 0% NEED merge Maintainer(s) crantila rlandmann neb pmkovar nathant See project at: https://www.transifex.net/projects/p/fedora-musicians-guide
=== fedora-power-management-guide fr_FR:fr 100% > 0% NEED merge it_IT:it 100% > 0% NEED merge uk_UA:uk 68% > 0% NEED merge nl_NL:nl 100% > 0% NEED merge ja_JP:ja 100% > 0% NEED merge es_ES:es 100% > 0% NEED merge ru_RU:ru 100% > 0% NEED merge ko_KR:ko 94% > 0% NEED merge de_DE:de 94% > 0% NEED merge pl_PL:pl 31% > 0% NEED merge ca_ES:ca 100% > 0% NEED merge Maintainer(s) rlandmann neb pmkovar nathant See project at: https://www.transifex.net/projects/p/fedora-power-management-guide
=== resource-management-guide === fedora-respin-guide === fedora-rpm-guide === fedora-security-guide === fedora-selinux-guide === software-collections-guide
=== fedora-install-guide as_IN:as 100% > 0% NEED merge bg_BG:bg 100% > 0% NEED merge ca_ES:ca 100% > 0% NEED merge ta_IN:ta 100% > 0% NEED merge ml_IN:ml 100% > 0% NEED merge kn_IN:kn 100% > 0% NEED merge ru_RU:ru 100% > 0% NEED merge mr_IN:mr 100% > 0% NEED merge pa_IN:pa 100% > 0% NEED merge or_IN:or 100% > 0% NEED merge ko_KR:ko 100% > 0% NEED merge te_IN:te 100% > 0% NEED merge it_IT:it 100% > 0% NEED merge sr_RS:sr 100% > 0% NEED merge gu_IN:gu 100% > 0% NEED merge id_ID:id 100% > 0% NEED merge pt_PT:pt 100% > 0% NEED merge hi_IN:hi 100% > 0% NEED merge uk_UA:uk 100% > 0% NEED merge de_DE:de 100% > 0% NEED merge fa_IR:fa 100% > 0% NEED merge si_LK:si 100% > 0% NEED merge es_ES:es 100% > 0% NEED merge fr_FR:fr 16% > 0% NEED merge sv_SE:sv 34% > 0% NEED merge lv_LV:lv 8% > 0% NEED merge pl_PL:pl 33% > 0% NEED merge el_GR:el 8% > 0% NEED merge Maintainer(s) rlandmann neb rforlot zoglesby alick ke4qqq pmkovar bcotton See project at: https://www.transifex.net/projects/p/fedora-install-guide
=== fedora-ins-quick-start-guide ta_IN:ta 100% > 0% NEED merge sv_SE:sv 100% > 0% NEED merge fr_FR:fr 100% > 0% NEED merge sr_RS:sr 100% > 0% NEED merge kn_IN:kn 100% > 0% NEED merge ru_RU:ru 100% > 0% NEED merge gu_IN:gu 100% > 0% NEED merge as_IN:as 100% > 0% NEED merge hi_IN:hi 100% > 0% NEED merge pt_PT:pt 100% > 0% NEED merge mr_IN:mr 100% > 0% NEED merge id_ID:id 100% > 0% NEED merge pa_IN:pa 100% > 0% NEED merge te_IN:te 100% > 0% NEED merge uk_UA:uk 100% > 0% NEED merge or_IN:or 100% > 0% NEED merge ko_KR:ko 100% > 0% NEED merge de_DE:de 100% > 0% NEED merge pl_PL:pl 100% > 0% NEED merge ml_IN:ml 33% > 0% NEED merge ca_ES:ca 33% > 0% NEED merge si_LK:si 33% > 0% NEED merge el_GR:el 100% > 0% NEED merge fa_IR:fa 66% > 0% NEED merge fi_FI:fi 25% > 0% NEED merge nb_NO:nb 25% > 0% NEED merge hu_HU:hu 25% > 0% NEED merge lv_LV:lv 100% > 0% NEED merge da_DK:da 100% > 0% NEED merge Maintainer(s) rlandmann neb nathant bcotton shaiton pmkovar See project at: https://www.transifex.net/projects/p/fedora-ins-quick-start-guide
=== fedora-elections-guide === fedora-cloud-guide === fedora-amateur-radio-guide
=== fedora-accessibility-guide sr_RS:sr 60% > 0% NEED merge [EE] Could not get the corresponding team for sr@latin pl_PL:pl 100% > 0% NEED merge de_DE:de 23% > 0% NEED merge pt_PT:pt 70% > 50% NEED merge Maintainer(s) rlandmann neb pmkovar nathant Sparks See project at: https://www.transifex.net/projects/p/fedora-accessibility-guide
=== fedora-wireless-guide
=== fedora-virtualization-guide ko_KR:ko 77% > 0% NEED merge de_DE:de 77% > 0% NEED merge Maintainer(s) rlandmann neb pmkovar nathant See project at: https://www.transifex.net/projects/p/fedora-virtualization-guide
=== fedora-user-guide
=== translation-quick-start-guide pt_PT:pt 84% > 0% NEED merge sr_RS:sr 40% > 0% NEED merge nl_NL:nl 84% > 0% NEED merge el_GR:el 66% > 0% NEED merge id_ID:id 21% > 0% NEED merge pa_IN:pa 40% > 0% NEED merge [EE] The team in which to merge is not part of our teams ms for ms_MY ko_KR:ko 66% > 0% NEED merge de_DE:de 91% > 0% NEED merge bs_BA:bs 42% > 0% NEED merge fa_IR:fa 96% > 0% NEED merge hu_HU:hu 57% > 0% NEED merge sv_SE:sv 8% > 0% NEED merge pl_PL:pl 100% > 0% NEED merge [EE] The team in which to merge is not part of our teams ms for ms_MY Maintainer(s) rlandmann neb raven glezos pmkovar fab noriko nathant See project at: https://www.transifex.net/projects/p/translation-quick-start-guide
=== system-administrators-guide
=== fedora-storage-admin-guide fr_FR:fr 100% > 0% NEED merge it_IT:it 100% > 0% NEED merge nl_NL:nl 100% > 0% NEED merge ja_JP:ja 80% > 0% NEED merge es_ES:es 60% > 0% NEED merge ru_RU:ru 60% > 0% NEED merge Maintainer(s) rlandmann neb pmkovar nathant See project at: https://www.transifex.net/projects/p/fedora-storage-admin-guide
=== fedora-software-mgmt-guide
Unknown teams are: sr@latin
[1] https://gitorious.org/tiny-scripts/transifex/blobs/master/check_teams/check_... [2] https://gitorious.org/tiny-scripts/transifex/blobs/master/check_teams/README
On Sat, Jun 9, 2012 at 10:30 PM, Kévin Raymond shaiton@fedoraproject.org wrote:
- do sr@latin has to be merged in sr-Latn-RS?
Correct
Thanks, Miloš
Le dimanche 10 juin 2012 à 00:00:12 (+0100), Miloš Komarčević a écrit :
On Sat, Jun 9, 2012 at 10:30 PM, Kévin Raymond shaiton@fedoraproject.org wrote:
- do sr@latin has to be merged in sr-Latn-RS?
Correct
Ok, but I've found the merge needed only in fedora-accessibility-guide, but sr-Latn-RS does not exists, some clarification are probably needed.
On Sun, Jun 10, 2012 at 1:00 AM, Kévin Raymond shaiton@fedoraproject.org wrote:
Ok, but I've found the merge needed only in fedora-accessibility-guide, but sr-Latn-RS does not exists, some clarification are probably needed.
IMHO, we should only have 'sr' and 'sr-Latn' (country qualifiers are surplus).
sr-Latn should have identical team members, or just the cooridnator(s) who will take care of syncing it to sr (transliteration is done semi-automatically, and sr is to be considered the source).
sr@latin and others should alias to sr-Latn
M
2012/6/10 Miloš Komarčević kmilos@gmail.com:
On Sun, Jun 10, 2012 at 1:00 AM, Kévin Raymond shaiton@fedoraproject.org wrote:
Ok, but I've found the merge needed only in fedora-accessibility-guide, but sr-Latn-RS does not exists, some clarification are probably needed.
IMHO, we should only have 'sr' and 'sr-Latn' (country qualifiers are surplus).
sr-Latn should have identical team members, or just the cooridnator(s) who will take care of syncing it to sr (transliteration is done semi-automatically, and sr is to be considered the source).
sr@latin and others should alias to sr-Latn
Actually sr@latin is the correct code and sr-Latn should be an alias to it. It's a convention used in glibc, and therefore in all the other software. You can see this, for example, in GNOME Serbian files, like GTK+ etc.
On Mon, Jun 11, 2012 at 9:56 PM, Piotr Drąg piotrdrag@gmail.com wrote:
Actually sr@latin is the correct code and sr-Latn should be an alias to it. It's a convention used in glibc, and therefore in all the other software. You can see this, for example, in GNOME Serbian files, like GTK+ etc.
I know, but this is only because of glibc (GNOME and others really pushed for something else), and is wrong IMHO. The @ POSIX locale modifiers were never intended to be used for different scripts (a wholly new locale), but to _modify_ an exisitng locale to create a _variant_ (de_DE@euro etc.)
Glibc is, with due respect, stuck behind times when it comes to i18n and needs to jump on the BCP47 wagon. So does Transifex.
M
2012/6/11 Miloš Komarčević kmilos@gmail.com:
I know, but this is only because of glibc (GNOME and others really pushed for something else), and is wrong IMHO. The @ POSIX locale modifiers were never intended to be used for different scripts (a wholly new locale), but to _modify_ an exisitng locale to create a _variant_ (de_DE@euro etc.)
Glibc is, with due respect, stuck behind times when it comes to i18n and needs to jump on the BCP47 wagon. So does Transifex.
Well, in theory you're probably right, but I think it's important to stay compatible with our software stack.
On Mon, Jun 11, 2012 at 11:24 PM, Piotr Drąg piotrdrag@gmail.com wrote:
2012/6/11 Miloš Komarčević kmilos@gmail.com:
I know, but this is only because of glibc (GNOME and others really pushed for something else), and is wrong IMHO. The @ POSIX locale modifiers were never intended to be used for different scripts (a wholly new locale), but to _modify_ an exisitng locale to create a _variant_ (de_DE@euro etc.)
Glibc is, with due respect, stuck behind times when it comes to i18n and needs to jump on the BCP47 wagon. So does Transifex.
Well, in theory you're probably right, but I think it's important to stay compatible with our software stack.
Just to be clear, I wasn't advocating renaming the .po files which would certainly break things (except where it is possible, like for docs and web pages), just labeling the team in Transifex the 'right' way and setting up aliases.
M
Hi,
On Tue, 12 Jun 2012 08:27:28 +0100 Miloš Komarčević kmilos@gmail.com wrote:
On Mon, Jun 11, 2012 at 11:24 PM, Piotr Drąg piotrdrag@gmail.com wrote:
2012/6/11 Miloš Komarčević kmilos@gmail.com:
I know, but this is only because of glibc (GNOME and others really pushed for something else), and is wrong IMHO. The @ POSIX locale modifiers were never intended to be used for different scripts (a wholly new locale), but to _modify_ an exisitng locale to create a _variant_ (de_DE@euro etc.)
Glibc is, with due respect, stuck behind times when it comes to i18n and needs to jump on the BCP47 wagon. So does Transifex.
Well, in theory you're probably right, but I think it's important to stay compatible with our software stack.
Just to be clear, I wasn't advocating renaming the .po files which would certainly break things (except where it is possible, like for docs and web pages), just labeling the team in Transifex the 'right' way and setting up aliases.
BTW, in Fedora docs Git repos, the sr translations are stored in the sr-Latn-RS directory, and sr-Latn-RS is also what we have in the Transifex lang code mappings because Publican needs this code.
Cheers, Petr Kovar
2012/6/9 Kévin Raymond shaiton@fedoraproject.org:
- I found the team ms_MY with some translations (look for [EE] entries), on which team should it be merged? ms appear to not exist yet.
If there is a need for a Malay team, code ms should be used with ms-MY as an alias.
-
Christopher Antila -
Dimitris Glezos -
Kévin Raymond -
Miloš Komarčević -
Petr Kovar -
Piotr Drąg -
Richard E. van der Luit