Issue #671360 by dereine: switch default option for messages to not be printed with i18n_string; usability fix

Jose Antonio Reyero del Prado authored May 13, 2011 and Florian Weber committed May 13, 2011

Issue #1156560 by skilip: Both delete translation sets when deleting a vocabulary and when deleting terms

Gábor Hojtsy authored May 13, 2011 and Florian Weber committed May 13, 2011

Issue #1156688 by Gábor Hojtsy: fix i18n_field_field_delete_instance() to use proper keys for the strings

- use validation callback from menu system
- add edit and delete operation to path translation overview
- add confirmation form for translation set deletion
- change module weight to override core translation. same module weight as i18n_menu and i18n_taxonomy
- use get_edit_path and get_delete_path for consistency
- reworked path overview

Issue #1156560 by skilip: Both delete translation sets when deleting a vocabulary and when deleting terms

Issue #1156688 by Gábor Hojtsy: fix i18n_field_field_delete_instance() to use proper keys for the strings

Issue #1156458 by Gábor Hojtsy: move menu translation functionality to translation tabs consistent with taxonomy, blocks, etc.

Issue #1078422 by danielnolde, tobiasb: Disabled taxonomy fields when enabling and disabling i18n_taxonomy

Issue #1156374 by Gábor Hojtsy: try to guide users to the taxonomy page where they can actually make edits and translations - not the best solution, but core already has this UX WTF, so we need to live with that