-
Notifications
You must be signed in to change notification settings - Fork 23
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
bug: no way to express font fallbacks in SCSS themes? #81
Comments
Sorry, to which themes are you referring? The nbpresent build chain is based on less... Also, instead of attaching notebooks as zips, please consider publishing them as gists and using nbviewer :) This lets us conveniently reference them. Actually, for this purpose, an anonymous gist is ideal, as it is immutable, and links will always work :) |
oh -- ok, I'll do that. Coming up.... |
here you go https://gist.github.com/jason-s/a3c00bcaa362359c7c87ea48f7fe986d It doesn't show the slideshow in nbviewer, however. You have to run them from a Jupyter instance to use the slideshow features. These are themes based on reveal.js "Simple" theme (using the "import from reveal.js" ipython notebook) and tweaked by hand to change the main font-family. |
one of them looks like this:
|
The other one contains
in a vain attempt to figure out how to get font fallbacks to work. |
Ok, that makes more sense. nbpresent doesn't presently handle font fallback chains. Indeed, we're considering how to embed actual fonts, again on the archival output goal. Again, if you are already very comfortable with these kinds of concepts, you may have more success working directly with the reveal.js/RISE approach! |
There appears to be no way to express font fallbacks in the SCSS themes. The normal CSS is
but if you use this in the SCSS it tries to find a font-family of
"Arial, Tahoma"
; I've tried using an array but it fails and gives me the errornbpresent.deps.min.js:55 Uncaught TypeError: n[e].split is not a function
here are notebooks demonstrating this:
fallback-fonts-fail.zip
The text was updated successfully, but these errors were encountered: