El ds 13 de 11 de 2010 a les 15:52 +0000, en/na Sesivany va escriure:
> Thank you for clarification.
> So Nautilus is upstream's fault in this case.
Well, it's no one's "fault", really. GNOME and Ubuntu are translated by
volunteers, so the fact that translations were submitted outside the
deadline most probably simply means that they had other obligations and
couldn't make it for that day.
> How can we fix this earlier? I work for a company which has
> Ubuntu-related products and we simply can't afford to have
> untranslated strings on such exposed places for two months. If this
> happens again and we take the finished translation from upstream and
> upload it on Launchpad the updated package will be released earlier?
> Or how else can we help?
>
There are many ways in which you can help:
* Translations. Help the Czech team with translations, so that
they can be finished earlier.
* Get upstream translations. Upload the upstream translation
manually as explained in the previous messages, so that they are
available in the next language pack
* Testing. Before they are released to the majority of users, help
testing the Czech language pack [1]. The start of the testing
period will be announced on the translators mailing list [2].
As mentioned earlier as well, the schedule for language packs is being
redeveloped [3], so I cannot tell you exactly when the next Maverick
language pack will be released, other than "soon". If you'd also like to
contribute on that, please have a look at the specification and get in
touch with me to find out in what you can help.
In summary, if you are willing to contribute, just get in touch in
whichever way you prefer with the translations team [2], or feel free to
contact me directly.
El ds 13 de 11 de 2010 a les 15:52 +0000, en/na Sesivany va escriure:
> Thank you for clarification.
> So Nautilus is upstream's fault in this case.
Well, it's no one's "fault", really. GNOME and Ubuntu are translated by
volunteers, so the fact that translations were submitted outside the
deadline most probably simply means that they had other obligations and
couldn't make it for that day.
> How can we fix this earlier? I work for a company which has
> Ubuntu-related products and we simply can't afford to have
> untranslated strings on such exposed places for two months. If this
> happens again and we take the finished translation from upstream and
> upload it on Launchpad the updated package will be released earlier?
> Or how else can we help?
>
There are many ways in which you can help:
* Translations. Help the Czech team with translations, so that
they can be finished earlier.
* Get upstream translations. Upload the upstream translation
manually as explained in the previous messages, so that they are
available in the next language pack
* Testing. Before they are released to the majority of users, help
testing the Czech language pack [1]. The start of the testing
period will be announced on the translators mailing list [2].
As mentioned earlier as well, the schedule for language packs is being
redeveloped [3], so I cannot tell you exactly when the next Maverick
language pack will be released, other than "soon". If you'd also like to
contribute on that, please have a look at the specification and get in
touch with me to find out in what you can help.
In summary, if you are willing to contribute, just get in touch in
whichever way you prefer with the translations team [2], or feel free to
contact me directly.
Thanks!
[1] /wiki.ubuntu. com/Translation s/LanguagePackU pdatesQA /wiki.ubuntu. com/Translation s/Contact/ /blueprints. launchpad. net/ubuntu/ +spec/ubuntuthe project- community- n-translations- language- pack-updates- schedule
https:/
[2] https:/
[3]
https:/
-- la.wordpress. com ca/dplanella / www.twitter. com/dplanella
David Planella
Ubuntu Translations Coordinator
www.ubuntu.com / www.davidplanel
www.identi.