In Drupal 7, content translation settings are on the content type settings page. Field translatability is supported in core but does not have a user interface. With the entity_translation module, field translatability is enabled on a per content type basis and then edited on each field settings page. This makes it pretty complex to go through and configure content for translation and provides no overview if something is not done right.
In Drupal 8, content translation is provided with the field translation feature and is applied across all content entity types in core. This includes users, comments, taxonomy terms, menu items, etc. To configure this matrix of settings, a one page overview was added where all content language settings are exposed (if language module is turned on) and translatability is configured (if content translation module is also turned on). If both modules are turned on, only types with translatability (entities which support translation and have fields) will have the translatability checkbox exposed. Find this new settings page at Administration > Configuration > Regional and language > Content language settings:
Attachment | Size |
---|---|
D8_content_language_settings.png | 45.3 KB |