{{ message }}
Pass explicit font paths to fontspec in backend_pgf. - #10339
Merged
Merged
Conversation
jklymak
approved these changes
Jan 29, 2018
jklymak
left a comment
jklymak
left a comment
Member
There was a problem hiding this comment.
This seems fine to me, and glad it fixes the pdf issue...
anntzer
force-pushed
the
pgf-fontspec
branch
from
February 26, 2018 20:13
9b8d6f1 to
a0313ec
Compare
anntzer
force-pushed
the
pgf-fontspec
branch
2 times, most recently
from
May 3, 2018 02:50
4dc3ed1 to
b002924
Compare
timhoffm
reviewed
May 6, 2018
| # backslashes. 2) The dirname needs to include a separator. | ||
| dirname = Path(fm.findfont(family)).parent.as_posix() + "/" | ||
| latex_fontspec.append( | ||
| r"\%s{%s}[Path=%s]" % (command, basename, dirname)) |
Member
There was a problem hiding this comment.
basename seems undefined. Apparently an untested code path 😦
| """Build fontspec preamble from rc.""" | ||
| latex_fontspec = [] | ||
| texcommand = get_texcommand() | ||
| texcommand = rcParams["pgf.texsystem"] |
Member
There was a problem hiding this comment.
Do we explicitly not want the check and fallback mechanism to xelatex, which was implemented in get_texcommand?
Contributor
Author
There was a problem hiding this comment.
That does already get checked during standard rcparam validation.
timhoffm
approved these changes
May 6, 2018
timhoffm
left a comment
timhoffm
left a comment
Member
There was a problem hiding this comment.
Conditional on CI.
Bonus points if you want to add a test for the pgf.rcfonts code path.
Contributor
Author
6 tasks
4 tasks
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
4 participants
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.
PR Summary
xref #10307. @laborleben Can you check whether this works for you? Seems better than continuously posting patches :)
Basically
PR Checklist