The emoji library from pypi is BSD-licensed so that's good.  And uses shortcode 
formats that are common on github, slack, etc.

I tried out your commit and it seems to work ok, but perhaps too broadly.  If 
you have something in backticks or a code-block, those shouldn't be replaced.  
Like this I mean:

````
`:smile:`
or
```
:smile:
```
````

So it would have to understand markdown semantics.  A little googling turned up 
a few libraries you could try that might do it 
https://facelessuser.github.io/pymdown-extensions/extensions/emoji/ and 
https://pypi.org/project/mdx_unimoji/ (not updated in many years though).  Want 
to try those out?

Our initial (current) emoji support is twemoji js/css for display.  A few 
concerns/ideas for development back then were: 
https://forge-allura.apache.org/p/allura/git/merge-requests/135/#4df8/4a2f/9b97 
 

* other outputs like email & rss feeds & apis - these seem good
* having autocomplete suggestions with CodeMirror's showHint functionality 
would be a logical next step.  Otherwise people will have to know the names of 
all the emoji.  Implementing this would also could give us the option of 
changing `:smile:` to 😄 (unicode) right as you type and not even use the short 
codes then.  Not sure how easy or hard that would be, but it could be nice 
alternative way of doing this.


---

** [tickets:#6923] Handle github emoji**

**Status:** in-progress
**Milestone:** unreleased
**Labels:** github import 
**Created:** Tue Nov 26, 2013 11:00 PM UTC by Dave Brondsema
**Last Updated:** Sat Oct 13, 2018 03:43 PM UTC
**Owner:** nobody


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.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed 
to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at 
https://forge-allura.apache.org/p/allura/admin/tickets/options.  Or, if this is 
a mailing list, you can unsubscribe from the mailing list.

Reply via email to