Gathering more i18n support

#338630: Locale is unable to rebuild lost Javascript translation files
#578360: improve localize terms UI support
#582438: improve content types UI support

PS: please add comments bellow, but avoid to directly use the reply link of this comment to keep it editable in time

it seems that i18n module prefers to avoid complicated stuff getting in

http://drupal.org/node/578360#comment-2220526

For i18n modules we try to keep them as simple as possible (...), so we are not adding translation links everywhere.

Maybe you can post the patch for that other module or work on improvements for it.

it really is a complicated module already
so, where to put UI improvements?
how to name such a module?
would locale module issues fit there as well?

besides #338630: Locale is unable to rebuild lost Javascript translation files
I also use a form button to "Re-import" all translations, useful when developing translations
or simply when an upgraded version of a translation replaces old translation files, since there is no way to demand Drupal to "upgrade" translations

all issues mentioned above are related to i18n/translations, which means multi-lingual support
should all of them be bundled in a single project?
again: how would be the name of such module?

that's a step forward, thanks for bringing a module name

for others, please bring to this thread as much i18n/translations issues to see where do they fit

suggestions for a project name to bundle locale's tweaks are welcome