-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Icons/Emojis in markdown not rendered in output properly #405
Comments
Hmm, we should probably clarify that, indeed we don't support all of that As as a workaround, I'm pretty sure you can just use the corresponding unicode characters (i.e. ✓) - how they look then depends on your font though... |
Ok so how do we get actual emoji support? |
i haven't looked closely, but perhaps we could convert things like |
I'm migrating Slick from Ornate, so you might want to look at what Ornate
does.
…On Thu, Jan 13, 2022 at 2:52 AM Arnout Engelen ***@***.***> wrote:
i haven't looked closely, but perhaps we could convert things like 👍
into unicode in preprocessing somewhere, and then make sure to include a
font that renders them nicely in the theme?
—
Reply to this email directly, view it on GitHub
<#405 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAYAUHYADQZUDQCCFODQLTUV2ADTANCNFSM4KHG3QVA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
An issue was noted here with the doc for the Cloudstate project: The markdown for emojis/icons, which appear to be supported, don't appear in the output as images, but as the original markdown.
In this page in the Paradox doc, we say we support GitHub-flavored markdown (e.g. this style), which in turn supports Emojis. However, any use of ✔️, etc appear as the source markdown in the output.
I was able to verify this locally (by building the Cloudstate doc locally), but have not tried every variation.
The text was updated successfully, but these errors were encountered: