Open
Conversation
Owner
|
This reduces the load time of But it doesn't solve the wideness and header overflow issue mentioned in #98, because it changes from the status quo: |
Author
|
overflow behavior is a separate topic to look at |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



A sample PR for employing the same font in the HTML as is used in the PDF. There is a bit of concern though: Serif fonts and low-resolution (96dpi) displays don't historically mix well, which is why you don't see them all that often on webpages (e.g. newspaper sites). It's ok when you look at it with a mobile phone (just tested at 400dpi) or set browser page magnification to 150% on a low-dpi screen, so 🤷 goodenoughforme.
Fixes #98 .
Fixes #103 (no longer using font fragments with
unicode-range).Incidentally, this also fixes contacting Google services (GDPR and all that).
Haven't looked at the MathJAX parts at all(!), I just made sure the new CSS renders ok with https://eel.is/c++draft/format.string.escaped#example-1 .