# Configurable ASCII-style emojis

**URL:** <https://meta.discourse.org/t/configurable-ascii-style-emojis/19294>\
**Category:** Feature\
**Created:** [2014 年8 月 26 日 13:20 UTC](https://meta.discourse.org/t/configurable-ascii-style-emojis/19294 "2014-08-26T13:20:47Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

作者： ![elberet](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/elberet/32/122404_2.png) [@elberet](https://meta.discourse.org/u/elberet)\
发布日期： [2014 年8 月 26 日 13:20 UTC](https://meta.discourse.org/t/configurable-ascii-style-emojis/19294/1 "2014-08-26T13:20:47Z")

</div>

Counter suggestion: the ASCII-smiley to emoji translations in Discourse’s emoji plugin should be configurable in the admin interface.

So far, I’ve been dragging around a patch file that gets applied on Discourse updates, because I’m my users are accustomed to stuff like `^^` for 😄, `^^;` for 😅 and `T_T` for 😭, and really don’t like some of the default translations, e.g. `:D` which should be 😆 instead of the normal smiley…

Circling back to the discussion from [[Paid] Need a Vanilla 2 Import tool](https://meta.discourse.org/t/paid-need-a-vanilla-2-import-tool/14852/39):

> [@\[Paid\] Need a Vanilla 2 Import tool](https://meta.discourse.org/t/paid-need-a-vanilla-2-import-tool/14852/39):
>
> I’m fine with adding a pre-processing step in the [vanilla importer](https://github.com/discourse/discourse/blob/master/script/import_scripts/vanilla.rb) to _translate_ these emoticons to the ones we support if there is a match. PRs are welcome 😉

With this in place, the Vanilla2 importer could just install a translation table that matches the emoticons the Vanilla2 emoji plugin defines instead of converting the posts.

---

_[View the full topic](https://meta.discourse.org/t/configurable-ascii-style-emojis/19294)._