Skip to content
This repository has been archived by the owner on Apr 6, 2023. It is now read-only.

Conflicts with typogrify #30

Closed
jboynyc opened this issue Aug 21, 2015 · 4 comments
Closed

Conflicts with typogrify #30

jboynyc opened this issue Aug 21, 2015 · 4 comments

Comments

@jboynyc
Copy link

jboynyc commented Aug 21, 2015

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.

@danielfrg
Copy link
Owner

Kinda tricky to fix for me since i don't use that plugin.

You can probably make it work with some extra CSS like I do for my theme: https://github.com/danielfrg/middle-theme/blob/master/templates/ipynb.css

@jboynyc
Copy link
Author

jboynyc commented Aug 21, 2015

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.

@danielfrg
Copy link
Owner

Not a problem at all. I like to record this stuff in issues.

@dan-tee
Copy link

dan-tee commented Feb 19, 2016

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.

Disabling Typogrify fixed it.

@jboynyc jboynyc closed this as completed Feb 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants