| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
| |
Use arrows to emphasise what’s mapped. Allow whitespace to visually
separate items. Also allow optional grouping with parentheses.
Now it’s possible to define a combination as follows:
\font \f = "combo: 1 -> 42;
2 -> 1337, U+0042-U+0084;
3 -> (55, 0x54 * 0x45 * 0x58)"
|
|
|
|
|
|
|
|
|
|
| |
This gives more leeway to the notation, allowing font definitions to
become more readable:
\font \f = "combo: 1 / \fontid\one,
2 / \fontid\two / 0x41-0x5a,
3 / \fontid\three / 0x42,
4 / \fontid\three / 0x54 * 69 * U+58"
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
We have the VCS info in the status file; these things are just silly.
|
| |
|
|
|
|
| |
more verbose messages
|
| |
|
|
|
|
|
|
|
|
| |
Addresses issue https://github.com/lualatex/luaotfload/issues/275
There indeed was a check missing for included files. Since a
corresponding check for included directories was in effect it probably
masked the potential stack blowthrough.
|
|
|
|
| |
being read
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|