Problem/Motivation
Migrate multilingual data from D6 and D7.
Proposed resolution
D6 migration and much of D7 is working so use those migrations, and their plugins as models for these migrations. It is preferred to improve the existing destination plugins instead of creating new ones.
Remaining tasks
Because D6 is nearing end of life, the D6 multilingual migrations are the highest priority as shown in the list below.
Must have - remaining content migrations
Drupal 6/7
- #2746541: Migrate D6 and D7 node revision translations to D8 - Changes the revision_translation_affected and removes vid: vid from migration.
- #2859297: Migrate taxonomy term references for D6 Node translations
- #2981393: Migrate D6 comment type language settings
- #3030937: Ensure language is not Null in translation source queries
Drupal 7
Multilingual taxonomies / content migrations
- #2979964: Migrate translations for D7 i18n taxonomy 'localized' terms - looks like this will be done in #2979966: Migrate D7 i18n taxonomy term language
- #2979966: Migrate D7 i18n taxonomy term language
- #3035392: Migrate taxonomy term references for D7 Node translations
Comments
Should have
- #2979970: Migrate D7 vocabulary language settings
- #2980551: Errors When Migrating Books From Multilingual Drupal 7
Could have
- #3008028: Migrate D7 i18n menu links (no BC breaks; see comment #97)
- #3008029: Migrate D7 i18n field option translations
- #3030939: D7 user profile translation migration
- #3031727: Migrate D7 synchronized fields