-
-
Notifications
You must be signed in to change notification settings - Fork 313
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
Add a theme that use LaTeX fonts for everything #3147
Conversation
I like the idea, maybe it's a good opportunity to show in the docs that you can merge themes. So we could call the theme |
In your docs examples, better use |
I simply don't understand the doc build failure for (also building the doc locally for either this branch or master error for me -- a different error, maybe because I'm on Windows. That's a separate issue, but it doesn't help) |
Hm I didn't have these macro issues in the docs in a while, but last time it was some Franklin weirdness that I couldn't really understand. |
Ok, I'm giving up... No idea why the |
I don't really know what to do here... I really don't want to start debugging franklin, and I really don't want this PR to rot, just because of a Franklin bug... |
Yeah this is really strange.. @tlienart just FYI this is one of those cases where we assume Franklin is doing something which messes with evaluation. But we can't be sure 🤷♂️ |
It would be a bit unfortunate to not have a LaTeX string as it shows the theming is consistent. But that's a minor thing, I'll change it before we all succumb to madness. |
I'll try to look into this. Note that it's a somewhat indirect Franklin bug; if you just execute a direct cell block with a LaTeXString in it, it will work fine (namely this code works fine:
however in the docs you do (much) more than this with the |
I can build the whole page fine, apart from an error halfway which seems to be on your side with a non-existent figure everything else seems fine: the above seems to suggest that it's may not just be a simple issue with Franklin. Could one of you try to build the docs locally and report what you see when you do |
Ok I won't be able to do much more digging just now but this repo: https://github.com/tlienart/ftest-makie basically is just your Failures at deployment stages are harder to fix because we need to figure out exactly what's happening on a github instance and why things aren't the same as locally... It might be helpful if you can confirm that you can indeed build that repo above locally without issue and that you see the figures as expected (e.g. if one of you is on Linux for instance as I'm on a mac). Not sure what could cause this; does Makie expect specific dependencies around LaTeX stuff that might not be available on a GitHub machine for instance? |
Ok I think I found a workaround, can you adapt your utils taking L28 from https://github.com/tlienart/ftest-makie/blob/main/utils.jl (I think if that line was just That seems to be the problem, the code in examplefigure is not run in an environment that has the right https://github.com/tlienart/ftest-makie/actions/runs/5968808262/job/16193413162#step:4:1 |
Although, looking at the file in this PR again, the example added is not the first on the page, and there are even other L strings on that page before it. Including in the first cell... |
I'm not sure what your last comment refers to but, your previous comment about |
I think I tried that in #3180, but maybe I did something wrong... |
Description
Most issues are asking to have the sans serif Makie font in LaTeX formulas, this PR only fix the font discrepency issue by putting the LaTeX font everywhere with the new theme.
A prototype fix for the problem in the other direction should come relatively soon.
With the theme I get that kind of results
Type of change
Delete options that do not apply:
Checklist