From Fedora Project Wiki

< FWN‎ | Beats

No edit summary
No edit summary
Line 8: Line 8:


Contributing Writer: [[RunaBhattacharjee|Runa Bhattacharjee]]
Contributing Writer: [[RunaBhattacharjee|Runa Bhattacharjee]]
=== String freeze breakage alarms ===
A few modules had new string additions during the week that modified the translation status figures[1][2].  Although initially suspected to be string freeze breakages, these modifications (except for one: comps) turned out to be the result of delayed creation of new template files.
Fedora packages are currently String Frozen for Fedora 10[3] i.e. no new translated messages can be added without the prior permission of the Fedora Localization Team as per the String Freeze Policy[4].
[1] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00053.html
[2] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00076.html
[3] https://www.redhat.com/archives/fedora-devel-announce/2008-September/msg00013.html
[4] http://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
=== Fedora Docs moved to git repository ===
The Fedora documentation (including the Installation Guide, Release Notes etc.) were moved to the Fedora git repo[5]. Translation submissions can be continued via the Transifex interface[6]. However, the statistics page will not be able to present the status for these documentation modules, as documents compiled with publican are not supported by Damned Lies yet[7].
[5] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00084.html
[6] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00099.html
[7] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00093.html
=== Translation schedule to be further discussed for clarity of tasks ===
John Poelstra and Dimitris Glezos are scheduled to meet on Monday 29th September 08[8], to discuss about the details of the Fedora 10 translation schedule to clearly define all the tasks and integrate them in the schedule. The meeting is open for others to join in.
[8] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00100.html

Revision as of 14:59, 28 September 2008

Translation

This section covers the news surrounding the Fedora Translation (L10n) Project.

http://fedoraproject.org/wiki/L10N

Contributing Writer: Runa Bhattacharjee

String freeze breakage alarms

A few modules had new string additions during the week that modified the translation status figures[1][2]. Although initially suspected to be string freeze breakages, these modifications (except for one: comps) turned out to be the result of delayed creation of new template files.

Fedora packages are currently String Frozen for Fedora 10[3] i.e. no new translated messages can be added without the prior permission of the Fedora Localization Team as per the String Freeze Policy[4].


[1] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00053.html

[2] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00076.html

[3] https://www.redhat.com/archives/fedora-devel-announce/2008-September/msg00013.html

[4] http://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy


Fedora Docs moved to git repository

The Fedora documentation (including the Installation Guide, Release Notes etc.) were moved to the Fedora git repo[5]. Translation submissions can be continued via the Transifex interface[6]. However, the statistics page will not be able to present the status for these documentation modules, as documents compiled with publican are not supported by Damned Lies yet[7].


[5] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00084.html

[6] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00099.html

[7] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00093.html


Translation schedule to be further discussed for clarity of tasks

John Poelstra and Dimitris Glezos are scheduled to meet on Monday 29th September 08[8], to discuss about the details of the Fedora 10 translation schedule to clearly define all the tasks and integrate them in the schedule. The meeting is open for others to join in.


[8] https://www.redhat.com/archives/fedora-trans-list/2008-September/msg00100.html