1

AFAIK core's does not support (and could take a while to do so) keyed based translation (like Symfony or other do). Theres an idea queued but seems to fall on deaf ears.


1

The text of the submit button depends only on the translation settings of the status field. If the field "Publishing status" is not translatable for the content type, the button says "Save (all translations)". You can change the language settings for content types, taxonomy vocabularies, user profiles here: /admin/config/regional/content-language


1

After a bit of struggle and research, here is the approach taken - custom_module.install file - /** * Enable translation for workbench_reviewer field. * Implements hook_update_n. */ function hook_update_xxxx() { $entity_definition_update_manager = \Drupal::entityDefinitionUpdateManager(); $field_storage_definition_node = $...


Only top voted, non community-wiki answers of a minimum length are eligible