Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork7.9k
Prepare for {xe,lua}tex support in usetex.#29817
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Merged
Merged
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
38c33e6
tob49c6dc
CompareUh oh!
There was an error while loading.Please reload this page.
DviFont.widths (the widths of each glyph in a font) is only usedby backend_pdf to embed (classic, Type1) TeX fonts; deprecate thatattribute and instead compute it where needed. This change is inpreparation for supporting {xe,lua}tex, where DviFont can also refer toOpenType fonts which would be embedded via a different mechanism intothe pdf file, and which can contain so many glyphs that explicitlylisting the width of each one would be wasteful.
Dvi fixed-point values are in 12.20 format (12 bits before the decimalpoint, 20 bits after -- see e.g. the 20-bit bitshifts scattered in thedviread module), not 20.12. Rename the helper function accordingly.
QuLogic approved these changesMar 27, 2025
See spec in `texdoc tftopl` section 10 and `texdoc dvitype` section 18.
Added a third doc-only commit. |
timhoffm approved these changesMar 27, 2025
b2b76d6
intomatplotlib:main 39 of 41 checks passed
Uh oh!
There was an error while loading.Please reload this page.
5 tasks
Sign up for freeto 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.
Uh oh!
There was an error while loading.Please reload this page.
Minor preparatory PRs for#29807:
Move listing of Type1 glyph widths to backend_pdf:
DviFont.widths (the widths of each glyph in a font) is only used
by backend_pdf to embed (classic, Type1) TeX fonts; deprecate that
attribute and instead compute it where needed. This change is in
preparation for supporting {xe,lua}tex, where DviFont can also refer to
OpenType fonts which would be embedded via a different mechanism into
the pdf file, and which can contain so many glyphs that explicitly
listing the width of each one would be wasteful.
Rename the confusingly named dviread._mul2012:
Dvi fixed-point values are in 12.20 format (12 bits before the decimal
point, 20 bits after -- see e.g. the 20-bit bitshifts scattered in the
dviread module), not 20.12. Rename the helper function accordingly.
Clarify doc for Tfm.design_size.:
See spec in
texdoc tftopl
section 10 andtexdoc dvitype
section 18.PR summary
PR checklist