| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
The config option must go since the FF based code was removed already
some time ago.
|
| |
|
|
|
|
|
|
| |
This was introduced with commit 67ad1263d032 during a code removal
frenzy.
Many thanks to @grizzilus for pointing that one out:
https://github.com/phi-gamma/luaotfload/commit/67ad1263d0328fc74928a9a1d06ea9aa0ee9a116#commitcomment-17726875
|
| |
|
|
|
|
|
|
| |
Remove all the FF stuff and the config option. The transition is
complete, no need to keep these things around any longer.
Since we won’t be going back to the FF loader we might as well dispose
of the junk identifiers and the translation layer as well.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows to domesticate packages that quite disrespectfully only use
“anon:” lookups. Example from the test repo:
\documentclass{scrartcl}
\usepackage{fontspec}
\directlua{
config.luaotfload = config.actions.apply
(config.luaotfload, { run = { anon_sequence = { "my" } } })
}
\directlua{
luatexbase.add_to_callback(
"luaotfload.resolve_font",
function (spec) spec.name = "comic.ttf" end,
"user.openbsd_style")
}
\setmainfont{Adobe Premier Deluxe Overpriced}
\begin{document}
There is no escape.
\end{document}
|
| |
|
|
|
|
|
|
| |
The arguments to “--find” on the command line avoided calling the real
index API functions and used crude approximations instead. In order to
make “--find” obey the new “anon-sequence” configuration item, it needs
to access the normal resolvers instead. This requires certain
adaptations to allow for a fallback on the “file:” lookup.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Implements #263
The resolvers have already been decoupled a while ago but the goal of
allowing the sequence to be reordered at will was still outstanding.
Add a config option “anon-sequence” that is parsed as a comma-delimited
list of sequence components.
|
| |
|
|
|
|
|
|
| |
This reverts commit c4c250414a83cc8c4ae99d286ed69a3763510609.
Partially, anyways: All mentions of the PFA format were stripped.
Since the new loader adds back in support for PFB-flavored PS fonts
without AFM we should support it from Luaotfload as well.
|
| |
|
|
|
|
|
| |
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 “AFM” code stays since PFB accompanied by an AFM file is still
supported by the fontloader.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Only font indexing is affected by “use-fontforge”. The fontloader itself
will always use the new code.
|
| | |
|
| |
|
|
|
|
| |
There are some non-negligible differences in the reader output,
especially concerning font names. Until this is sorted out we need a
fast way to switch back to the old code for reference.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
The (fontloader, path) return value cannot pass the post-config
validation because the value of ``run.fontloader`` is of type string.
Since the path is always checked during configuration we can just
forward it as-is and attempt a path load later on.
|
| | |
|
| |
|
|
|
|
| |
Makes the config test for paths specified as “context:/path/to/texmf”
and return a ("context", path) pair that is intended for use as the base
path of the fontloader files.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
For now, this pertains only to the modules we ship in Luaotfload. For
loading from Context we still need a step to distinguish between the
namespaced versions of the files, the pure ones in texmf/…/base, and the
Luatex-Fonts ones.
But yeah, setting
[run]
fontloader = unpackaged
in the luaotfloadrc now works splendidly.
|
| |
|
|
| |
We have the VCS info in the status file; these things are just silly.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
This adds an entry ``loader`` on the ``notes`` hash in the status table
by means of which the fontloader can be specified. The status file is
read when building the configuration table, and if it is present the
entry in the ``loader`` table will be used as the default fontloader.
Otherwise, Luaotfload falls back on the reference loader.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Addresses this behavior: http://tex.stackexchange.com/q/238539/14066
This is a breaking change but it hardly matters since font-based
colorization is deprecated and the old behavior can be restored by means
of a configuration setting.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
What the hell was that for?
|
| |
|
|
|
| |
List items are now stripped of leading and trailing spaces before
building the formats list.
|
| |
|
|
|
|
| |
Adds a validation function that checks whether the value is indeed a
list of comma-separated identifiers. Also, duplicate and invalid entries
are dropped from the result.
|
| | |
|
| | |
|
| | |
|
| | |
|
