I tried messing with the emoji short code (:ivory_coast: and using different unicode options for circumflex on the “o” of “côte_d_ivoire”), but it didn’t fix things.
Curious if this issue will show up here on meta when I post this…
UPDATE: I see that the issue doesn’t occur here on Meta. I have tried typing the :côte_d_ivoire: elsewhere in my text so that it’s not next to another emoji short code and I still get the same issue. Note that I myself have not typed in the emoji shortcode. It’s converted automatically by my Discourse install once I input the emoji itself. This doesn’t occur here on Meta.
I’m not sure I can see the 🇨🇮 emoji in the discourse emoji-picker, so maybe it’s an issue from changing away from the apple emoji set to one of the new alternatives? Emojis update
@joffreyjaffeux looks like after d38acc5df120e6f3a89d04cf746d2fe03534be29 this broke, seems there’s some inconsistency w.r.t. the diacritic in the emoji gem?
should we add an alias côte_d_ivoire → cote_d_ivoire?
(or maybe the version with the ô should be primary? I don’t know what the “correct” primary is here)
or maybe we just don’t handle diacritics in emoji properly
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.
I tried turning this on and I still had the same issue using the iOS emoji picker.
For a future fix re: the diacritics, you might need to also watch out for precomposed (e.g., a single glyph with o and the diacritic baked in) and decomposed (e.g., o + ^ combined separately) unicode characters