summaryrefslogtreecommitdiff
path: root/src
AgeCommit message (Collapse)Author
2016-04-21Revert "[db,conf] drop support for PS fonts"Philipp Gesang
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.
2016-04-21[fontloader] sync with Context as of 2016-04-21Philipp Gesang
Hans fixed a couple issues due to our reports. Also, brand new Lua based PFB loader.
2016-04-21[*] bump versionv2.7Philipp Gesang
2016-04-20[*] remove references to obsolete formats (PF{A,B}, DFONT, FEA)Philipp Gesang
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.
2016-04-20[db,conf] drop support for PS fontsPhilipp Gesang
The “AFM” code stays since PFB accompanied by an AFM file is still supported by the fontloader.
2016-04-20[loaders] remove support for PF{A,B}Philipp Gesang
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.
2016-04-19[aux] make fontname substitution more robustPhilipp Gesang
Another take on https://github.com/lualatex/luaotfload/issues/334 The parsing issues we aim to prevent occur with spaces because Luatex treats them as argument separators. Hence apply quoting only if necessary. Also use the appropriate format string as a defense against garbage inputs.
2016-04-19[main] fix oversight in comment (thanks, Èlie)Philipp Gesang
2016-04-19[aux] fix crash with tfm fontsPhilipp Gesang
Fixes https://github.com/lualatex/luaotfload/issues/334 Old-style font definitions only need a font name, so the extra quotes aren’t necessary to feed the \fontname string back into \font.
2016-04-19[features] cull legacy feature handlerPhilipp Gesang
2016-04-19[features] do not attempt to add features on incomplete fontsPhilipp Gesang
2016-04-19[*] shred 2014 fontloaderPhilipp Gesang
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.
2016-04-19[fontloader] sync with Context as of 2016-04-19Philipp Gesang
2016-04-18[db,fontloader] fix subfont table handling (by Dohyun Kim)Philipp Gesang
TTC subfonts must be considered if there is at least one subfont. Discovered and fixed by @dohyunkim; the fix for ``font-otr.lua`` goes upstream.
2016-04-18[tool,doc] inter fontloader warnings optionPhilipp Gesang
The option has become redundant with the new loader so we might as well get rid of it.
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 :/