| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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 is an experiment: The character kerning callback has been converted
in its entirety to utilize the not-so-new direct node API. Since the
translation was mechanical only to a certain extent, this may have
introduced errors. On the other hand, the revised code resembles its
distant ancestor in Context’s ``typo-krn.lua`` much more closely again,
which may come in handy in the future.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For better orientation, the fontloader tree now contains two
subdirectories into which files have been reorganized:
The two files required at runtime for the fontloader and luaotfload-tool
are:
× ``fontloader-basics-gen.lua``
× ``fontloader-fontloader.lua``
They are now kept in the ``src/fontloader/runtime/`` subdirectory.
All other files from upstream are now located in
``src/fontloader/misc``. This includes a number of files that have not
yet been part of Luaotfload. Currently, the *misc* set of files is not
packaged along with Luaotfload. This may change in the future when there
is an option to switch the merged fontloader for its constituent files,
or even for upstream.
|
| |
|
|
|
|
|
| |
This moves the fontloader files into a separate subdirectory to simplify
maintainance.
|
|
|
|
|
|
|
|
| |
The message violated our policy of not suppressing all non-error
messages on the terminal at log level 0. The faulty message was moved to
level 1 for both streams.
addresses https://github.com/lualatex/luaotfload/issues/256
|
|
|
|
|
|
| |
fix https://github.com/lualatex/luaotfload/issues/258
This fix was proposed by /u/saidai-no on Github.
|
|
|
|
| |
Lots of changes, it’s been a while =)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
| |
definers
The definers ``info_patch`` and ``info_generic`` wrap the two existing
font definers in a function that emits verbose information about the
definitions taking place.
|
|
|
|
|
|
| |
This is a partial revert of 3cf26fc.. -- The test must be for features
not specified in the font definition. Also applies in the same manner to
the global defaults.
|
| |
|
|
|
|
|
|
|
| |
Closing https://github.com/lualatex/luaotfload/issues/243
The behavior was introduced with commit d84ce4e.. when non-boolean
default feature values were introduced as part of the configuration.
|
|
|
|
| |
Closes https://github.com/lualatex/luaotfload/issues/237
|
|
|
|
|
| |
The ``db.update-live`` option caused all db updates, even forced ones to
fail due to a missing check for the kind of run.
|
| |
|
|
|
|
|
| |
Now ``luaotfload-tool --dumpconf`` can be used to output the current
configuration to a file.
|
| |
|
|
|
|
|
| |
Gets rid of even more ugliness caused by the recent unification of the
parsers.
|
| |
|
|
|
|
|
|
|
| |
The reference to ``find_files`` didn’t get passed on to recursive calls
which caused an error if multiple directories are searched.
Reported by Norbert Preining.
|
| |
|
|
|
|
| |
Hope I didn’t mess this up again …
|
|
|
|
|
|
|
|
|
| |
Fixes https://github.com/lualatex/luaotfload/issues/233
On non-POSIX systems, the Lua interpeter is compiled with a reduced set
of options accepted by ``os.date()`` [0].
[0] http://www.lua.org/source/5.2/loslib.c.html#LUA_STRFTIMEOPTIONS
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
due to configuration
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This message originates in ``luatex-fonts.lua`` [0]. The advice given on
using the Context libraries directly is counterproductive unless one is
already hacking on the Luaotfload code, in which case it should be
obvious anyways. Cluttering the log file with those lines is
unjustified.
[0] http://git.contextgarden.net/context/context/blob/master/tex/generic/context/luatex/luatex-fonts.lua#L139
|