Hi
Can 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 AEM, where the displayed page renders them back to the & character. This all works as expected except for jcr:title and jcr:description, where the entity is retained after translation.
Example:
Source text:
Apples & Pears
Extracted xml content:
<translationObjectProperties>
<property isMultiValue="false" nodePath="/content/we-retail/language-masters/de/CC_nameV1/jcr:content" propertyName="jcr:title">Apples & Pears</property>
</translationObjectProperties>
retruned translation in the AEM title field is: Apples & Pears
AEM TIF is not rendering it back to the & character
Is this expected behaviour and is there somethign specific in title and description field where & should not be used?
thanks
Solved! Go to Solution.
Views
Replies
Total Likes
Hi @nwatson69 Which translator you are using ?. Standard translators do not encode these characters after translation. If you check with Microsoft translator(available with AEM), It keep character in jcr:title and jcr:description same after translation.
Can you check if your translator has some configuration to manage this.
Hi @nwatson69 ,
That is expected behaviour for some special characters, Faced similar issue here: https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/rte-link/m-p/451393
I don't know what was the exact issue causing it, unfortunately couldn't able to find it yet, hence raised it to Adobe support team.
Regards,
Santosh
Hi @nwatson69 Which translator you are using ?. Standard translators do not encode these characters after translation. If you check with Microsoft translator(available with AEM), It keep character in jcr:title and jcr:description same after translation.
Can you check if your translator has some configuration to manage this.
Views
Likes
Replies
Views
Like
Replies
Views
Likes
Replies