Support » Requests and Feedback » Get rid of emoji

  • Resolved shanhard

    (@shanhard)


    Please make the new emoji additions added in 4.2 optional. we don’t want this on our site and would appreciate a way to turn them off in settings somehow.

Viewing 15 replies - 1 through 15 (of 29 total)
  • Agree with you. Strange decision to put this into the core…

    For the first time in several years I had to roll back a new version of WordPress to the old one. The Reason Is Emoji. What was the need to implement this for all users by default? That’s a pretty specific function! I want the old smilies!

    Give the opportunity to choose to use emoticons or Emoji. After updating all my emoticons partially replaced by Emoji, partially instead of black squares that looks terrible!

    Previously, I have added all the smilies under the comment form that commentators would put them in the form of a comment, now it will not start! Still the file names in the path to the images are broken, replacing the file name in Emoji and a link causes a 404 error. Do something, it looks bad.

    I suggest to remove Emoji from the core of WordPress and add them as a plugin, for example in a Jetpack.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    If you just want to disable the new emoji code, this will do it:
    https://wordpress.org/plugins/disable-emojis/

    If you want to disable the emojis and also revert all the smilies to the original ones, this will do it:
    https://wordpress.org/plugins/classic-smilies/

    Thread Starter shanhard

    (@shanhard)

    We dont want to have to install a plugin just to remove emojis!

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    We dont want to have to install a plugin just to remove emojis!

    Then you won’t be able to remove the emoji support.

    Any changes you wish to make to the core system can be done through plugins. Plugins are the way that the system is altered. If you don’t want to use a plugin, then nothing actually gets changed. Even core changes happen through feature plugins.

    Plugins are the backbone of the WordPress system. Most of the internal functionality in the core code is done through a plugin system. The plugin system is fundamental to how WordPress works.

    So live with the emoji’s, or use a plugin to solve the problem you’re having. That’s how it is.

    If you just want to rant, then do that on your own blog. These are support forums. We’re here to provide solutions, not to listen to you complain.

    Yes! We don’t want to install plugins to deactivate the functions of the WordPress core! Users should always be a choice, please make it to were you can choose to use the standard emoticons or emoji! It’s a matter of taste and the appearance of the site.

    And the fact that inserts emoji me unnecessary scripts and styles in the header – is clearly of no use to the blog and contrary to all the Google guidelines for optimization and acceleration of the work site. Emoji needs to be an option and not a forced imposition. The desire for functionality of social networks does not Bode well, if I wanted something would keep his diary in a social network, but WordPress is the best blogging engine, and it should not impose its users using emoji or other third-party services.

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    @webliberty: That is a view, certainly, but it’s one that contrary to the philosophical principles guiding WordPress development.

    “Decisions, not options.”

    It is highly unlikely that this will be made into an optional thing in the future. Therefore, you can either use a plugin to enable the type of emoticons you want, or you can not do that. You do have a choice. Plugins are the way that WordPress offers choices. Sorry if that’s not good enough for you, but they’re not going to put in a checkbox type of thing. That’s just not how WordPress works.

    @webliberty: I totally agree

    @samuel Wood: “Plugins are the way that WordPress offers choices” I think that what you said sums things up perfectly. This Emoji thing should have been made as an optional plugin that users have the choice to install or not. At the very least, it should be an option to enable or disable via the admin. There are many core features built into WordPress that can be enabled or not used via a choice in the admin…this should be one of them…its only common sense.

    I have now just installed 5 plugins and not very desirable whenever the innovation is to install a new plugin to disable something. The plugin you want to use to add new features, not to disable them.

    When I upgraded to WP 4.2 all my emoticons in the records turned into a terrible emoji and some were black squares. Do I have several hundred records manually edit to remove them from the pages?

    Because in WP there are many things where you can select. Why not give the option to choose between emoticons and emoji? After all code in the kernel file functions.php not much has changed.

    I read somewhere that emoji is not symbols and Unicode characters, however, if you inspect element in the browser all the Unicode character I also loaded the picture from the website s.w.org. If this is the same picture, then what’s the point? And the original picture size 72×72 px and they are scaled to a smaller size. Why to force the size of the emoji 1em is equal?

    Here is a look at the screenshot, I wasn deduced smiles at the comment form using the code: https://www.dropbox.com/s/9gfg8c29d0tzo4c/smilies.png?dl=0

    Now I can’t do that because the link to the picture in the form of breaks and a file called smiley face turns into a strange symbol, so the link doesn’t work. How will users be able to insert a smiley in a comment? Now how to implement it? Why not make a standard function to list all available emoji form?

    For users with mobile devices that may be convenient, but how to paste on a PC? Why do commentators have to open obscure third sites and copy the codes from there?

    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    This Emoji thing should have been made as an optional plugin that users have the choice to install or not.

    By and large, the emoji support came from underlying updates to the database code, to support 4-byte unicode characters properly. This enables character sets such as Han allowing for native support for languages such as Chinese, Korean, and Japanese. That’s the underlying motivation here. Emojis also use 4 byte characters, but don’t have a lot of widespread browser support, as such.

    I read somewhere that emoji is not symbols and Unicode characters, however, if you inspect element in the browser all the Unicode character I also loaded the picture from the website s.w.org.

    The actual core code to support emoji basically detects if your browser can support it, and then either uses the native browser support, or loads javascript to replace the unsupported characters with images from here on WordPress.org (w.org is our CDN’s domain). The images come from the twemoji set, made by Twitter, to allow for backward compatibility support in browsers that lack native support. Native support for emoji is used if detected, and is somewhat limited to Mac’s and iPhone’s at present, although Chrome has improved support recently and is presumably coming out with it soon.

    Note that even if you use my plugin to disable the emoji back-compat layers, Emoji *still work*. You can input them if you are using a device capable of inputting them, like iPhone or some Android keyboards. They will indeed save as unicode characters or as the converted unicode character if your database character set does not support it properly. They will still display as unicode characters if your browser supports them.

    In that respect, the emoji support is not optional at all, because it’s not really a new feature, it’s a side-effect of the underlying improved character set support. The emoji-specific code is a compatibility layer, to allow them to be seen in all browsers.

    Why not make a standard function to list all available emoji form?

    There’s freakin’ thousands of them. Currently 872 characters are supported by the twemoji set we released with. More are likely to be added in the future. Emoji isn’t a fixed set of emoticons, it is a character set, supported by the Unicode standard. They are indeed Unicode characters, and any added in the future will work regardless of the core having knowledge of them or not.

    If you want to insert emoji, you don’t use special codes. You use your keyboard to type them, like any other character. See here for more information:
    https://codex.wordpress.org/Emoji

    I have a modern browser Google Chrome 42, but instead of characters in the source code of a picture. I don’t know how to add Emoji in articles and comments, because I don’t know the code which is converted in the publication in icon.

    Will formulate the main negative aspects of Emoji:

    • no all browser support
    • it is not convenient to insert in the record and comments
    • in the header is loading unnecessary scripts and styles (one of the sites I never use emoticons and the checkbox in the settings I have disconnected to the characters in the picture did not become – why do I need scripts and styles if I don’t use them???)
    • when rendering a page is image scaling

    Ultimately, this new feature will ship the website, makes it slow, but if emoticons used not at all – it’s just too much garbage on the page.

    I don’t mind emoji, but I don’t want them imposed. Now I have a few sites and don’t know what to do with them, it makes me very angry, although I was always happy and on the first day updated WordPress to the new version. Now I was left unhappy.

    Maybe emoji is cool and modern, but it really has widespread support and recognition could not yet time for their implementation in the kernel? Again, add them to Jetpack is the only right decision. Why then the remaining modules of Jetpack are not added to the core WordPress?

    Please tell me how to get emoji under the comment form, so that when the icon is clicked it is added to the form? Do you plan to do in the future? Maybe it would be able to calm me down and wincing a bit still to upgrade to version 4.2

    PS:

    There’s freakin’ thousands of them. Currently 872 characters are supported by the twemoji set we released with.

    When I said it, we meant those that were previously in the form of emoticons in functions.php:

    ':mrgreen:' => 'icon_mrgreen.gif',
    ':neutral:' => 'icon_neutral.gif',
    ':twisted:' => 'icon_twisted.gif',
    ':arrow:' => 'icon_arrow.gif',
    ':shock:' => 'icon_eek.gif',
    ':smile:' => 'icon_smile.gif',
    ':???:' => 'icon_confused.gif',
    ':cool:' => 'icon_cool.gif',
    ':evil:' => 'icon_evil.gif',
    ':grin:' => 'icon_biggrin.gif',
    ':idea:' => 'icon_idea.gif',
    ':oops:' => 'icon_redface.gif',
    ':razz:' => 'icon_razz.gif',
    ':roll:' => 'icon_rolleyes.gif',
    ':wink:' => 'icon_wink.gif',
    ':cry:' => 'icon_cry.gif',
    ':eek:' => 'icon_surprised.gif',
    ':lol:' => 'icon_lol.gif',
    ':mad:' => 'icon_mad.gif',
    ':sad:' => 'icon_sad.gif',
    '8-)' => 'icon_cool.gif',
    '8-O' => 'icon_eek.gif',
    ':-(' => 'icon_sad.gif',
    ':-)' => 'icon_smile.gif',
    ':-?' => 'icon_confused.gif',
    ':-D' => 'icon_biggrin.gif',
    ':-P' => 'icon_razz.gif',
    ':-o' => 'icon_surprised.gif',
    ':-x' => 'icon_mad.gif',
    ':-|' => 'icon_neutral.gif',
    ';-)' => 'icon_wink.gif',
    Moderator Samuel Wood (Otto)

    (@otto42)

    WordPress.org Admin

    I have a modern browser Google Chrome 42, but instead of characters in the source code of a picture.

    Chrome on Windows does not yet have full emoji support. Chrome on OSX does, for the most part. It has to do with fonts and such.

    Thanks for the plugin. Explains why some of my old posts had characters that didn’t render. They got changed to Emojis which wouldn’t show in Firefox 37.0.2 in Windows 7 Pro.

    Dumb idea to add it into the core. Anyway…

    +1
    “Dumb idea to add it into the core. Anyway… “

    Put some option in setting for those not using it.

    @samuel Wood:

    This enables character sets such as Han allowing for native support for languages such as Chinese, Korean, and Japanese. That’s the underlying motivation here.

    少拿中国人说事儿!如果真考虑中国人,就不会用w.org这个我们根本没法访问的域名了。4.2一出,所有中国大陆的WP用户都在叫苦,严重影响了网站的访问速度。

    Please don’t say your motivation is for Chinese. If you consider our feelings, you would not use the domain “w.org” that Chinese mainland can not directly access. Chinese WP user are discussing “how to remove emoji” since 4.2 was released.

Viewing 15 replies - 1 through 15 (of 29 total)
  • The topic ‘Get rid of emoji’ is closed to new replies.