Stripping UTF codes/emojis in subject | Community
Skip to main content
Travis_Schwartz
Travis_Schwartz
Level 4
Feb 6, 2020 5:46 PM UTC
Solved

Stripping UTF codes/emojis in subject

I need help.

 

In the past, I had used converters to program emojis into the subjects of my emails.

 

For example, I've used these converters in the past:

And they worked wonderfully.

 

Now the email subject is displaying the UTF code when I send instead of the emoji, or clear box. Has something changed? Is this not supported anymore?

    SanfordWhiteman
    SanfordWhitemanAccepted solution
    Level 10
    Feb 6, 2020 7:29 PM UTC

    Those characters are not ASCII, so they should also be Q-encoded.

    View reply

    6 replies

    Travis_Schwartz
    Travis_SchwartzAuthor
    Level 4
    Feb 6, 2020 7:10 PM UTC

    An update... apparently using an en-, or em-dash in the subject line causes the emoji to not render. I don't know why, but those two marks specifically cause the code to display instead of the emoji.

     

    Hyphen works:

    en-dash doesn't:

    em-dash doesn't:

    Translate
      SanfordWhiteman
      SanfordWhitemanAccepted solution
      Level 10
      Feb 6, 2020 7:29 PM UTC

      Those characters are not ASCII, so they should also be Q-encoded.

      Translate
      Travis_Schwartz
      Travis_SchwartzAuthor
      Level 4
      Feb 6, 2020 7:54 PM UTC

      Is there a reason that the dash would display/render when it isn't coded, yet it would show the code instead of the emoji that was q-encoded?

      to me, it feels like it should render the emoji and the dash space be blank because it wasn't coded.

      Translate
      SanfordWhiteman
      SanfordWhiteman
      Level 10
      Feb 6, 2020 6:32 PM UTC

      Have you tried putting the output of those converters (the Q-encoded output) into a Velocity token, then using that {{my.token}} as the Subject? Velocity tokens keep original formatting, for the most part, unlike other tokens or direct text entry.

       

      P.S. Just to avoid confusion, you wouldn't be seeing "UTF-8" (which is a binary encoding) but perhaps are seeing partial Q encoding (which is an ASCII encoding of UTF-8) because Marketo is truncating something.

      Translate
      Terms & ConditionsAccessibility statement

      Loading footer...