Curved quotes converted to ASCII code

[Milan_Vucetic]

Hi all,

whenever curved quotes are used from AEM templates, after synchronizing in Adobe Campaign are shown in ASCII code.

Any suggestions how to overcome this?

Regards,

Milan

[Darren_Bowers · Accepted solution]

Its probably just a normal function of the serialiser/deserialiser to HTML encode certain characters to make the HTML source validate against your source DTD. Its perfectly valid and shouldn't cause any issues in your rendered HTML content. Its the slightly more valid code for an apostrophe character in HTML. ' is the other valid encoding for an apostrophe (see link)

Is there any reason you dont want this code in your HTML source?

[Milan_Vucetic]

Hi @DarenOrigin,

as you said this does not impact HTML generation a lot, but as we use a Text content customers can receive this unreadable cod in text version of email.

Anyway, the bigger issue is when we use some conditional personalization and delivery failed every time on Text personalization because value is not under quotes.

We want to avoid this failure in the deliveries.

Regards,

Milan

[Darren_Bowers]

Hi Milan - We found we had to remove these codes from the Text Alternative too. The auto-generated text was always terrible, so we made it part of our QA to check and remove these from the deliveries. Can you explain a bit more about the personalisation issue? Cheers Darren

[Milan_Vucetic]

Hi @DarenOrigin,

for example we have a conditional code like <%= targetData.customerSegment = "Resident" %> and if curved quotes are used instead of straight (from my example) after synchronization we got condition in Text content like this:  <%= targetData.customerSegment = &#34Resident&#34 %> and delivery fails. 

Therefore, I am looking for easy way to avoid this in Text content. 

Business user correct this when is visible but often not.

Regards,

Milan

[Darren_Bowers]

There are some best practices that Adobe recommend for creating email templates in AEM: https://helpx.adobe.com/au/experience-manager/6-5/sites/administering/using/best-practices-for-email... - it could be something to do with the content-type declaration. It could also be a bug so worth opening a Neolane support ticket