| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
With the new loader, the ``units_per_em`` field resides under the
toplevel TFM structure with the key ``units``. For AFM fonts, it is not
fount under the metadata table too, which we are currently querying.
Thus we prefer the main value, falling back on metadata only in case it
is missing.
At this occasion, tidy up our unit lookup helper and use that wherever
we need access to the values ourselves.
|
|
|
|
|
|
|
|
| |
Fix #341
Hironori Kitagawa pointed out that the patch for the other math
parameters doesn’t work. Turns out Hans relocated the “mathconstants”
table …
|
| |
|
|
|
|
|
| |
Provide fallbacks in case no ‘X’ character is available for capheight
measurement.
|
|
|
|
|
|
|
|
| |
Addresses #341
This cleans up the font patching code we inherited from Fontspec. In
addition to treating the bitrot with an extra dose of fungicide, we also
make the process in which the final values are chosen more transparent.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Fix #338
Due to the new loader, certain tables were relocated inside the fontdata
structure. This would cause a crash with certain kinds of fonts, most
notably those for which TeX metrics exist.
Many thanks to @aminophen and @u-fischer for their help in tracking this
down.
|
|
|
|
|
|
|
|
|
| |
Another take on https://github.com/lualatex/luaotfload/issues/334
The parsing issues we aim to prevent occur with spaces because Luatex
treats them as argument separators. Hence apply quoting only if
necessary. Also use the appropriate format string as a defense against
garbage inputs.
|
|
|
|
|
|
|
| |
Fixes https://github.com/lualatex/luaotfload/issues/334
Old-style font definitions only need a font name, so the extra quotes
aren’t necessary to feed the \fontname string back into \font.
|
|
|
|
|
|
|
|
|
|
| |
Obviously, since Fontforge has been ditched, we need to adapt to the
slightly different data structures created by the Lua reader. For the
time being, we revise the code so it will not crash instantly due to the
lack of a missing ``pfminfo`` table.
Hans has been notified of our use of the ``capheight`` data and may
add that value grudgingly again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The fontloader requires parts of the ``characters`` table to be present
at load time. This turns out to interfere with our custom of installing
the lazy loader for the table components only after the fontloader has
been injected. Since inserting the code at the appropriate place in the
loading chain would be tedious and unmaintainable due to the various
load options, we just preinstall the metatable onto an empty table prior
to loading the loader.
Some precautions had to be taken regarding the ``classifiers`` subhash
of the table that needs to be relocated from the data we received via
mkcharacters.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Doesn’t seem like anyone is using these since this would’ve exploded
immediately …
|
|
|
|
| |
We have the VCS info in the status file; these things are just silly.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/lualatex/luaotfload/issues/253
Sort of.
In order to not interfere with the other callbacks which expect a sane
environment this hack got added by means of another callback that is
called whenever a defined font lacks essential subtables. This means
that the user must consider cases like numbers and partially defined
fonts. It’s best to keep both cases separate so those who aren’t
concerned with workarounds for weird fonts can stick with the clean
interface.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This adresses an issue with entries in the font table that lack the
common font structure (manually parsed fonts??). Subtable lookups
are now guarded with nil-checks.
Reported by Herbert Voss
Signed-off-by: Philipp Gesang <phg42.2a@gmail.com>
|
| |
|
| |
|
|
|