Currently not possible. The main problem here is: We cannot detect programmatically which field contains translatable values and which doesn’t.
And we cannot just offer all custom fields, because some might expect arrays (values lists) as a value, not a string (a piece of text). Some fields even might get their values automatically by a plugin.
We don’t want to offer an interface in which users can break things, so this is rather difficult. So it is on our list, but have to find a good solution.
Any news for this topic?
I’m wondering if letting the user supply some info to the plugin could be a feasible approach. For example, select wich fields are translatable, their type (text, select, wysiwyg, …), …
Closing this 9 month old topic.
