SOLVED

Re: Using Q code of emoji in Subject-line cause issue in gmail

Go to solution
raiashutosh
Level 2

Hi Guys,

I used an emoji in our subject line, using Q-code (after reading Stanford's blog).
The emoji is rendering properly in all email clients, however, in Gmail mobile, it is adding extra space in the subject line.
See the below example:
 

raiashutosh_0-1643890172698.png

 

raiashutosh_1-1643890194698.png


I am using the below code in the subject line
=?UTF-8?Q?=F0=9F=99=8C?= NEW! Master's in Information Technology

raiashutosh_2-1643890283003.png


Anyone has experienced this before? please let me know a way aound.

1 ACCEPTED SOLUTION
SanfordWhiteman
Level 10 - Community Moderator

Only put characters that require Q-encoding between opening =?UTF-8?Q? and closing ?= sequences (i.e. only the emoji and the apostrophe).

 

View solution in original post

4 REPLIES 4
SanfordWhiteman
Level 10 - Community Moderator

I am using the below code in the subject line

=?UTF-8?Q?=F0=9F=99=8C?= NEW! Master's in Information Technology


I don’t think you are. 🙂

 

I think that single straight quote is actually a curly quote, i.e. apostrophe. Which means it too needs to be Q-encoded. If you have one manually Q-encoded non-ASCII character, they all need to be manually encoded or Marketo... reacts poorly. Apostrophes are not allowed without encoding.

raiashutosh
Level 2

Hi @SanfordWhiteman ,

I have encoded the curly apostrophe in the subject line (=?UTF-8?Q?=F0=9F=99=8C NEW! Master=E2=80=99s in Information Technology?=) attached a screenshot of the preview also. Still, I can see the same output in Gmail mobile

raiashutosh_0-1644239697815.png


I also tried removing the apostrophe altogether. 

Thanks!

SanfordWhiteman
Level 10 - Community Moderator

Only put characters that require Q-encoding between opening =?UTF-8?Q? and closing ?= sequences (i.e. only the emoji and the apostrophe).

 

raiashutosh
Level 2

Thanks, @SanfordWhiteman !  I got it now.