A discussion on configurable ASCII-style emojis in Discourse has started. elberet proposes making the ASCII-smiley to emoji translations configurable in the admin interface, as they have custom translations (e.g. ^^ for , ^^; for ) that differ from the defaults. elberet references a previous discussion about adding a pre-processing step to the Vanilla importer to translate emoticons.
elberet envisions this as a customization feature with its own unique UI and sam agrees, but thinks it may be too sophisticated for a site setting.
Benno asks where to find the current translations, and elberet points to the Discourse emoji plugin’s source code and a list of available emojis. The default ASCII shortcuts are defined in the emoji.js.erb file, which would need to be patched locally to customize shortcuts.
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…
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.
, 
and 
, and really don’t like some of the default translations, e.g. 
instead of the normal smiley…