| Table of Contents |
|---|
Introduction
Though it happens quite rarely, aside from standard translation items, you might also You might sometimes want to send some additional files through XTM Cloud, as reference for AEM end users, along with standard translation items. This is unusual, but it is possible. Those files are not meant to be translated, as they only constitute contain subsidiary material (guidelines, descriptions, etc.).
One of the constraints imposed by the AEM connector is that every file/job in an XTM Cloud project has to must have its corresponding job in AEM. The connector itself stores jobs job pairs (AEM job ID - /XTM Cloud job ID) , and only a specific pair can be imported back to into AEM. Therefore, it It is therefore not possible send such additional files of this kind by, for example, uploading them as a “reference material” to an already existing project in XTM Cloud, as “reference materials", since they do not originate from AEM, thus not having so there are no relevant jobs there.
The only solution is to create an extra folder on the AEM side with a dummy file (in with the same format as the dedicated file!), which will constitute some act as a sort of a “container” "container" for our dedicated file from XTM Cloud, add that folder to a project and send the project over for translation in XTM translationCloud. During the translation process, our dedicated file is uploaded as the target to replace the dummy file. Finally, upon completion of when that particular job is completed in XTM Cloud, our additional/dedicated file is delivered to AEM.
At this point, there is yet another constraint, imposed by the connector, that we need to be aware of. The format of source and target files must be in the same format. What it this means is that, if an AEM source file is in the “DOCX” "DOCX" format, its XTM Cloud target file also needs to come back as “DOCX”. Whereas a “DOCX" file. While this does not pose any problem for such formats as the aforementioned “DOCX” or “TEXT”"DOCX" or "TEXT", things are different for PDF files. Once XTM Cloud receives the a file in PDF format as a source file, the system automatically converts it to “DOCX” in order to properly "DOCX" to extract text for translation correctly. However, once the job is finished, XTM Cloud does not convert generated target back to “PDF”, thus "PDF" so the target file is still in the “DOCX” "DOCX" format. As a result, it cannot, and will not, be properly retrieved correctly by AEM.
In the context of For PDF files, there is a workaround for this problem that consists in of sending a non-analyzable file as well as and employing a “workflow workflow for non-analyzable files” - files. This is a special feature in XTM Cloud. The whole process will be is described step-by-step in the next section.
| Note |
|---|
IMPORTANT! Taking into account the said XTM constraint, we kindly recommend using a different file format than “PDF”, for example “DOCX”, to To avoid setting an additional workflow for non-analyzable files on the XTM Cloud side, and to take this XTM Cloud constraint into account, we recommend that you use a different file format instead of “PDF". Example: "DOCX". |
...
Guidelines
The following guide presents the process of creating guide below describes how to create a new translation project alongside incorporation of a dummy file needed for retrieving and add a dummy file. XTM Connect – AEM needs this dummy file to retrieve a dedicated additional file, in the PDF format, by the AEM connector.
On the XTM Cloud side, go to Configuration → Settings → Workflow → Workflow options, check Workflow for non-analysable files, and save the changes(administrative privileges required!).
...
4. On the right-hand side, click Create, and then select Folder.
...
5. Provide Enter a Title, and then click Create. Both Private and Orderable options can be uncheckeddeselected.
...
6. Check a newly - created folder, click on Create, and then select Files.
...
7. Upload a PDF file without content (this is our dummy file). XTM Cloud will treat it as a non-analyzable file.
8. Go back to Adobe Experience Manager → Navigation, and go to Projects.
...
15. Add the source content that is to be translated and the dummy file you created in the previous steps.
16. Once the files are have been added, click on Translation Job in the middle of the tab screen, and go back to your project.
...
17. Expand the drop-down dropdown in Translation Job and send the project to XTM Cloud in your usual way.
...
18. On the XTM Cloud side (Project editor → Workflow), you will see that the dummy file was not analyzed.
Such a file is not present in the Files section, and we cannot manually upload target to it.
...
19. By dint of enabling “workflow for non-analazyble files”, we can make use of the Set workflow option.
Since this is a file without any translatable content, the Set workflow option will “bypass” the process of converting it for the into editable “DOCX” format, so it will still remain as in “PDF” format.
...
20. Choose a preferred the required workflow,and then click OK.
...
21. A newly - created workflow for this dummy file will appearis displayed.
If you will want to finish that job immediately after uploading a file, then you need to assign some resources here straightaway, immediately.
...
22. Go to Files. In the Target column, and you will see in the Target column that the actual target file can now be uploaded.
...
23. Search for your dedicated file , and then click Upload.
...
| Note |
|---|
IMPORTANT! The name of your uploaded file has to must be the same as the name of the dummy file in XTM Cloud! |
24. You should receive a confirmation message.
...
26. On the AEM side, go back to the respective relevant project, and, in the Translation Job pane, click three dots.
...
27. Your PDF file has already landed in been returned to AEM. Select the file, and then click on Reveal in Assets.
...
28. Click on Download.
...
29. Provide Enter a name, select desirable options, and finally click on Download to confirm the process.
...
30. Congratulations! You should now obtain receive your additional PDF file from XTM Cloud.