<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Using &amp;amp; in jcr:title and jcr:description fields - cause translation issue in Adobe Experience Manager Questions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-amp-in-jcr-title-and-jcr-description-fields-cause/m-p/458457#M132084</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="2397979"&gt;&lt;/LI-USER&gt;&amp;nbsp; 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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you check if your translator has some configuration to manage this.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Jun 2022 22:34:03 GMT</pubDate>
    <dc:creator>sunil_kumar_</dc:creator>
    <dc:date>2022-06-28T22:34:03Z</dc:date>
    <item>
      <title>Using &amp; in jcr:title and jcr:description fields - cause translation issue</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-amp-in-jcr-title-and-jcr-description-fields-cause/m-p/458390#M132062</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;Can someone help with how &amp;amp; character should be used in AEM sites textual nodes.&lt;/P&gt;&lt;P&gt;When text is extracted from AEM through the translation integration framework, &amp;amp; characters are converted to entities (&amp;amp;amp;) in the exported xml. The entities are preserved during translation and imported back into AEM, where the displayed page renders them back to the &amp;amp; character. This all works as expected except for jcr:title and jcr:description, where the entity is retained after translation.&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;Source text:&lt;BR /&gt;Apples &amp;amp; Pears&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Extracted xml content:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;lt;translationObjectProperties&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;property isMultiValue="false" nodePath="/content/we-retail/language-masters/de/CC_nameV1/jcr:content" propertyName="jcr:title"&amp;gt;Apples &amp;amp;amp; Pears&amp;lt;/property&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;lt;/translationObjectProperties&amp;gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;retruned translation in the AEM title field is:&amp;nbsp;Apples &amp;amp;amp; Pears&lt;BR /&gt;AEM TIF is not rendering it back to the &amp;amp; character&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Is this expected behaviour and is there somethign specific in title and description field where &amp;amp; should not be used?&lt;BR /&gt;&lt;BR /&gt;thanks&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 16:52:56 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-amp-in-jcr-title-and-jcr-description-fields-cause/m-p/458390#M132062</guid>
      <dc:creator>nwatson69</dc:creator>
      <dc:date>2022-06-28T16:52:56Z</dc:date>
    </item>
    <item>
      <title>Re: Using &amp; in jcr:title and jcr:description fields - cause translation issue</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-amp-in-jcr-title-and-jcr-description-fields-cause/m-p/458430#M132073</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="2397979"&gt;&lt;/LI-USER&gt;&amp;nbsp;,&lt;/P&gt;&lt;P&gt;That is expected behaviour for some special characters, Faced similar issue here: &lt;A href="https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/rte-link/m-p/451393" target="_blank" rel="noopener"&gt;https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/rte-link/m-p/451393&lt;/A&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 18:49:36 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-amp-in-jcr-title-and-jcr-description-fields-cause/m-p/458430#M132073</guid>
      <dc:creator>SantoshSai</dc:creator>
      <dc:date>2022-06-28T18:49:36Z</dc:date>
    </item>
    <item>
      <title>Re: Using &amp; in jcr:title and jcr:description fields - cause translation issue</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-amp-in-jcr-title-and-jcr-description-fields-cause/m-p/458457#M132084</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;LI-USER uid="2397979"&gt;&lt;/LI-USER&gt;&amp;nbsp; 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.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Can you check if your translator has some configuration to manage this.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 22:34:03 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/using-amp-in-jcr-title-and-jcr-description-fields-cause/m-p/458457#M132084</guid>
      <dc:creator>sunil_kumar_</dc:creator>
      <dc:date>2022-06-28T22:34:03Z</dc:date>
    </item>
  </channel>
</rss>

