Migrations with config or content entity destination should depend on "default_language"

As part of the Bug Smash Initiative, we are triaging issues that are marked "Postponed (maintainer needs more info)". This issue was marked "Postponed (maintainer needs more info)" more than 2 years ago.

Since there was no additional information provided since it was requested last year, I'm marking the issue "Closed (cannot reproduce)". If anyone can provide complete steps to reproduce the issue (starting from "Install Drupal core"), document those steps in the issue summary and set the issue status back to "Active" [or "Needs Work" if it has a patch, etc.].

Thanks!

I am not so sure about closing this. The Issue Summary makes sense and core does not test with a site that has a default language other than English. And if the result is a site where you can translate content, that is a problem.

I would like to find time to test this. Assigning to myself.

I did some limited testing on this with a D7 site, installed in Italian with a translated node and translated config (content type). After migrating I didn't have any error messages or trouble translating the content. But again, my testing and source was limited.

I do to agree with @Wim Leers and @Kristen Pol that steps to reproduce are needed here. And sample database would help as well. However, since it has been 3 years since the first request for more information, and none has been supplied, I am changing the status as per #11.