The simple solution is to implement "prepare translation" in the nodeapi hook in icl_content.module. Added at line 1029 (6.x-1.21)

} else if ($op == 'prepare translation') {
if (isset($node->translation_source->format))
$node->format = $node->translation_source->format;
if (isset($node->translation_source->path))
$node->path = $node->translation_source->path;
}

This should probably be implemented in the core modules themselves, but until this happens this is a quick and reliable solution. I can't think of any circumstances where you would want different input types and url path for translated content, so I think this is pretty safe.

Comments

mattb’s picture

mattb commented
Title: On selecting ADD TRANSLATION from node TRANSLATE tab, copy the URL Path and input type over to the new node. PATH INCLUDED » On selecting ADD TRANSLATION from node TRANSLATE tab, copy the URL Path and input type over to the new node. PATCH INCLUDED
brucepearson’s picture

brucepearson commented
Status: Patch (to be ported) » Closed (works as designed)

I don't think it's appropriate to add this to the Translation Management module. The Add Translation function is done by the core modules.

The node format and path are set when translations are created by the Translation Management module.