HiCan someone help with how & character should be used in AEM sites textual nodes.When text is extracted from AEM through the translation integration framework, & characters are converted to entities (&) in the exported xml. The entities are preserved during translation and imported back into AE...

we've investigated this further and find it only happens when the AEM translation framework creates a launchreproduce this on a Vanilla AEM instance under following conditions:The page + child pages need to exists in the master languageThe page + child pages need to exists in the other languageThe c...

During a translation project, only when the launch is created on AEM (becasue its an update to an already translated page), not only the page you which to translate is included but also all of its child pages. When the project is sent to translation vendor, the page to translate is send, and the chi...

This is the scenario we are facing:1. Create a translation project with a page and its child pages. All pages are translated, and appear in langauges as expected.2. Create a new translation project with the same page (because the English page been updated), but do not include child pages (because th...

We are using the getTranslationObjectPreview() endpoint in our integration to retrieve preview packages from AEM during project creation. The preview packages are sent to the translation vendors for context during translation.The solution works perfectly with WeRetail site.But with some customers, w...

HiWe have a translation integration built on the BootstrapTranslationService. As part of that integration we are using the below instructions/method to call for the preview package, generated by AEM on project creation:"If the Preview feature is enabled, then the file will be generated automatically...