summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2016-04-18[passim] update maintainer contactPhilipp Gesang
2016-04-18[fontloader] sync with Context as of 2016-04-18Philipp Gesang
2016-04-18[db] fix misleading error messagePhilipp Gesang
No such warnings with the new loader. Instead we need to test for the ``fontname`` / ``fullname`` fields. Thanks to @dohyunkim for reporting.
2016-04-17[conf] move “use-fontforge” option into section “[db]”Philipp Gesang
Only font indexing is affected by “use-fontforge”. The fontloader itself will always use the new code.
2016-04-17[features] account for subfont indexing changesPhilipp Gesang
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.
2016-04-17[features] adjust feature processor to new data structuresPhilipp Gesang
2016-04-17[db] undo commented out texmf tree processingPhilipp Gesang
D’oh! Too much debugging =)
2016-04-17[fontloader] quick fix by Hans for issue #326Philipp Gesang
Addresses #326 This is a hot-fix with non-official code. The actual fix will come downstream later from Context as usual.
2016-04-17[features] fix buggy state checkPhilipp Gesang
2016-04-17[fontloader] sync with Context as of 2016-04-17Philipp Gesang
2016-04-16[tool] adapt fullinfo to new loaderPhilipp Gesang
Note that this will explode on the current loader code due to a typo in font-otr.lua. Patch submitted upstream, please be patient.
2016-04-16[fontloader] sync with Context as of 2016-04-16Philipp Gesang
2016-04-16[features] rely on config to detect runtime modePhilipp Gesang
2016-04-16[tool] annihilate references to FFPhilipp Gesang
The tables emitted by the new font reader functions do not correspond to their Fontforge counterparts. Thus, some of the display routines had to be rewritten, in some cases like the names table this resulted in the removal of a good deal of obsolete code.
2016-04-15[fontloader] sync with Context as of 2016-04-15Philipp Gesang
2016-04-15[db] fix extraction of name info important for family clusteringPhilipp Gesang
… or perhaps more accurately, “megafamily”. For the time being we prefer the “windows” versions of the fonts due to the higher quality of the “typographic family” and “subfamily” fields. Another advantage of the new loader over FF is that we’re even given that choice.
2016-04-13[db] pull raw name information with getinfo()Philipp Gesang
This facility was added by Hans to accomodate our peculiar requirements: There should be no fallback from prefmodifiers to familyname since that removes valuable information about larger font sets like the Adobe ones.
2016-04-13[init] avoid infinite recursion in characters.__indexPhilipp Gesang
Fallout of the new character table loading routine.
2016-04-13[db] add some stats regarding the new loaderPhilipp Gesang
2016-04-12[db] adjust names extraction to Lua loaderPhilipp Gesang
2016-04-11[fontloader] sync with Context as of 2016-04-11Philipp Gesang
After some discussion, Hans came up with these extensions to the new reader. We get access to more items from the hideous “name” table. On the one hand, this means more brokenness to endure and a less sane matter to work with. But since our tracker was devoid of font-matching related bug reports for some time, it’s the right move nonetheless. In addition to the name table junk, the font loader now also includes the “version” field in the output of “getinfo()”. It’s meaningless per se, but it sure helps to distinguish historical bugs from the ones that matter. **UNTESTED**
2016-04-10[db] in ff mode, collect font object after accessPhilipp Gesang
2016-04-10[conf] rework logic ff/lua fontloader choicePhilipp Gesang
2016-04-10[db] do not rely on __gc for font object lifetimesPhilipp Gesang
The penalty for having font object closed automatically is huge: It takes around nine seconds more to rebuild the font database: 58 s with __gc, 49 s by closing manually. Even if it’s not the default, we reintroduce the code for closing fonts manually to avoid that situation.
2016-04-09[conf,db] allow switching back to fontforgePhilipp Gesang
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.
2016-04-09[tool,db] kill off fontforgePhilipp Gesang
This has been coming for some time: Upstream now provides full Opentype reader capabilities. This allows Luatex to drop those horrible fontforge libraries. Since the API is pretty similar, for Luaotfload it means little change and a decent speed gain. Though we still need to investigate whether the result is equivalent or at least acceptable.
2016-04-09[aux] fix crash in patching code that sets \fontdimen8Philipp Gesang
Obviously, since Fontforge has been ditched, we need to adapt to the slightly different data structures created by the Lua reader. For the time being, we revise the code so it will not crash instantly due to the lack of a missing ``pfminfo`` table. Hans has been notified of our use of the ``capheight`` data and may add that value grudgingly again.
2016-04-09[aux,init] move lazy char-def loading code into earlier stage of initializationPhilipp Gesang
The fontloader requires parts of the ``characters`` table to be present at load time. This turns out to interfere with our custom of installing the lazy loader for the table components only after the fontloader has been injected. Since inserting the code at the appropriate place in the loading chain would be tedious and unmaintainable due to the various load options, we just preinstall the metatable onto an empty table prior to loading the loader. Some precautions had to be taken regarding the ``classifiers`` subhash of the table that needs to be relocated from the data we received via mkcharacters.
2016-04-08[init] force preloading of the character tablePhilipp Gesang
2016-04-08[db] ditch our gzip wrappersPhilipp Gesang
We again depend on the full Lualibs set for some time so our wrappers are irrelevant as we can just use the similar once from there.
2016-04-08[init] addremove fontloader filesPhilipp Gesang
2016-04-07[*] update dates, versionPhilipp Gesang
2016-04-07[fontloader] sync Context as of 2016-04-07Philipp Gesang
2016-04-06[fontloader] sync fontloader package with Context revision 274c32699..Philipp Gesang
2016-04-05[tool] status library API falloutPhilipp Gesang
With revision 5624, the status library was overhauled. Among others we lose the ``luatex_svn`` field which was rather useful for debugging :/
2016-02-19*: bump version and datePhilipp Gesang
Now that we’re heading towards TL 2016, this seems necessary.
2016-02-19[features,parsers] implement font fallbacksPhilipp Gesang
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.
2016-02-19[parsers] rework combo syntaxPhilipp Gesang
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)"
2016-02-19[parsers] allow whitespace around combo elementsPhilipp Gesang
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"
2016-02-19[features,loaders] fix lookup conflicts via introduction of “evl” lookupPhilipp Gesang
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.
2016-02-18[features,loaders] allow for direct injection of tfmdata when defining fontsPhilipp Gesang
2016-02-16[features] handle combination definitionsPhilipp Gesang
2016-02-15[parsers,features] parse combo requestsPhilipp Gesang
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.
2016-02-12[fontloader] patch font-otn.lua to skip unusable contextpos featuresPhilipp Gesang
Address issue #322 The annotation says it all; reportedly this is fine with TL 2016, though.
2016-01-27[resolvers] allow arbitrary sequence lookupsPhilipp Gesang
This primarily affects the “anon” lookup. However, since we cannot any longer determine the lookup success by crude means, the resolver signature had to be modified to indicate success or failure via the return value. This does no longer match the resolver implementation of Context but the interface has become much cleaner.
2016-01-22[init] fix Context module sequencev2.6-fix-5showPhilipp Gesang
2016-01-22[fontloader] revert features handler temporarilyPhilipp Gesang
Address issue #318 This reverts the changes made to font-otn.lua with commit adc43c3c24.. Certain features related to directionality are not handled correctly with the most recent fontloader. As a temporary measure, revert the handling code in font-otn.lua and restore the values it references. While this appears to suppress the issue, we’ll switch back to the upstream code once we have an actual solution.
2016-01-21[init] always log final fontloader choicePhilipp Gesang
2016-01-11[fontloader] re-patch font-otn.lua to avoid crashPhilipp Gesang
See issue https://github.com/lualatex/luaotfload/issues/303
2016-01-11[features] import feature loading codePhilipp Gesang