Issue #1030970 by loominade: Fixed Terms description not allowed for translation because of its input format.

Issue #1223522: Fixed missing API functions i18n_string_array_merge(), i18n_string_update_context() from install scripts, added some update dependencies.

Issue #1217782 by fietserwin: Fixed Strings page: option 'Clean up left over strings' does not work.

Cleaning up and making reusable string translation forms. Reworking field translation forms, path was too long for the menu.

Issue #1224878 by Devin Carlson: Multilingual settings page has incorrect link to block administration page

Issue #1225124: Fixed Unable to save menu item translation and other issues with the menu translation form.

Issue #1182030: Not displaying all translations for taxonomy term (disable i18n_select for translation set loading)

Issue #1202372: Fixed Field labels and descriptions for fields with multiple values are not translated by i18n_field().

Issue #1214616: Improved translation sets to keep track of related ones when moving items from one to another.

Fixed permission issue with taxonomy tests (needs administer site configuration to change string settings)

Issues #1214616 and #1156564: Taxonomy term translation issues and Remove term from translation set when language is set to none.

Issue #1212200 by jox: Fixed Language in menu_links() does not get updated properly for language neutral nodes.

Issue #1125290 by jox | andrea.corelli: Changed Why if I disable multilingual support for a content type then the language is marked as the default instead of neutral?. Simplified patch.

Issue #1192332: Fixed Incorrect message on wrong Block translation. Other format handling issues for translation form.

Issue #1170850: Fixed switching default language changes source language. Added variable for source language.

Issue #1194234 by luisortiz: Fixed i18nsync uses a translation function but doesn't require the module.