This article describes some possible reasons for the layout of pages not being transferred for a specific language copy after a job or project is finished in XTM Cloud, and provides an explanation to that.

There might be several reasons. The two, however, are most likely to be the case:

1. Certain fields of the page in AEM that are related to layout and should not be localized have actually been translated in XTM Workbench. For this reason, once the translated content comes back to the CMS, it breaks the UI.

2. Particular target language version of the site already exists in AEM, and you attempt to update the existing content. When, for example, you add extra containers and spacing, those changes are applied only to the source page. Note that when updating the target language copy, only the text (translations) is transferred to the project. Any structural changes, such as adding containers, will not be carried over automatically unless you also apply those changes to the existing target language version of the page.

First of all, you should verify the translation rules on your AEM instance. The translation rules are responsible for what part of the content should be sent for the project and what should not. Once the translation rules are changed, you have to create the project anew.

Furthermore, in the case of potential page structure changes, it is important to remove the previous target language version from the AEM instance before sending the project for translation in XTM Cloud, into that particular language once again. Otherwise, only the text will be updated, and the page structure will remain unchanged.