Moderator
Jan Dembowski
(@jdembowski)
Forum Moderator and Brute Squad
Please don’t say your motivation is for Chinese.
No one is saying that at all. The Han language reference was an example. Making WordPress more global is a stated and admirable goal.
See this video by Andrew Nacin at the last WordCamp San Francisco.
It was a great session, I enjoyed it. 😉
If you consider our feelings, you would not use the domain “w.org” that Chinese mainland can not directly access.
That’s a different situation and I do not believe this topic should devolve into a conversation about how some countries block the open Internet. I just don’t see the point; the censors in China are capricious. An open source project can’t be expected to cater to government censors anywhere.
Chinese WP user are discussing “how to remove emoji” since 4.2 was released.
That’s a legitimate discussion and is something that is easily accomplished in a number of ways. The easiest way is to install and activate this plugin.
https://wordpress.org/plugins/disable-emojis/
There are other plugins too and those may work for you as well. That one should do it for you.
Edit: This looks like a good one too.
https://wordpress.org/plugins/classic-smilies/
There should definitely be an option to disable this in the core
Asking people to install a plugin to disable it is like asking people to install a plugin to change their blog timezone, or admin email
There’s already an option to “Convert emoticons like 🙂 and 😛 to graphics on display” in Settings > Writing. Why not add another option which when ticked just removes the actions/filters like the plugin does
@webliberty I agree with you.
I assume that this change to the core is the cause of the following change to my website.
I was using:
◀
to generate a purple left pointing arrow (solid triangle). That’s the character I found on w3schools.com which I use as a reference.
After the upgrade, my purple arrow had been replaced by an image with a white triangle (pointing left) inside a blue box. How is that the same as a purple arrow?
Fortunately, I discovered that by changing it to
◄
the problem is fixed. But I now have to go through hundreds of posts and pages on all my websites to see what unexpected characters are appearing instead of the ones I put there.
@samuel Wood: I agree with @semrocc. The need to install a plugin to defeat core functionality seems, well, backwards. Shouldn’t it be the other way around? Shouldn’t the core provide the basic functionality and if you want emoji replacements, then install a plugin?
Once everybody cools down and thinks rationally about this change I’m sure you will introduce Setting to opt in/out to emoji replacements.
I discovered this new emoji script because it wasn’t being re-written to pull from CDN via w3-total-cache, which was costly in more than one way.
I agree that emoji should not be a part of the core. It should be a plugin that adds additional functionality. Please drop this “emoji cuteness” from the core and move it to the plugins directory. Focus the core on building a better WordPress.
@trailness Woo hoo! Added the code and emoji are gone! Many thanks.
Still think it was silly to force them on everyone by putting them in the core.
FYI, just using the code from @trailness will still cause some of your emoticons to not render, like one for “confused”. The Classic Smilies plug-in also redoes the array to point to actual images instead of character codes that don’t render.
After updating to 4.2.1, the WordPress editor has become unbearably slow, typing a few characters takes a few seconds to catch up (on a page about 20K characters).
I have an Intel Core i7, 16 GB of RAM, run Linux 64 bit and Chrome stable version 42.
While typing, Chrome’s CPU use shows in htop around 100% – 180% (> 100% means multiple CPU cores).
Using Chrome Developer Tools, I collected a JavaScript profile. The time is consumed in wp-emoji-release.min.js?version=4.2.1 and the hot path there is:
e > i > d > h.observeChildList
I really hope this serious front-end performance problem can be fixed, and also hope that emoji support becomes optional with a setting in WP itself, not plugin.
As @dccharron states a major deal breaker is that this breaks HTML character codes. We often use these instead of images or icon fonts to reduce HTTP requests. I’m concerned this update now replaces these character codes with graphics. In testing the following are replaced:
◀
▶
Lastly adding inline CSS and Javascript for a minor feature isn’t ideal.
On Chrome latest Mac OS, visiting the following site, relevant Emoji are automatically replaced by the browser. Why are you not leaving this to the native browser?
http://bohemianalps.com/tools/characters/#char-set-3
If this functionality needs to remain please:
– tie this functionality to the existing setting for converting emoji in the ‘writing’ setting panel.
– limit the aggressive replacement to the post / page content
+ 1 disable by default
Why this stuff is in core is beyond me. It would be perfect to have emoji as a plugin, not as a core feature.
Good Lord. Today I saw those emojis replacing utf-8 characters on our site and I immediately thought my boss had hired someone else to edit the templates and I was fired.
I think is not funny to roll out a change that will alter the looks of thousands of sites overnight.
Andrew Nevins
(@anevins)
WCLDN 2018 Contributor | Volunteer support
Here’s where you can keep up to date with WordPress and avoid finding out things on the day of their release: https://make.wordpress.org/core/
Particularly for Samuel Wood (Otto)
WordPress.org Tech Guy
& everyone else interested to keep wordpress clean:
I found this thread when searching for “turn off emojis”, yes those new icons that lack character.
While you are at it getting rid of that useless and unwanted new feature called emojis: Could you kindly also roll back that less-than half-baked new feature that scrolls the text editing window?
There have been too many foolish new features to mention, but this one particularly must try to win the trophy for the most foolish feature! Since that change we cannot concentrate on writing posts (as wordpress claims!), but instead in longer posts EVERY SINGLE new character typed or deleted scrolls the screen and we are searching for the location where we wanted to edit! Get the flawless old editing window back, that was the only way and best way to edit text without being annoyed by the software behind it!
If only you can manage these two roll-backs with the NEXT tiniest update, you’d help out the wordpress user community enormously. Thanks.
Just wanted to note that we also think automatic emoji substitution is a bad idea. The technical explanation for this new state of affairs feels a bit autistic in a Y2K manner…yes this new situation is a side-effect of implementing something important but shrugging off protests is oddly tone-deaf, given that UX concerns are paramount.
+1 for adding an option to disable
I don’t want unicode characters replaced by emojis.
