It would be great if the base module could follow the field module naming pattern, and instead of trying to replace a core module (and reproduce a core module under a different name), it would simply be renamed (and drop the copy of the core module). I'd suggest 'field_translation'. Using the same name as a core module has multiple problems. For example, when you enable the module, there is actually no module enabled as far as Drupal is concerned (Drupal recognizes a module moved places), so the caches are not rebuilt. Also, the module needs to include a copy of the core translation module, hardly much of it needs to have code changes. I think it can reproduce those changes with alters instead of copying the whole module under a different name. Finally, translation module itself includes functions with the translation_node prefix, which makes the namespaces overlap in possibly confusing ways.
Comments
Comment #1
plachNo time for a proper answer now. Here is a related issue: #902760: Change module name so it can work with Core translation.
Comment #2
gábor hojtsyLet's close this and move discussion back there.