same emoji in different subject line not rendering

[Khyra]

Hi,

I'm wondering if someone could explain why the literal same emoji is displaying in one of my emails but not the other? I copy pasted the exact same Q-encoded symbol from here, yet my SLs are behaving differently.

[SanfordWhiteman]

Most likely because you have another character in the second Subject line that also needs to be Q-encoded. If you show the entire Subjects here I can help.

[Khyra]

Hi Sanford,

Here are the exact subject lines as they are posted in Marketo:

- Up to 40% off packages and more =?UTF-8?Q?=F0=9F=92=B8?=

- Jusqu=?UTF-8?Q?=E2=80=99?==?UTF-8?Q?=C3=A0?= 40 % sur les forfaits et plus =?UTF-8?Q?=F0=9F=92=B8?=

The second one is a French subject line with special characters that need to be Q encoded...I wonder if that's what's at play here?

Looking forward to hearing back!

[Jasbir_Kaur]

Hi @Khyra,

If it's not fixed yet, could you please let me know the emoji image what you want to show here so that, I can check the correct encoded code because the 2nd subject line working like as below for me?

Thanks!

Jasbir

[Khyra]

Hi Jasbir,

I removed the emojis from the SLs as I really needed to move forward with the email send but I'm curious about what you find so here's the requested info:

emoji: 💸

q code generated from this URL  : =?UTF-8?Q?=F0=9F=92=B8?=

Did you q encode the special characters? I have to in Marketo

[Jasbir_Kaur · Accepted solution]

Hi @Khyra,

This code is working fine, please try again and let me know if you are still facing any issue.

Jusqu=?UTF-8?Q?=E2=80=99?==?UTF-8?Q?=C3=A0?= 40 % sur les forfaits et plus =?UTF-8?Q?=F0=9F=92=B8?=

[SanfordWhiteman]

Well, the first one as pasted here on the community only has one non-ASCII character, the emoji. And that's the one that isn't working, correct?

I'm going to DM you a debugging address, to which I'd like you to send each email. Then I can inspect the source closely.

[CS2_Marketing2]

Hi, was there any update for the issue above? Im seeing the same thing happen.

[SanfordWhiteman]

I'll send you the same debugging address.

[Guitarrista82]

Hi @SanfordWhiteman ,

We're running into problems as well.

Our marketers have been using https://emojipedia.org/ to copy an emoji and then https://www.sendblaster.com/utf8-email-subject-encoder/ to encode the emoji for email.

Apparently this has been working fine until recently.

I came across your article here and pasted this emoji into the Q encoder you provided, then pasted the code into the subject line.

However, it appears like this when sent via an email campaign:

Any ideas what might be going wrong?

Thank you,

LK

[Guitarrista82]

That worked, thanks @SanfordWhiteman.

One question though, this article says that the apostrophe is an ASCII character. If that's the case, why does it need to be encoded?

[SanfordWhiteman]

Curly apostrophe ≠ straight single quote.

[Guitarrista82]

Got it...Similar to how a straight single quote will work in HTML but curly apostrophes are a no-no.

[SanfordWhiteman]

Well, not exactly the same reason.

If you mean the fact that you can use single quotes in <div class='myclass'> but not curly quotes <div class=‘myclass’> that’s because HTML decided to make ASCII single quotes and double quotes special because they’re easy to type and work in any encoding.

In theory, curly quotes could — at least now — be an alternative special character in addition to straight quotes, since a UTF-8 HTML page can include them verbatim. It just would be very confusing!

[SanfordWhiteman]

Probably because you forgot to encode the other non-ASCII character, the apostrophe.