<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for labels:"emoji"</description><language>en</language><lastBuildDate>Mon, 12 Nov 2018 15:42:56 -0000</lastBuildDate><item><title>Only use twemoji when needed</title><link>https://forge-allura.apache.org/p/allura/tickets/8252/</link><description>Lots of emoji are already supported in many browsers.  I think it'd be nice to use native emoji when possible and only twemoji if needed.  However, that may mean sometimes things are shown native and sometimes they are twemoji images, so that inconsistency might not be good either.

I found https://github.com/pento/x1f4a9/issues/4 as an example of detecting if certain emoji are supported natively.  I don't see a built-in twemoji option for it.  One tricky part would be figuring out what emoji to detect.  Different browsers &amp; OS have different levels of emoji support.  For example, simple emoji like smile are probably supported, but newer emoji are not.  So I'm not sure how to practically if a check should look for support of "all" emoji or just certain ones, or different levels, etc.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 12 Nov 2018 15:42:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8252/</guid></item><item><title>Editor support for emoji short codes</title><link>https://forge-allura.apache.org/p/allura/tickets/8251/</link><description>Since most people won't have memorized lots of emoji names, it would be helpful for the markdown editor to provide prompts/help for it.

One method would be with the [CodeMirror hint](https://codemirror.net/doc/manual.html#addon_show-hint) addon.  So as soon as you type `:` it starts showing suggestions.  SimpleMDE is the package we use for markdown editors, and that is built on CodeMirror.  Both of which are due for an upgrade, if that helps at all.

A button in the toolbar would be helpful too for people that don't even know that `:foo:` shortcode format is a thing.  It could suggest some popular ones, potentially with a search for more (but not sure how easy that is).  Buttons are controlled with the SimpleMDE config.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 23 Oct 2018 09:46:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8251/</guid></item><item><title>Make twemoji skip some non-emoji unicode</title><link>https://forge-allura.apache.org/p/allura/tickets/8250/</link><description>&amp;trade; &amp;copy; &amp;reg; and perhaps more are not really emoji, but twemoji changes those to images.  This is particularly noticable on https://forge-allura.apache.org/ where "tm" is in the project name and footer.

https://github.com/twitter/twemoji#exclude-characters-v1 indicates its possible to do that, although those docs might be for v1 api? So maybe different</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:22 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8250/</guid></item><item><title>Handle github emoji</title><link>https://forge-allura.apache.org/p/allura/tickets/6923/</link><description>Emoji (e.g. :+1: thumbs up) are heavily used on some GH projects and would be good to carry over during import. However, the images are not licensed for us to redistribute https://github.com/github/gemoji/blob/master/LICENSE  Maybe we could use https://github.com/Genshin/PhantomOpenEmoji if the mapping is straightforward.  We also need to decide if we want an emoji-like feature throughout our markdown or handle this just at import.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:19 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6923/</guid></item></channel></rss>