translate.fp.o is showing a wrong state for spanish locale, http://translate.fedoraproject.org/languages/es It says, for example, for Documentation 0% while http://translate.fedoraproject.org/languages/es/fedora-8 says 100%.
Do we have to work with http://i18n.redhat.com/cgi-bin/i18n-status for the software translation ?
regards
Domingo Becker (es)
On 11/27/07, Domingo Becker domingobecker@gmail.com wrote:
translate.fp.o is showing a wrong state for spanish locale, http://translate.fedoraproject.org/languages/es It says, for example, for Documentation 0% while http://translate.fedoraproject.org/languages/es/fedora-8 says 100%.
You can safely ignore the right-hand-side column called "Documentation" and scoll down to see the proper docs stats.
It's a special way of handling documentation based on the `intltool` toolchain. Ideally we should use this, since it produces the POT files on the fly etc, but it needs some work before it actually works with our Docs toolchain.
I went on and commented it out of the HTML for now.
-d
Do we have to work with http://i18n.redhat.com/cgi-bin/i18n-status for the software translation ?
2007/11/27, Dimitris Glezos dimitris@glezos.com:
You can safely ignore the right-hand-side column called "Documentation" and scoll down to see the proper docs stats.
It's a special way of handling documentation based on the `intltool` toolchain. Ideally we should use this, since it produces the POT files on the fly etc, but it needs some work before it actually works with our Docs toolchain.
I went on and commented it out of the HTML for now.
Ok, I saw the changes. Looks better now.
But it still shows incorrect stats. See at http://translate.fedoraproject.org/languages/es/fedora-8 I also read your comments to this post, saying the interface needs more maintenance. So, let's wait.
Do we have to work with http://i18n.redhat.com/cgi-bin/i18n-status for the software translation ?
This question is still unanswered.
I read that Translation Quick Start Guide is up to date. But if we can not submit modules in https://publictest5.fedora.redhat.com/submit/ which are listed in http://translate.fedoraproject.org/languages/es/fedora-8 then we will have to use the old i18n interface. But the guide doesn't cover it. If a new translator read http://docs.fedoraproject.org/translation-quick-start-guide/en_US/sn_transla... and then finds out that some modules are not submittable, he/she would probably quit the job.
This is the time to get things up and running. It would give translators enough time to complete their work on time for F9.
kind regards
Domingo Becker
Domingo Becker wrote:
2007/11/27, Dimitris Glezos dimitris@glezos.com:
You can safely ignore the right-hand-side column called "Documentation" and scoll down to see the proper docs stats.
It's a special way of handling documentation based on the `intltool` toolchain. Ideally we should use this, since it produces the POT files on the fly etc, but it needs some work before it actually works with our Docs toolchain.
I went on and commented it out of the HTML for now.
Ok, I saw the changes. Looks better now.
But it still shows incorrect stats. See at http://translate.fedoraproject.org/languages/es/fedora-8 I also read your comments to this post, saying the interface needs more maintenance. So, let's wait.
Do we have to work with http://i18n.redhat.com/cgi-bin/i18n-status for the software translation ?
This question is still unanswered.
The answer would be 'yes' for a while, from my understanding. However if any package appeared there but already moved to t.fp.o must be removed for avoiding confusion.
I read that Translation Quick Start Guide is up to date. But if we can not submit modules in https://publictest5.fedora.redhat.com/submit/ which are listed in http://translate.fedoraproject.org/languages/es/fedora-8 then we will have to use the old i18n interface. But the guide doesn't cover it.
It states at the first para of Section 3 Translating Software. "To sign up for an account on i18n.redhat.com, please visit http://i18n.redhat.com/cgi-bin/i18n-signup/."
In same para, it also says "This warning will probably be deprecated soon.". I am hoping that 'soon' will be happened soonish, or happened well before enough FC9. If so, then it might not be needed for newbies, simple is better:) But it's just my assuming and anyone can add the section/sub-section anytime. How you think?
If a new translator read http://docs.fedoraproject.org/translation-quick-start-guide/en_US/sn_transla... and then finds out that some modules are not submittable, he/she would probably quit the job.
The modules not-submittable would be only the ones which it's maintainer moved the repository to fedora.org but have not taken appropriate action (making po files available in transifex) or the thing is just on the way. Otherwise we can translate either in transifex or on elvis. That is what I am understanding, but I can be wrong. Please correct me if so.
This is the time to get things up and running. It would give translators enough time to complete their work on time for F9.
Strongly agree.
cheers noriko
kind regards
Domingo Becker
-- Fedora-trans-list mailing list Fedora-trans-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-trans-list
2007/11/28, Noriko Mizumoto noriko@redhat.com:
Domingo Becker wrote: The answer would be 'yes' for a while, from my understanding. However if any package appeared there but already moved to t.fp.o must be removed for avoiding confusion.
Ok, we will continue working with i18n for modules not submittable on transifex.
It states at the first para of Section 3 Translating Software. "To sign up for an account on i18n.redhat.com, please visit http://i18n.redhat.com/cgi-bin/i18n-signup/."
In same para, it also says "This warning will probably be deprecated soon.". I am hoping that 'soon' will be happened soonish, or happened well before enough FC9. If so, then it might not be needed for newbies, simple is better:) But it's just my assuming and anyone can add the section/sub-section anytime. How you think?
It would be scary for a new translator to find this. Anyway, great job from you with the t.q.s. guide.
The modules not-submittable would be only the ones which it's maintainer moved the repository to fedora.org but have not taken appropriate action (making po files available in transifex) or the thing is just on the way. Otherwise we can translate either in transifex or on elvis. That is what I am understanding, but I can be wrong. Please correct me if so.
Would be nice if maintainers take the appropriate actions in order to have transifex up and running for all modules. Would be less confusing for new translators.
I have new spanish translator volunteers, coordination work must be done. I also see at least two new translator a week on fedora-trans-list. It must be clear for all of them which system to use and for how long it will be available.
By the way, which would be the F9 branch (devel) in t.fp.o ?
kind regards Domingo Becker (es)
Following on the topic:
t.fp.o shows a 5% average completion for Bulgarian (bg) language where http://i18n.redhat.com/cgi-bin/i18n-status shows around 50% (or more)
Which one are the correct stats and why the difference? Do translators need to translate again the files from t.fp.o or they could be merged with the one from i18n.redhat.com?
Thanks, Alexander.
Alexander Todorov kirjoitti:
Following on the topic:
t.fp.o shows a 5% average completion for Bulgarian (bg) language where http://i18n.redhat.com/cgi-bin/i18n-status shows around 50% (or more)
The same thing happens for Finnish (fi), see http://translate.fedoraproject.org/languages/fi/fedora-8. I think there's something wrong with t.fp.o now, the po files are there, but it won't notice them...
On 11/27/07, Ville-Pekka Vainio vpivaini@cs.helsinki.fi wrote:
Alexander Todorov kirjoitti:
Following on the topic:
t.fp.o shows a 5% average completion for Bulgarian (bg) language where http://i18n.redhat.com/cgi-bin/i18n-status shows around 50% (or more)
The same thing happens for Finnish (fi), see http://translate.fedoraproject.org/languages/fi/fedora-8. I think there's something wrong with t.fp.o now, the po files are there, but it won't notice them...
*sigh*.. It seems that Damned Lies will need more maintenance love and a close eye than we had expected. :/
Next week I'll be at the Open Translation Tools 2007 workshop in Croatia and then at FOSS.IN, so I believe I'll have some time to look into these issues.
-d