Closed OrangeChannel closed 4 years ago
You could also format the footnote I added regarding limited 8-bit range in artifacts.md
Playing around with CSS right now, we have the option of using the current font on the page instead of the TeX font.
tex:
website serif: website sans:
Let me know what you think @FichteFoll .
Using the page's font seems nice as it will be less of a context break than a separate paragraph already is. And using sans-serif on a website should always be preferred (unless the user dislikes that for some reason).
How does this work with katex? Does it generate svg?
So, I chose to go with the website font theming for generic math font for KaTeX stuff. It changes to serif if you use the dropdown selector at the top. The block code/TeX also share the same theming now, except for a slightly larger non-mono font.
How does this work with katex? Does it generate svg?
No, in fact the benefit of KaTeX over other *tex libraries is that it pre-renders them as HTML at build-time, leaving no shape/svg generation on the user side.
In the case of changing font-styles, that’s all it’s actually doing. The dropdown is just a css change, no html/svg differences
Thanks for taking the time to work on this. You're the only person who has touched our CSS so far, so I'll trust your judgement when you say it's easier to edit like this.
e1ea810d3b8b153accd46a6f1e927a8bad3e360a has some weird stuff so I'll explain it here. On GitHub, it doesn't change the
$$
within back-ticks to the templates, but gitbook always does. That explains the weirdness of me explaining the templates, but there not being any templates in the actual markdown. There's no actual way around this, as you can't escape characters within back-ticks.