TextdomainStatus

From The Battle for Wesnoth Wiki

This page aims to gather information on plans regarding mainline content changes affecting each textdomain. It's strongly advised for translators to follow the recommendations as it might save you *a lot* of work.

Textdomain Changes since 1.8 Changes still planned (before 1.10) Status
wesnoth general development none - stringfreeze active! ready
wesnoth-editor general development none - stringfreeze active! ready
wesnoth-help new textdomain, based on wesnoth none - stringfreeze active! ready
wesnoth-lib general development none - stringfreeze active! ready
wesnoth-multiplayer general development none - stringfreeze active! ready
wesnoth-test no changes none - stringfreeze active! ready
wesnoth-tutorial general development none - stringfreeze active! ready
wesnoth-units general development none - stringfreeze active! ready
wesnoth-manpages general development none - stringfreeze active! ready
wesnoth-manual general development none - stringfreeze active! ready
wesnoth-anl general development none - stringfreeze active! ready
wesnoth-aoi general development none - stringfreeze active! ready
wesnoth-did general development none - stringfreeze active! ready
wesnoth-dm general development none - stringfreeze active! ready
wesnoth-dw completely new domain none - stringfreeze active! ready
wesnoth-ei general development none - stringfreeze active! ready
wesnoth-httt general development none - stringfreeze active! ready
wesnoth-l general development none - stringfreeze active! ready
wesnoth-low rewrote several scenario dialogs none - stringfreeze active! ready
wesnoth-nr general development none - stringfreeze active! ready
wesnoth-sof general development none - stringfreeze active! ready
wesnoth-sotbe general development none - stringfreeze active! ready
wesnoth-tb story polishing none - stringfreeze active! ready
wesnoth-thot general development none - stringfreeze active! ready
wesnoth-trow general development none - stringfreeze active! ready
wesnoth-tsg general development none - stringfreeze active! ready
wesnoth-utbs general development none - stringfreeze active! ready

In the cycle after 1.8 the term general development does cover large punctuation changes. This means that apostrophes, dashes, minuses and stuff like this were changed and unified to use the unicode chars meant for this stuff. Only a part of those changes could be automatically converted in the translations using tools like pofix.py. This leads to many fuzzy strings.

The term small corrections means changes that alter grammar, punctuation and fix typos but tend to not change the general meaning. If this is listed as only term in the area of planned changes it means that just general cleanup and spelling fixes will happen without bigger changes being planned. If it is listed as the only item in the "changed stuff" area it means that not too many really bigger changes did take place and most should be covered in a short time.

The term soft string freeze means almost the same as smaller corrections, it is just a little stricter. So there should be no changes beside spelling and grammar fixes in those frozen textdomains at all.

The term none - stringfreeze active! means just that. All changes that happen from now on are either explicitly announced on the translation mailing list (and should be damn small) or they are gracefully handled by utils/pofix.py which is run before files are committed (so the changes are tiny, too...).

Summary of possible statuses:

  • not ready - not done at all and many changes planned
  • wait for stringfreeze - changes can happen any time in this textdomain, better wait for the stringfreeze
  • not sure - not sure how much might change
  • ready - ready for translations, feel free to work on things, not much should change
This page was last modified on 11 November 2011, at 20:08.