| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
|
| |
Highly experimental at this point. The font request parser has been
extended to handle combinations of already defined fonts. Nothing else
has been implemented yet, so the request handler will simply error out
with a message.
|
| |
|
|
|
|
|
| |
Address issue #322
The annotation says it all; reportedly this is fine with TL 2016,
though.
|
| |
|
|
|
|
|
|
| |
This primarily affects the “anon” lookup. However, since we cannot any
longer determine the lookup success by crude means, the resolver
signature had to be modified to indicate success or failure via the
return value. This does no longer match the resolver implementation of
Context but the interface has become much cleaner.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Address issue #318
This reverts the changes made to font-otn.lua with commit adc43c3c24..
Certain features related to directionality are not handled correctly
with the most recent fontloader. As a temporary measure, revert the
handling code in font-otn.lua and restore the values it references.
While this appears to suppress the issue, we’ll switch back to the
upstream code once we have an actual solution.
|
| | |
|
| |
|
|
| |
See issue https://github.com/lualatex/luaotfload/issues/303
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Closing #309
Many thanks for @simifilm for the report!
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Pretty hackish and probably not supported forever, but this is required
on account of the changes to the loader since TL 2014.
|
| | |
|
| | |
|
| |
|
|
| |
Fixes the crash but apparently not the feature.
|
| |
|
|
|
|
|
|
| |
This addresses one error reported by u/priyadarshan:
https://github.com/lualatex/luaotfload/issues/310
Some chained node field access got garbled during the update to nuts.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Not required since we now package the loader ourselves. Good riddance.
|
| |
|
|
|
| |
We still had some 2014 values lingering around dark corners. In theory
this is all meaningless wrt. the Git repo.
|
| | |
|
| |
|
|
|
|
| |
This extends commit 78a1273715.. to the tool. Also fixes the wrong path
being issued to the formatter. Luckily, this is not a functional defect
since the path is used for display purposes only.
|
| | |
|
| | |
|
| |
|
|
|
| |
This kludge dumps the input arguments on one line each -- fix this by
defining a dumb imitation of our real logger that is installed later on.
|
| | |
|
| |
|
|
|
|
| |
This function needn’t be as general for this kind of callback. The new
implementation is simpler but also complains about irregularities like
multiple registered functions.
|
| |
|
|
|
| |
Doesn’t seem like anyone is using these since this would’ve exploded
immediately …
|
| |
|
|
| |
As of ltluatex, provides_module() has no return value any longer.
|
| |
|
|
|
| |
These were rendered unusable due to the suspended initialization.
Creating the directives mapping on the fly is just as good.
|
| |
|
|
|
|
|
|
|
| |
Some upstream API change (possibly in file.join()) caused that function
to emit relative paths.
file.join("/foo", "bar") --> good
file.join("/foo", "" ) --> good
file.join("/foo" ) --> wtf‽
|
| |
|
|
|
|
| |
With tex.scantoks provided by luatex v0.85, now we can
support color transparency in harmony with beamer/pgf/tikz.
No hacking needed at tex macro level, all done in lua code.
|
| |
|
|
|
| |
* default: our package (without lualibs)
* reference: the package from upstream
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Fix https://github.com/lualatex/luaotfload/issues/297
Interword glue hasn’t been considered yet. This again adapts the
relevant logic from Context to our letterspacing method. The code is
deliberately simplistic and will most likely not address all
constellations of a glue preceding a character.
|
| |
|
|
|
|
|
| |
The Luatexbase API was consolidated. Since the priority_in_callback
functionality wasn’t used for anything but determining whether we
need to convert to an hlist first, there’s not really any gain in
keeping it around in the generic form.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This seems to help with the examples from #165 that rely on setting
``$OPENTYPEFONTS`` via the environment.
Referencing a non-existing value caused a branch to always pick Unix
path separators. The affair was pretty insidious since the paths we
received from kpse were sane so the behavior was only triggered with
manual overrides.
|