Closed cabello closed 9 years ago
Okay, I was doing some research on how to implement this and it looks like the Javascript option is not a good one, because very few projects have emoticons on documentation and the Javascript needs two assets: javascript and css file to work.
The other option that looks good is to have this on backend and after the markdown transformation apply a regex like :[^\s]+:
to replace it by a class name or a base64 of the emoticon file, what do you think?
I think they would be nice to have, but I wouldn't consider it unless I was presented with a really good and simple solution.
Want to take a stab at it?
Definitely I started trying yesterday but I would like to hear your opinion before going ahead, imagine if you say: "emoticons are useless sorry" I could help on another issue then.
Does Github support them in READMEs? I'd like to stay as close to Github as possible.
Yeap, they support it.
+1 emoji support
:+1:
This is now working.
Thanks for your patience!
It would be nice to translate
:octocat:
to :octocat: and all other emoji defined in http://www.emoji-cheat-sheet.com/.We could use: https://github.com/hassankhan/emojify.js
It looks pretty straightforward.