| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Subfont loading seems to have been broken for a while but no reports …
|
| |
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
| |
No need for patching font-tfm.lua any longer.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
Even though it works fine as it was, the loader actually expects “false”
as the value to indicate that no subfont was requested.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
Due to the origin in other parts of Luatex, some messages in this file
were logged under the “load” facility; corrected. Also, the combo
mechanism still spits debug levels of noise at log level zero; raised to
two.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This one hasn’t been touched for ages. The will be no compatibility
loader this year. For testing, creating a loader on the fly from the Git
repos is sufficient.
|
| |
|
|
|
|
| |
The new Lua based loader consistently numbers subfonts from one, not
zero like the Fontforge one. We correct the value immediately before
passing a handled font request on to the loader.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Building on the combination mechanism, this allows defining fallback
fonts of which all glyphs are pulled that aren’t currently part of the
base font. Example:
\input luaotfload.sty
\font \lm = file:lmroman10-regular.otf:mode=base
\font \cmu = file:cmunrm.otf:mode=base
\font \lmu = "combo: 1->\fontid\lm; 2->\fontid\cmu,fallback"
\lmu Eh bien, mon prince. Gênes et Lueques ne sont plus que des
apanages, des поместья, de la famille Buonaparte.
\bye
This allows setting Latin Modern text that contains Cyrillic letters.
Note that -- as with the other combinations -- only glyphs are
considered, no other properties of the fallback font. So besides the
occasional letter in a different script this functionality is probably
useless.
|
| |
|
|
|
|
|
|
| |
This introduces a forced lookup type “evl” that bypasses the other
methods. The specification is extended with the correct values including
a more meaningful hash string. As a result, the loader no longer
attempts to interpret the specification as a “file:” request but the
backend can still resolve the necessary files.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
We still had some 2014 values lingering around dark corners. In theory
this is all meaningless wrt. the Git repo.
|
| | |
|
| |
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
