[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    RFC: Release of KDE 2 translations
From:       "Thomas Diehl" <thd () kde ! org>
Date:       2000-08-11 10:07:44
[Download RAW message or body]

===================
Request For Comment
===================

Situation
---------

Due to the late message freeze and vacation time most language teams
won't be able to finish their translations in time for the 2.0 release.
After the release, however, the feature freeze will end and so would
normally the message freeze. In other words: the messages in kde-i18n
would change on a daily basis again and wouldn't reflect the 2.0 status
anymore. In this case, teams would be unable to complete translation
of KDE 2.0 at a later date (except they would keep a separate set of
POs themselves which is not easy to organize for all teams).

Suggestions
-----------

*   We only release such translations with KDE 2 which are explicitely
reported as "finished" by the language coordinators (all of which
should get this message by a separate BCC).

It is the responsibilty of the individual teams when they regard their
work as "finished" (ie: good enough for release) but it's generally
recommended that all modules, and esp. kdebase, should be translated at
80 percent or more, kdelibs and desktop.po at 100%. (Also remember that
desktop.po has to be in UTF-8 format and that everything must compile.)

*   All other translations of KDE 2.0 are released at a later date.
That means: they will be made publicly available as soon as they are
reported as finished but we can also set a formal release date for a
"KDE 2, Part II" which would comprise the new translations, maybe also
new documentation, style & icon stuff, and bug fixes (provided the
latter don't result in changed message strings).

A date for such a second release date has to be discussed yet but it
should be not too far in the future. Maybe 3-4 weeks after the main
release.

*   To enable all teams to produce a translation of KDE 2.0,
coordinators can request an individual message freeze for their
language. This means: Even after the release of KDE 2, the PO files of
the respective team in the kde-i18n module of CVS will _not_ change
and will still reflect the status of the 2.0 release until the
coordinator reports his translation as finished.

*   All languages which are neither reported as finished nor get an
individual message freeze will be checked if there's still active
translation work going on. If there's no visible activity for a longer
time I will set the status of the respective language to "unmaintained"
on the team page at http://i18n.kde.org/teams/ and will encourage new
translators to start working on them.

Thoughts? Objections?

Thomas




--- 
KDE translation: http://i18n.kde.org/
Deutsche KDE-Uebersetzung: http://i18n.kde.org/teams/de/

[prev in list] [next in list] [prev in thread] [next in thread]