Dear translation teams,
according to [Fedora 25 schedule], we reached "Software String Freeze" on august 9th.
What to translate ? Packages that follow Fedora release cycle : Main projects : https://fedora.zanata.org/version-group/view/main
Need priority list ? https://fedoraproject.org/wiki/L10N_GUI
Is there a time limit ? The same schedule says "Software Translation Deadline" is 2016-09-06
When can I see it live ? It should arrive in beta release.
What can I do if my language is already awesomely well translated ? (congratulation to Spanish team who is 100%!) Search untranslated strings that should be, test the translation in real world use case, search a useful software witch is untranslated, etc. Or just go help upstream, Gnome String Freeze is tomorrow : https://l10n.gnome.org/languages/
Anything else ? Websites, some strings are added/removed from time to time, remember to go and have a look, but there is no schedule as it is automatically published. Documentation, I personally advice not to translate it until docs team find the way to automatically publish content with his new system Pintail (they said a blog post should arrive soon on community blog). Please note this is a team decision and only my personal point of view.
Have fun!
[Fedora 25 schedule] https://fedoraproject.org/wiki/Releases/25/Schedule?rd=Schedule
Thank you! Good to know.
Cheers, Sylvia
On 14 August 2016 at 16:51, Jean-Baptiste jean-baptiste@holcroft.fr wrote:
Dear translation teams,
according to [Fedora 25 schedule], we reached "Software String Freeze" on august 9th.
What to translate ? Packages that follow Fedora release cycle : Main projects : https://fedora.zanata.org/version-group/view/main
Need priority list ? https://fedoraproject.org/wiki/L10N_GUI
Is there a time limit ? The same schedule says "Software Translation Deadline" is 2016-09-06
When can I see it live ? It should arrive in beta release.
What can I do if my language is already awesomely well translated ? (congratulation to Spanish team who is 100%!) Search untranslated strings that should be, test the translation in real world use case, search a useful software witch is untranslated, etc. Or just go help upstream, Gnome String Freeze is tomorrow : https://l10n.gnome.org/languages/
Anything else ? Websites, some strings are added/removed from time to time, remember to go and have a look, but there is no schedule as it is automatically published. Documentation, I personally advice not to translate it until docs team find the way to automatically publish content with his new system Pintail (they said a blog post should arrive soon on community blog). Please note this is a team decision and only my personal point of view.
Have fun!
[Fedora 25 schedule] https://fedoraproject.org/wiki /Releases/25/Schedule?rd=Schedule -- Jean-Baptiste Holcroft -- trans mailing list trans@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/trans@lists.fedoraproject.org
2016-08-14 16:51 GMT+02:00 Jean-Baptiste jean-baptiste@holcroft.fr:
Need priority list ? https://fedoraproject.org/wiki/L10N_GUI
That list was very out of date. I've updated it to reflect reality.
Or just go help upstream, Gnome String Freeze is tomorrow : https://l10n.gnome.org/languages/
GNOME's string freeze starts on 29th. Tomorrow is the UI freeze and the start of the all-important String Change Announcement Period. :)
https://wiki.gnome.org/ThreePointTwentyone
But you're absolutely right, helping upstreams is always a good idea!
Best regards,
On 2016年08月15日 05:43, Piotr Drąg wrote:
2016-08-14 16:51 GMT+02:00 Jean-Baptiste jean-baptiste@holcroft.fr:
Need priority list ? https://fedoraproject.org/wiki/L10N_GUI
That list was very out of date. I've updated it to reflect reality.
WOW!! super!! thank you so much, Piotr!! -- n
Or just go help upstream, Gnome String Freeze is tomorrow : https://l10n.gnome.org/languages/
GNOME's string freeze starts on 29th. Tomorrow is the UI freeze and the start of the all-important String Change Announcement Period. :)
https://wiki.gnome.org/ThreePointTwentyone
But you're absolutely right, helping upstreams is always a good idea!
Best regards,
Dear all,
quick question in regards to creation of f25-branach. What branch will be used as source? I am asking because, for example for anaconda, there at least three branches that are 100% translated into my language, while the master branch is only at 50%. So, how do tell the devs to use a specific branch for creation of f25 translation files? Or can we use zanata to merge an existing translation (e.g. f24-branch) into master, which should be used to create f25-branch. What are the criteria for devs to select an appropriate branch?
Thanks, Cheers, and Happy Monday! Florian
On 14.08.2016 10:51, Jean-Baptiste wrote:
Dear translation teams,
according to [Fedora 25 schedule], we reached "Software String Freeze" on august 9th.
What to translate ? Packages that follow Fedora release cycle : Main projects : https://fedora.zanata.org/version-group/view/main
Need priority list ? https://fedoraproject.org/wiki/L10N_GUI
Is there a time limit ? The same schedule says "Software Translation Deadline" is 2016-09-06
When can I see it live ? It should arrive in beta release.
What can I do if my language is already awesomely well translated ? (congratulation to Spanish team who is 100%!) Search untranslated strings that should be, test the translation in real world use case, search a useful software witch is untranslated, etc. Or just go help upstream, Gnome String Freeze is tomorrow : https://l10n.gnome.org/languages/
Anything else ? Websites, some strings are added/removed from time to time, remember to go and have a look, but there is no schedule as it is automatically published. Documentation, I personally advice not to translate it until docs team find the way to automatically publish content with his new system Pintail (they said a blog post should arrive soon on community blog). Please note this is a team decision and only my personal point of view.
Have fun!
[Fedora 25 schedule] https://fedoraproject.org/wiki/Releases/25/Schedule?rd=Schedule
On 2016年08月15日 12:00, Florian H. wrote:
Dear all,
quick question in regards to creation of f25-branach. What branch will be used as source?
afaik, 'master'.
I am asking because, for example for anaconda, there at least three branches that are 100% translated into my language, while the master branch is only at 50%. So, how do tell the devs to use a specific branch for creation of f25 translation files? Or can we use zanata to merge an existing translation (e.g. f24-branch) into master, which should be used to create f25-branch. What are the criteria for devs to select an appropriate branch?
only dev can tell... we do not perform merge. however, any f24-branch translation should be available in TM (translation memory) at the bottom left, and those can be copied and paste by clicking 'copy' button.
noriko
Thanks, Cheers, and Happy Monday! Florian
On 14.08.2016 10:51, Jean-Baptiste wrote:
Dear translation teams,
according to [Fedora 25 schedule], we reached "Software String Freeze" on august 9th.
What to translate ? Packages that follow Fedora release cycle : Main projects : https://fedora.zanata.org/version-group/view/main
Need priority list ? https://fedoraproject.org/wiki/L10N_GUI
Is there a time limit ? The same schedule says "Software Translation Deadline" is 2016-09-06
When can I see it live ? It should arrive in beta release.
What can I do if my language is already awesomely well translated ? (congratulation to Spanish team who is 100%!) Search untranslated strings that should be, test the translation in real world use case, search a useful software witch is untranslated, etc. Or just go help upstream, Gnome String Freeze is tomorrow : https://l10n.gnome.org/languages/
Anything else ? Websites, some strings are added/removed from time to time, remember to go and have a look, but there is no schedule as it is automatically published. Documentation, I personally advice not to translate it until docs team find the way to automatically publish content with his new system Pintail (they said a blog post should arrive soon on community blog). Please note this is a team decision and only my personal point of view.
Have fun!
[Fedora 25 schedule] https://fedoraproject.org/wiki/Releases/25/Schedule?rd=Schedule
-- trans mailing list trans@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/trans@lists.fedoraproject.org
2016-08-15 5:00 GMT+02:00 Florian H. postfuerflo@gmail.com:
I am asking because, for example for anaconda, there at least three branches that are 100% translated into my language, while the master branch is only at 50%.
That was the situation in Spanish too until a week ago or so. I don't know what the devs are up to, they may be trying to separate stuff, and there are now three documents: anaconda, extra and main. main was empty and had about 50% of the strings in the project, so I started praying for a high reuse factor, and even then with no hope of finishing for F25. After a few strings, though, I noticed TM gave me 100% matches for all of them. Not only that, they were also in the same master branch. I downloaded the po for both the anaconda and main documents, compared, and the original strings where mostly the same (one of them is in extra, instead of main). A msgmerge:
msgmerge anaconda.po main.po --output-file=main-translated.po
and an upload later, and we were back to 100%.
Answer to two emails below...
On 15.08.2016 05:30, Máximo Castañeda wrote:
2016-08-15 5:00 GMT+02:00 Florian H. postfuerflo@gmail.com:
I am asking because, for example for anaconda, there at least three branches that are 100% translated into my language, while the master branch is only at 50%.
same (one of them is in extra, instead of main). A msgmerge:
msgmerge anaconda.po main.po --output-file=main-translated.po
and an upload later, and we were back to 100%.
Oh yes, that seems to be the best way to do it. Thanks!
On 15.08.2016 02:51, Noriko Mizumoto wrote:
On 2016年08月15日 12:00, Florian H. wrote:
Dear all,
quick question in regards to creation of f25-branach. What branch will be used as source?
afaik, 'master'.
Wouldn't it be good if devs would create a f2x-branch as soon as the cycle reaches String Freeze?
I am asking because, for example for anaconda, there at least three branches that are 100% translated into my language, while the master branch is only at 50%. So, how do tell the devs to use a specific branch for creation of f25 translation files? Or can we use zanata to merge an existing translation (e.g. f24-branch) into master, which should be used to create f25-branch. What are the criteria for devs to select an appropriate branch?
only dev can tell... we do not perform merge. however, any f24-branch translation should be available in TM (translation memory) at the bottom left, and those can be copied and paste by clicking 'copy' button.
That would work but is way to much clicking - I will try merging the strings from f24-branch into the new master/main..
Best, Florian
Hi,
On Mon, Aug 15, 2016 at 11:45 PM, Florian H. postfuerflo@gmail.com wrote:
Answer to two emails below...
On 15.08.2016 05:30, Máximo Castañeda wrote:
2016-08-15 5:00 GMT+02:00 Florian H. postfuerflo@gmail.com:
I am asking because, for example for anaconda, there at least three branches that are 100% translated into my language, while the master branch is only at 50%.
same (one of them is in extra, instead of main). A msgmerge:
msgmerge anaconda.po main.po --output-file=main-translated.po
and an upload later, and we were back to 100%.
Oh yes, that seems to be the best way to do it. Thanks!
Zanata offers TM merge which can do 100% TM match and re-use on a page by page manner (since it's coming from TM so it's best to double check afterwards. This way you don't need to download and re-upload. The TM merge button is on the TM panel beside the clear button.
On 15.08.2016 02:51, Noriko Mizumoto wrote:
On 2016年08月15日 12:00, Florian H. wrote: only dev can tell... we do not perform merge. however, any f24-branch translation should be available in TM (translation memory) at the bottom left, and those can be copied and paste by clicking 'copy' button.
That would work but is way to much clicking - I will try merging the strings from f24-branch into the new master/main..
Again you can use TM merge to do bulk TM reuse. There are also ways to copy/merge translation from another version [1]. If you think the devs/package maintainers are not aware of this feature when creating the new version, please let them know. These functions are only available to Zanata project maintainers as they are potentially quite destructive and should only be used at the version creation time. It will definitely save a lot of translation effort.
[1] http://zanata.readthedocs.io/en/release/user-guide/versions/merge-translatio...
Best,
Florian
trans mailing list trans@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/trans@lists.fedoraproject.org
On 15.08.2016 05:30, Máximo Castañeda wrote:
know what the devs are up to, they may be trying to separate stuff, and there are now three documents: anaconda, extra and main. main was empty and had about 50% of the strings in the project, so I started
Anaconda and main from the master-branch seem to be pretty much the same. Does anyone know what the devs are trying to do here? Why the split of anaconda in main and extra? Which one will be used to fork f25-branch?
Thanks, Florian
praying for a high reuse factor, and even then with no hope of finishing for F25. After a few strings, though, I noticed TM gave me 100% matches for all of them. Not only that, they were also in the same master branch. I downloaded the po for both the anaconda and main documents, compared, and the original strings where mostly the same (one of them is in extra, instead of main). A msgmerge:
msgmerge anaconda.po main.po --output-file=main-translated.po
and an upload later, and we were back to 100%.
trans mailing list trans@lists.fedoraproject.org https://lists.fedoraproject.org/admin/lists/trans@lists.fedoraproject.org
-
Florian Heiser -
Jean-Baptiste -
Máximo Castañeda -
Noriko Mizumoto -
Patrick Huang -
Piotr Drąg -
Sylvia Sánchez