I’m running a community forum using Discourse and I noticed a display bug. Basically if someone posts with an iPhone using the built-in emoji keyboard AND the emoji has no space with the word it follows, then Discourse displays its own alphanumerical version of the emoji instead of its emoji.
Here is an example:heart_eyes:
In the above example I put 3 “heart eyes” emojis and the first one doesn’t display on Safari.
2 Likes
It would be interesting to see if posting from an Android phone does the same.
There is a site setting for this. This is not just on iPhone works like this. 
1 Like
Oh nice, I had exchanged with our Discourse guru and he didn’t mention this one. I think it should be enabled by default, don’t you think? Or is there some issues that can pop up from having it activated?
Nope, I don’t think it cause any issue. But if you enabled this you’ll have to rebuild the existing posts html or rebake posts to update emojis.
1 Like
This isn’t specific to Android or iPhone at all but a problem with our post cooker
The relevant part from the originally posted text is:
Here is an example😍😍😍
which is
Here is an example\xf0\x9f\x98\x8d\xf0\x9f\x98\x8d\xf0\x9f\x98\x8d
Looks like the cooker is translating the raw emoji into its name, but then doesn’t process it unless enable inline emoji translation is set.
tests:
word♥
word♥♥
word♥♥♥
word😍
word😍😍
word😍😍😍
word♥😍
word😍♥
word😍🖖
word🖖😍
word♥
word:heart:
word:heart:
word😍
word:heart_eyes:
word:heart_eyes:
word:heart:
word:heart_eyes:
word:heart_eyes:
word:vulcan_salute:
(you can see when there’s only a single emoji attached to a word it doesn’t get changed at all but when there’s more than one it breaks)
7 Likes