| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
The AFM one is still preferable when passed a PFB because of the extra
checking it does.
|
|
|
|
|
|
|
| |
formats
Latest updates to the loaders seem to have obsoleted a number of our
precautions. Neat.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Add a message that includes the information relevant for
troubleshooting.
Due to the spammy nature of the message printed by Fontspec this is not
exactly useful with Latex so disabled by default for now.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The current PFB loader, although it is indeed completely independent of
the FF libraries, is not yet feature complete. Only the loading of
vectors is supported which suffices for font rendering given the AFM
information.
According to Hans, we have decent chance of it growing into a
full-fledged reader for 1.0.
|
|
|
|
|
|
|
| |
Thanks to @dohyunkim for reminding me to be thorough!
At least in our own files. A patch has been sent upstream to apply the
same change to the generic loader.
|
|
|
|
|
|
|
|
| |
The Lua fontloader doesn’t support these formats and they’re very low
priority. There is no “shortcut” like with the FF loader anymore which
would parse such files into the same data structures as {O,T}TF. Support
for postscript formats may come back at some point in the future if
there is demand.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
| |
We have the VCS info in the status file; these things are just silly.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
... changing the meaning of the file’s designation instead of adding yet
another file.
All the callback manipulation is now contained inside that module which
will inject most of its functionality only when its main ``.install()``
method is called.
|
|
|
|
|
|
|
|
|
| |
This defines a loader for the recognized OFM format. Somehow more recent
versions of Luaotfload (TL 2014) did not provide one, causing to OFM
fonts to fail loading whilst not being an issue without Luaotfload
loaded.
Addresses https://github.com/lualatex/luaotfload/issues/273
|
|
|