Translator's Information

From Claws Mail FAQ
Revision as of 10:13, 6 February 2007 by Claws (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigationJump to search

The Release Process

The Claws Team sets a date for release, at least 2 weeks in advance.
Week One: CVS feature freeze
No new features are added to CVS, the Team try to fix as many outstanding bugs as possible, test new features thoroughly, and improve any translatable strings as is deemed necessary.
A message announcing the forthcoming release is sent to the translators' mailing list.
Week Two: CVS string freeze
No new features are added and no translatable strings are changed, added or removed.
During this second week, translators should update their local CVS trees and work on updating their translations. For those translators who are unable to build from CVS, up to date POT files are made available for download at
Whan a translator has updated his/her translations they should be sent to Paul at at any time before the week is up. They will then be committed to CVS and included in the release.
Week Three: The release
The release will be made on Day One of Week Three.
Bug-Fix Releases
The Claws Team occasionally feels the need to make bug-fix releases. These are normally indicated by an increment of the MICRO_VERSION, (e.g. from version 2.7.0 to 2.7.1). The bug-fix releases contain none of the new features that have been added to CVS since the last major release, and they also do not contain any new translatable strings that may have been added to CVS. Therefore no translation updates are required for these releases and, consequently, the usual process, detailed above, is not initiated.

Information for new translators

Checking your translation for errors (and completeness)

/usr/bin/msgfmt -c --statistics en_GB.po