Prepare for {xe,lua}tex support in usetex. #29817
Merged
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.
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