You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.
I had set TYPOGRIFY = True in my pelicanconf.py only to find that it breaks some functionality of ipynb posts. Specifcally, typogrify applies <span> elements to parts of the inline CSS, which ends up breaking those styles as well as MathJax. That is probably a bug in typogrify, but I thought I'd point it out here.
Obviously the easiest way to fix the issue is to disable typogrify.
The text was updated successfully, but these errors were encountered:
Yeah, sorry to even open a ticket about this. It's not something that you need to worry about fixing, I think. I just thought this conflict should be documented in some way, because it cost me a while to figure out what was going wrong. Maybe adding a brief note in the README would do it.
Thanks for opening the ticket. Spent some time trying to figure out why my strings don't get colored red. I found the weird s inside color properties, but didn't know why.
I had set
TYPOGRIFY = True
in mypelicanconf.py
only to find that it breaks some functionality of ipynb posts. Specifcally, typogrify applies<span>
elements to parts of the inline CSS, which ends up breaking those styles as well as MathJax. That is probably a bug in typogrify, but I thought I'd point it out here.Obviously the easiest way to fix the issue is to disable typogrify.
The text was updated successfully, but these errors were encountered: