[wp-trac] [WordPress Trac] #64318: ↗ should not be replaced by Twemoji

[WordPress Trac]

#64318: ↗ should not be replaced by Twemoji
--------------------------+---------------------
 Reporter:  Joen          |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  7.0
Component:  Emoji         |     Version:  4.2
 Severity:  normal        |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+---------------------

Comment (by westonruter):

 Replying to [comment:15 siliconforks]:
 > So if you have the sequence U+2197 (NORTH EAST ARROW) followed by
 U+FE0E, Twemoji will (correctly) avoid replacing it with an image. ¶ If
 you really want the text presentation, this is probably the best way to do
 it.

 The problem is existing content out there that doesn't have U+FE0E, right?
 Existing content expecting the text presentation unexpectedly gets the
 emoji presentation when upgradinging Twemoji. It would be a good idea for
 newly-inserted characters to add this U+FE0E, but I presume only for
 characters inserted via some integrated symbol inserter (like TinyMCE
 had). If the character were inserted by the operating system's character
 picker, then it wouldn't include this U+FE0E, presumably.

 So would a new filter be required for `the_content` to inject this U+FE0E
 after the set of characters that we determine? But then this wouldn't
 really be any different than the JS-based exclusion? Both are programmatic
 means to the same end.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64318#comment:17>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform