Emojis

[hut8]

Thanks very much for moving this out into its own repository.

I saw your goal is to make this equivalent to the output of api.github.com/markdown/raw, which is awesome. The emojis are missing for now, however:

liam@hut8 ~ % curl -H"Content-Type:text/plain"  --data ":+1:" https://api.github.com/markdown/raw
<p><img class="emoji" title=":+1:" alt=":+1:" src="https://assets-cdn.github.com/images/icons/emoji/unicode/1f44d.png" height="20" width="20" align="absmiddle"></p>

If I implemented this, would you accept a PR?

[dmitshur]

Hi, I'm glad this package is helpful!

You are right, the goal is to produce output equivalent to https://developer.github.com/v3/markdown/#render-a-markdown-document-in-raw-mode, which includes Emoji, therefore github_flavored_markdown should support Emoji as well.

A PR would be very appreciated! Before you spend too much time on it, can you please outline how you're planning to approach it, so I can review or give some suggestions.

Thanks a lot!

[hut8]

Thank you very much. My blog is powered by Hugo and I would say rendering these things is an absolutely critical feature.

I'm really surprised how complete the GitHub API is. Here's a list of all their emojis:
curl -L https://api.github.com/emojis

It depends on how close you really want the output to be to GitHub's. If you actually want it to be identical, i.e., linking to GitHub's CDN, then generating the output is straightforward. If you want the emojis to be part of the document so that it's usable without hot-linking or Internet access, I'd probably generate data URLs.

I haven't actually looked at the internals of your project much, but I have written a lexer and parser and I'll get back to you on that tomorrow. Thanks for the quick reply.

[dmitshur]

The output should be functionally equivalent, it doesn't need to be byte-for-byte the same. As long as the output produces same or similar looking images.

It depends on how close you really want the output to be to GitHub's. If you actually want it to be identical, i.e., linking to GitHub's CDN, then generating the output is straightforward. If you want the emojis to be part of the document so that it's usable without hot-linking or Internet access, I'd probably generate data URLs.

This is a good question. I'm not sure what's best. I think linking to the "https://assets-cdn.github.com/images/icons/emoji/unicode/..." urls is probably simplest, and it'll ensure the result emoji images match those generated by the GitHub Markdown API endpoint. But if you're making a heavy use of GFM on your site, you may want to host the assets yourself.

The current output already expects you to "bring your own" css for styles and it the example suggests using "//cdnjs.cloudflare.com/ajax/libs/octicons/2.1.2/octicons.css" for octicons (which you can host yourself, of course). Perhaps a similar approach for emoji would be best, if possible?

I haven't actually looked at the internals of your project much, but I have written a lexer and parser and I'll get back to you on that tomorrow. Thanks for the quick reply.

The package code is pretty short. It is a little messy in parts, sorry in advance about that. I made it in limited spare time and I was focusing on functionality first, that's my excuse. :P

[dmitshur]

By the way,

My blog is powered by Hugo

I'm not closely familiar with Hugo, but I thought it doesn't use this package. Or can you use any Markdown processor with it that you want, including github_flavored_markdown?

[hut8]

Hugo doesn't use this package, but it does use blackfriday to render the site and I don't think it would be too hard to modify it. After all, the blackfriday README references this project.

[dmitshur]

github_flavored_markdown is a Markdown HTML renderer that is largely based on blackfriday Markdown HTML renderer. It reuses 90% of its functionality, and adds some tweaks (like fenced code block highlighting, and clickable header anchor links).

If you add support for Emoji in github_flavored_markdown directly, it will only be here. If you add it to blackfriday under a configuration option, then github_flavored_markdown can simply reuse it.

After all, the blackfriday README references this project.

It does because I added it there. :) Thanks for reminding me, as I need to update its import path! (Done in russross/blackfriday@10880f6.)

[thewhitetulip]

Are we going to have emoji support? I'd love to help if required 👍 I am writing a simple todo list manager github.com/thewhitetulip/Tasks and it'd be cool to have emojis directly in our awesome markdown library!

[dmitshur]

Hey @thewhitetulip,

Help would be very appreciated! If you can make a PR that adds this functionality, I'll be happy to review it.

I suggest showing me an idea of what approach you're taking as soon as possible, so I can let you know if it looks on track or not, to avoid wasting time.

[thewhitetulip]

Hey @shurcooL Well I have no idea how to add emojis 😄 But I'd be happy to work on the idea if shown the way :-)

[dmitshur]

Have you read the rest of the comments in this thread? Specifically #1 (comment), and the one above it? They go over in quite a bit of detail about how to approach this.

[thewhitetulip]

Well, to be honest I had gone through it, but not in the depth which the topic deserved. If I worked on a PR I'd like to not link blindly the the github CDN I'd like to build something which gives emoji support even without an Internet connection, the above comment thread mentions this data URLs., what are they?

Correct me if I am wrong in this approach

1. We'll have to download the image files and host it along with the rest of the package
2. It is a matter of replacing the emojis with their respective images then

Is it this simple?

[dmitshur]

I'm not sure if we should be generating output that uses image URLs from the internet, or serving the emojis ourselves so they work even when offline.

GitHub's API obviously produces Markdown output that uses online emoji links.

However, I can see that being able to generate Markdown that works when offline can be nice too.

I hate to say it, but perhaps this should be an option? Which of the two you use depends on your desires/needs.

For serving emojis, perhaps another Go package can be employed. Something similar to https://github.com/shurcooL/octicons, except for emojis.

I think it might be better/simpler to start with relying on online links, and then consider serving emojis locally as an enhancement.