Difference between revisions of "String Freeze"

Revision as of 08:39, 27 May 2006

The GnuCash Subversion repository went into String freeze on April 16th, version 1.9.5 Announcement 1.9.5. See Release Schedule for the schedule context on our way to a 2.0.0 release.

This means that all strings are fixed. It is guaranteed that no string changes occur. We invite every translator to contribute with new translations.

Purpose

The purpose of a String Freeze is to give translators enough time to translate all the strings in the application. During the String Freeze all user-visible strings are frozen and must not change; if they do change then some part of the translation work has been in vain. The translators try hard to achieve 100% of translations so that the user will not encounter any English messages when running in a non-English locale. This will break as soon as any message is added or changed (which means it will show up untranslated). To give the translators the time necessary to achieve full translation we will have a String Freeze period between March xx and the 2.0.0 release. Every feature addition and/or change that changes or adds strings will have to wait until 2.0.0 is out.

See also:

• http://live.gnome.org/ReleasePlanning/Freezes
• http://live.gnome.org/TranslationProject/HandlingStringFreezes

Rules

To ensure every developer respects this String Freeze, here's what we ask every developer:

• During string freeze you must not change or add any string.
• If you have a new feature that brings a new string, postpone it until after 2.0.0 is released.
• If you think a new feature is desperately needed right now, ask on the gnucash-devel mailing list and be sure to state that the feature requires a violation of the string freeze. If there is no objection from the other developers and the translation manager (User:cstim, Christian Stimming), an exception to the string freeze might be allowed, but it is highly unlikely that this will happen.
• String Freeze violations that haven't been asked for on gnucash-devel will be reverted. Period.
• The *only* exception to the above rules is if an existing string is just plain wrong and/or is completely misleading. In any other case, including typos, the strings must remain unchanged and any string changes must be postponed until after 2.0.0.

Comments? Questions? --Cstim 11:26, 16 March 2006 (EST)

(Nevertheless there might be a very small number of strings that need unexpected changes, for example if we mentioned the GnuCash version 1.8 instead of 2.0. Apart from those, nothing will change.)

Scheduled String Changes after String Freeze

Here is a draft collection of strings whose changes are rejected during string freeze, but should be changed as soon as the string freeze ends.

• src/gnome/schemas/apps_gnucash_general.schemas.in : "show horizontal borders between cells" -> "between rows".
• src/gnome-utils/glade/preferences.glade: "... Legal values are any single non-alphanumeric unicode character" -> "... A legal value is any single character except letters and number."
• src/gnome-utils/druid-gnc-xml-import.c (twice): "The file could not be reopen." -> "The file could not be reopened."
• src/gnome/gnc-plugin-page-account-tree.c: "Check & Repair Su_baccount" -> "Check & Repair Su_baccounts"
• src/gnome-search/search.glade: "_New item ..." -> "_New item..."
• src/gnome-utils/glade/preferences.glade: "... date format comon in ..." -> "... date format common in ..."
• /src/gnome-utils/gnc-file.c: "...not write to file %s Check that ..." -> "...not write to file %s . Check that ..."
• src/report/report-system/report.scm: Translate error messages when a duplicate report name is ignored.
• src/gnome/gnc-plugin-page-register.c: "Exit the exchange rate..." -> "Edit the exchange rate..."
• src/import-export/import-provider-format.glade.h src/import-export/qif-import/qif.glade.h: It seems "m-d-y" is right, so "month-year-day" should be changed to "month-day-year" (see http://bugzilla.gnome.org/show_bug.cgi?id=342030)
• lib/libqof/backend/file/qsf-backend.c: "Encoding string to use when writing the XML file." -> clarify wording, e.g. "String encoding to use when writing the XML file." seem to be clearer??
• lib/libqof/backend/file/qsf-backend.c: "...by passing the encoding string in this option." -> clarify wording, e.g. "...by passing the string encoding in this option." clearer??
• doc/tip_of_the_day.list.in: "... View -> Style ... " -> There is no longer a Style submenu. The values are directly on View menu.
• src/gnome-utils/glade/preferences.glade: 07/31/05 -> 07/31/2005, 31/07/05 -> 31/07/2005, 31.07.05 -> 31.07.2005 (bug)