| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Since TFM fonts now take the same path as OTF and suchlike, not passing
on the spec literally may actually be harmful.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
formats
Latest updates to the loaders seem to have obsoleted a number of our
precautions. Neat.
|
| |
|
|
|
| |
Even though it works fine as it was, the loader actually expects “false”
as the value to indicate that no subfont was requested.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Also set a dummy ``pdf`` table that is referenced in the file. Whether
we actually need font-tfm in luaotfload-tool should be reevaluated at
some point before 2.8.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
Reported by @dohyunkim: https://github.com/lualatex/luaotfload/pull/364#issuecomment-226059150
Under certain circumstances, update_names() was invoked with an empty
table instead of a correctly initialized one, breaking the assumptions
of the db populating code.
This commit also guards more strongly against this kind of oversight and
tidies up the db constructor.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Some of the more absurd aspects of fonts ;) This will fork inkscape for
the actual SVG processing.
|
| | |
|
| |
|
|
|
|
|
| |
The new addfeature() as of 499160de78a1 accesses utf8.len() which wasn’t
imported at this point. Another import, utf8.char(), became irrelevant.
Spotted by @doyunkim
|
| |
|
|
|
|
|
|
|
| |
Fix issue #344
The paths changed a while ago making a change necessary. We can’t just
replace the path because older versions of the tree would fail,
rendering bisection unusable. We compensate by testing the candidate
directories beforehand.
|
| |
|
|
|
|
| |
This corresponds to commit a274872832cd on the mirror repo. The changes
since then were numerous but seem to introduce a couple new files we
didn’t ask for =) Later.
|
| |
|
|
|
|
|
|
|
| |
Addresses #359 and #325
To avoid duplicate entries, paths have to be resolved before collecting
them. This necessitates loop detection of some sort, currently
implemented naively as a flat table containing the directories already
traversed.
|
| | |
|
| |
|
|
|
|
|
|
| |
This was introduced with commit 67ad1263d032 during a code removal
frenzy.
Many thanks to @grizzilus for pointing that one out:
https://github.com/phi-gamma/luaotfload/commit/67ad1263d0328fc74928a9a1d06ea9aa0ee9a116#commitcomment-17726875
|
| |
|
|
|
|
|
|
|
| |
Fix #358
The typographic ascender value from the metrics (Windows metrics) table
comes prescaled by the fontloader but we scaled it nevertheless. This is
not true, however, for the value in the metrics table. Fix the access
method to treat the values differently.
|
| |
|
|
|
|
|
|
|
| |
Address issue #356
The DejaVu Family needs stricter handling of fallback choices so we take
the font’s avertised width into consideration. This used to be easier
with the old loader since it had some decent heuristics in place for the
more or less reliable “fontstyle_name”.
|
| |
|
|
|
|
|
|
| |
Remove all the FF stuff and the config option. The transition is
complete, no need to keep these things around any longer.
Since we won’t be going back to the FF loader we might as well dispose
of the junk identifiers and the translation layer as well.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
The crash happens with these broken files MS used to ship:
beef66370e7124eb683514ad9ad07576 palabi.ttf
975972a205fd91a532d1b7433281af70 palab.ttf
be4590eba976dace111b6686f6dade52 palai.ttf
96261bb90c9babbf8042ce7f43200d65 pala.ttf
on account of a broken rule in the “s_s_l” lookup. The change removes
the entire lookup in this case since otherwise the rest of the font
behaves *very* strange.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Add a message that includes the information relevant for
troubleshooting.
Due to the spammy nature of the message printed by Fontspec this is not
exactly useful with Latex so disabled by default for now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
The assumption that the AFM/PFB pair will reside in the same directory
together is wrong for TeX Live. Hence the new lookup against kpse.
|
| | |
|
| |
|
|
|
|
| |
Fixes #349 and #357.
Also the new AFM code is due, let’s see what else we need to use it.
|
| |
|
|
|
| |
This info is indeed valuable on top of the commit hash, thanks to @jfbu
who complained about its absence.
|
| |
|
|
|
|
|
| |
With commit 8c0dd0ebbedd kern accesses were fixed but the results never
tested for the lookup, which caused the default which is set up before
to be nil’ed. Fix this by reusing the value we initialized the kern
factor to.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Defining a combination did not override the default file: lookup so
every font defined that way will at font embedding time trigger a reload
of the index on account of a missing file. Setting the ``combo:`` lookup
will prevent the issue.
|
