[wp-trac] [WordPress Trac] #36955: Remove emoji from core. PLEASE
WordPress Trac
noreply at wordpress.org
Tue Aug 2 17:17:02 UTC 2016
#36955: Remove emoji from core. PLEASE
------------------------------+-------------------------
Reporter: Online-marketing | Owner:
Type: enhancement | Status: closed
Priority: normal | Milestone:
Component: Emoji | Version: 4.5.2
Severity: normal | Resolution: maybelater
Keywords: | Focuses:
------------------------------+-------------------------
Changes (by DrewAPicture):
* status: reopened => closed
* resolution: => maybelater
Comment:
Replying to [comment:4 Online-marketing]:
> I sincerely appreciate having the end user in mind, when one designs a
core framework. But on the other hand I would even more be grateful to
developers who might give the publishers, who use the software on a daily
basis the chance to not use so called user experience enhancements from
the start without having to alter code or to install a plugin to not to.
>
> Furthermore I would develop a plugin for those users, who really want to
use Smileys, Emojis and whatever else they would want to implement. The
goal is to slim down and not to bloat. Every unneccessary byte is a byte
too much, especially if i have to install about 30 plugins to make my
wordpress run in desired ways.
To be fair, `utf8mb4` support covers far more than just ''emoji'' or
''smileys'' – it also covers displaying native character sets for
languages like Chinese, Japanese, and Korean. I think it's safe to say
that publishers worldwide benefit from wider language support in
WordPress, so while some may not realize the immediate value, others
absolutely do.
WordPress is currently [https://wordpress.org/about/stats/ translated] for
more than 150 locales around the world, and it's with that worldwide
audience in mind that we extend language support wherever we can (within
reason).
It seems to me that a basic tenet of content management would be to avoid
placing unnecessary burdens on content creators by doing our best to
display content as it's intended to be displayed. The shims that exist in
core WordPress are extending an olive branch to browsers that don't
support modern language standards – it's not bloat, it's basic language
support.
'''I'm re-closing the ticket as ''maybelater''. Tickets do not need to
remain open for discussion to continue.'''
--
Ticket URL: <https://core.trac.wordpress.org/ticket/36955#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list