| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
| |
Credits to Taco for the talk at Kalenberg that inspired the feature.
Extending the parser is required so we can have proper name for the
feature.
Happy Luatex 1.0.0
|
| | |
|
| |
|
|
|
| |
Fontloader crashes during loading. Hans is notified, let’s wait for him
to fix it properly.
|
| |
|
|
| |
This incorporates our patch for issue #377.
|
| |
|
|
| |
Patch has been upstreamed for a while but no response yet.
|
| |
|
|
|
|
| |
The loader makes some assumptions about available lookup functions early
on. Since fonts-syn.lua only installed dummies for most of these, we
might as well do that too.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
addfeature() and the likes -- with less extensive logging -- is now
provided directly by means of font-otc.lua so we don’t need to keep
these parts around any longer. The loader installs anum features
identical to ours and a slightly different “tlig” one which we override.
Clean up locals and misleading comments while we’re at it.
|
| | |
|
| |
|
|
|
| |
CAVEAT LECTOR This adds font-otc.lua part of which has already been
included in our feature handler.
|
| |
|
|
| |
No need for patching font-tfm.lua any longer.
|
| |
|
|
| |
Hans appears to have heard our pleas =)
|
| |
|
|
|
|
|
|
|
|
| |
This makes our own features work with otf.addfeature().
However, for TFM it’s still not functional out of the box since the
enhancer is installed at a time when it has not been defined yet. An
answer from Hans is pending. In the meantime, we put a crude hack into
our font-tfm.lua to allow injecting the enhancer retroactively on
Luaotfload init.
|
| |
|
|
|
| |
The AFM one is still preferable when passed a PFB because of the extra
checking it does.
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
