In order to be able to identify a given migration as multilingual, we need to migrate the content type translation settings for the different content types.
Content type translation setting variables:
- language_content_type_$type (one for each content type). Has 4 possible states:
- No value: Means no translatable.
- 0: Means no translatable.
- 1: Means has language.
- 2: Means has language, and it is translatable.
- i18n_newnode_current_$type (one for each content type). A checkbox that indicates if the current language is the default for new content.
- i18n_required_node_$type (one for each content type). A checkbox that makes language required (neutral not allowed).
- i18n_lock_node_$type (one for each content type). A checkbox that makes the language locked, so it cannot be changed on edit.
- i18n_node_$type (one for each content type). Has 4 possible states:
- No value: not applicable, no translatable.
- 1: All enabled languages allowed.
- 2: All defined languages allowed.
- 3: All defined languages allowed, but not displayed in links.
- language_content_type_negotiation ?
- language_content_type_default ?
entities: node: article: language: default_configuration: langcode: current_interface language_show: true
Original report by Ryan Weal
Content type translation settings (D6/D7 core content translation and entity_translation contrib -> D8 content type config). This will bring what language settings are allowed for content authors of a particular content type. It will determine what the translation method was (content translation == 1 node per language, entity_translation = 1 und node with translatable fields). Config here specifies if it is possible to set langauge_none/undefined/language neutral/UND or if setting a language is mandatory.