Enable translation for newly referenced PDFs on AEM pages
When a PDF is added to a page in Adobe Experience Manager (AEM) and the page is sent for translation, the PDF is only translated if language copies already exist in Digital Asset Management (DAM). This article explains the required configuration changes so new or untranslated PDFs are automatically included in translation jobs and correctly linked to translated pages.
Description description
Environment
Adobe Experience Manager (AEM) Managed Services, v6.5
Prerequisite
The target DAM language root must already exist.
Issue/Symptoms
When sending a page containing a newly added or untranslated PDF for translation, the translated page continues to reference the original language PDF instead of creating and linking a language-specific copy.
Resolution resolution
- Go to Tools
>Cloud Services>Translation Cloud Services>Translation Integration>Default Configuration and click Edit. - Change the Translate Page Assets setting from Do Not Translate to Using Sites Translation Workflow, and save the Configuration.
- Go to Tools
>General>Translation Configuration. - Open the configuration that applies to your content path (for example,
/content). - Select the relevant path in the left panel (for example,
/contentor your site’s context). - Switch to the References tab, and add a new reference rule.
- Set the resource type to the resource type of your PDF Viewer component.
- Set the reference attribute to the property that points to the PDF asset.
- Ensure Create Language Copy is checked.
- Save the Configuration.
- Verify the fix by sending a page with a newly referenced PDF for translation and confirming that a language copy of the PDF is created in DAM and correctly linked on the translated page.
Notes: If the changes do not take effect immediately, toggle the Create Language Copy option by unchecking and rechecking it in the UI, then save again.
Additional information
- Use the correct resource type and reference attribute in your custom or standard PDF Viewer component.
- If you use custom workflows for link translation, make sure they do not override or conflict with these settings.
- If the issue continues, check that you saved all configurations and activated them in your production environment.