Closed SomeWeekendReading closed 3 years ago
Please open an issue at https://github.com/kramdown/parser-gfm/issues - thanks!
Done.
On Tue, May 4, 2021 at 7:22 PM Thomas Leitner @.***> wrote:
Please open an issue at https://github.com/kramdown/parser-gfm/issues - thanks!
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/gettalong/kramdown/issues/716#issuecomment-832310762, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARC3GOWQDGEI3VX67QS2L6TTMB6UXANCNFSM44DHZTXQ .
I'm using kramdown as the default markdown engine in a blog generated by Jekyll. For the most part, I'm sticking to Github-flavored Markdown (GFM) and that seems to be reasonable.
GFM advertises certain emojis as being available, but some experiments show that kramdown does not render them. In particular, I've been trying to use some flag icons for a blog post about language translation: :jp:, :fr:, :india:, :it:, :cn:, :ru:, :greece:, :romania:. They get rendered as text.
There's an example in a blog post here.
I realize emojis are pretty silly and may not be a priority.