3

I have a node that has many fields but need only the title and body field translated.

This node type has a workflow associated to it and any authenticated user can create that node.

The client requires that fields for language EN/FR are all available on the form

I'm wondering what is the best approach to adopt: content translation + different fields for each language or Entity field translation

I've tried entity field translation but it does not provide the fields for each language on the same interface and it does not seem to work well with workbench moderation.

3
  • do you have some advance? Commented Nov 13, 2015 at 5:01
  • I've added distinct fields for the different languages. Overwritten the node title through hook_node_view and used a custom views handler for the title for my views Commented Nov 14, 2015 at 14:08
  • if you want you can post your solutions as a answer Commented Dec 4, 2015 at 16:51

2 Answers 2

3

You must repeat the fields, because the Entity Translation and the Internationalization (i18n) module don't provive the fields for each language in the same interface.

0

Apparently there is a module for Drupal 7 called Dual-language editor (DLE) that does this.

For Drupal 8 and 9 there are 2 contrib modules:

Multilanguage Form Display: This tries to achieve the same thing by adding a form to translate all fields for each language. Seems that the module may not be stable enough, though.

Entity Translation Unified Form: I haven't used it yet, but this looks a bit more polished, has more usage and claims support for Paragraphs.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.