Commit message (Collapse) | Author | Age | Files | Lines | ||
---|---|---|---|---|---|---|
... | ||||||
| * | [fontloader] sync with Context as of 2016-04-24 | Philipp Gesang | 2016-04-24 | 4 | -34/+138 | |
| | | ||||||
| * | [aux] make name_of_slot API more robust | Philipp Gesang | 2016-04-24 | 1 | -2/+14 | |
| | | ||||||
| * | [aux] make slot_of_name API more robust | Philipp Gesang | 2016-04-24 | 1 | -15/+22 | |
| | | ||||||
| * | [aux] fix features table access (issue #338) | Philipp Gesang | 2016-04-24 | 1 | -17/+59 | |
| | | | | | | | | | | | | | | | | | | | | | | Fix #338 Due to the new loader, certain tables were relocated inside the fontdata structure. This would cause a crash with certain kinds of fonts, most notably those for which TeX metrics exist. Many thanks to @aminophen and @u-fischer for their help in tracking this down. | |||||
| * | [doc] fix typo in example snippet | Philipp Gesang | 2016-04-23 | 1 | -1/+1 | |
| | | | | | | | | Reported by @u-fisher on Github. | |||||
| * | Revert "[db,conf] drop support for PS fonts" | Philipp Gesang | 2016-04-21 | 2 | -7/+65 | |
| | | | | | | | | | | | | | | | | 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. | |||||
| * | [fontloader] sync with Context as of 2016-04-21 | Philipp Gesang | 2016-04-21 | 9 | -107/+370 | |
| | | | | | | | | | | Hans fixed a couple issues due to our reports. Also, brand new Lua based PFB loader. | |||||
* | | Merge pull request #336 from phi-gamma/master | Philipp Gesang | 2016-04-21 | 10 | -107/+61 | |
|\| | | | | | 2.7 | |||||
| * | [*] bump versionv2.7 | Philipp Gesang | 2016-04-21 | 5 | -9/+9 | |
| | | ||||||
| * | [*] update news | Philipp Gesang | 2016-04-21 | 1 | -2/+2 | |
| | | ||||||
| * | [*] remove references to obsolete formats (PF{A,B}, DFONT, FEA) | Philipp Gesang | 2016-04-20 | 7 | -26/+19 | |
| | | | | | | | | | | | | | | 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. | |||||
| * | [doc] extend request syntax with combinations | Philipp Gesang | 2016-04-20 | 1 | -6/+28 | |
| | | | | | | | | It’s sort of official now ;) | |||||
| * | [db,conf] drop support for PS fonts | Philipp Gesang | 2016-04-20 | 2 | -67/+6 | |
| | | | | | | | | | | The “AFM” code stays since PFB accompanied by an AFM file is still supported by the fontloader. | |||||
* | | Merge pull request #335 from phi-gamma/master | Philipp Gesang | 2016-04-20 | 6 | -191/+96 | |
|\| | | | | | format and feature handling, fixes for 2.7 | |||||
| * | [*] update news | Philipp Gesang | 2016-04-20 | 1 | -1/+2 | |
| | | ||||||
| * | [doc] rip our section about feature files | Philipp Gesang | 2016-04-20 | 1 | -32/+0 | |
| | | | | | | | | | | Unsupported as of now. They were only ever supported by accident and very incompletely, which was misleading. | |||||
| * | [loaders] remove support for PF{A,B} | Philipp Gesang | 2016-04-20 | 1 | -2/+10 | |
| | | | | | | | | | | | | | | | | 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. | |||||
| * | [doc] expand chapter on font combos | Philipp Gesang | 2016-04-20 | 1 | -1/+55 | |
| | | ||||||
| * | [aux] make fontname substitution more robust | Philipp Gesang | 2016-04-19 | 1 | -2/+7 | |
| | | | | | | | | | | | | | | | | | | 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. | |||||
| * | [main] fix oversight in comment (thanks, Èlie) | Philipp Gesang | 2016-04-19 | 1 | -1/+1 | |
| | | ||||||
| * | [aux] fix crash with tfm fonts | Philipp Gesang | 2016-04-19 | 1 | -1/+4 | |
| | | | | | | | | | | | | | | 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. | |||||
| * | [features] cull legacy feature handler | Philipp Gesang | 2016-04-19 | 1 | -145/+1 | |
| | | ||||||
| * | [features] do not attempt to add features on incomplete fonts | Philipp Gesang | 2016-04-19 | 1 | -8/+18 | |
| | | ||||||
* | | Merge pull request #333 from phi-gamma/master | Philipp Gesang | 2016-04-19 | 10 | -13975/+40 | |
|\| | | | | | latest 2.7 progress | |||||
| * | [doc] start chapter on font combos | Philipp Gesang | 2016-04-19 | 1 | -0/+31 | |
| | | ||||||
| * | [*] shred 2014 fontloader | Philipp Gesang | 2016-04-19 | 7 | -13969/+3 | |
| | | | | | | | | | | | | 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. | |||||
| * | [fontloader] sync with Context as of 2016-04-19 | Philipp Gesang | 2016-04-19 | 2 | -4/+4 | |
| | | ||||||
| * | [db,fontloader] fix subfont table handling (by Dohyun Kim) | Philipp Gesang | 2016-04-18 | 2 | -2/+2 | |
| | | | | | | | | | | | | 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. | |||||
* | | Merge pull request #331 from phi-gamma/master | Philipp Gesang | 2016-04-18 | 16 | -155/+299 | |
|\| | | | | | current progress on 2.7 | |||||
| * | [doc] update graph for current file list | Philipp Gesang | 2016-04-18 | 1 | -12/+52 | |
| | | ||||||
| * | [tool,doc] inter fontloader warnings option | Philipp Gesang | 2016-04-18 | 2 | -45/+7 | |
| | | | | | | | | | | The option has become redundant with the new loader so we might as well get rid of it. | |||||
| * | [passim] update maintainer contact | Philipp Gesang | 2016-04-18 | 6 | -10/+8 | |
| | | ||||||
| * | [*] update news | Philipp Gesang | 2016-04-18 | 1 | -0/+1 | |
| | | ||||||
| * | [fontloader] sync with Context as of 2016-04-18 | Philipp Gesang | 2016-04-18 | 4 | -33/+145 | |
| | | ||||||
| * | [doc] update file list | Philipp Gesang | 2016-04-18 | 1 | -16/+28 | |
| | | ||||||
| * | [db] fix misleading error message | Philipp Gesang | 2016-04-18 | 1 | -4/+2 | |
| | | | | | | | | | | | | | | No such warnings with the new loader. Instead we need to test for the ``fontname`` / ``fullname`` fields. Thanks to @dohyunkim for reporting. | |||||
| * | [conf] move “use-fontforge” option into section “[db]” | Philipp Gesang | 2016-04-17 | 1 | -18/+18 | |
| | | | | | | | | | | Only font indexing is affected by “use-fontforge”. The fontloader itself will always use the new code. | |||||
| * | [doc] describe “use-fontforge” option in man page | Philipp Gesang | 2016-04-17 | 1 | -18/+24 | |
| | | ||||||
| * | [features] account for subfont indexing changes | Philipp Gesang | 2016-04-17 | 1 | -0/+4 | |
| | | | | | | | | | | | | 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. | |||||
| * | [features] adjust feature processor to new data structures | Philipp Gesang | 2016-04-17 | 1 | -4/+10 | |
| | | ||||||
| * | [db] undo commented out texmf tree processing | Philipp Gesang | 2016-04-17 | 1 | -1/+1 | |
| | | | | | | | | D’oh! Too much debugging =) | |||||
| * | [fontloader] quick fix by Hans for issue #326 | Philipp Gesang | 2016-04-17 | 1 | -2/+8 | |
| | | | | | | | | | | | | | | Addresses #326 This is a hot-fix with non-official code. The actual fix will come downstream later from Context as usual. | |||||
| * | [features] fix buggy state check | Philipp Gesang | 2016-04-17 | 1 | -2/+1 | |
| | | ||||||
* | | Merge pull request #330 from phi-gamma/master | Philipp Gesang | 2016-04-17 | 54 | -16616/+32580 | |
|\| | | | | | fontloader update | |||||
| * | [fontloader] sync with Context as of 2016-04-17 | Philipp Gesang | 2016-04-17 | 5 | -164/+207 | |
| | | ||||||
| * | [tool] adapt fullinfo to new loader | Philipp Gesang | 2016-04-16 | 1 | -4/+13 | |
| | | | | | | | | | | Note that this will explode on the current loader code due to a typo in font-otr.lua. Patch submitted upstream, please be patient. | |||||
| * | [fontloader] sync with Context as of 2016-04-16 | Philipp Gesang | 2016-04-16 | 7 | -10/+184 | |
| | | ||||||
| * | [features] rely on config to detect runtime mode | Philipp Gesang | 2016-04-16 | 1 | -6/+7 | |
| | | ||||||
| * | [tool] annihilate references to FF | Philipp Gesang | 2016-04-16 | 1 | -101/+36 | |
| | | | | | | | | | | | | | | 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. | |||||
| * | [fontloader] sync with Context as of 2016-04-15 | Philipp Gesang | 2016-04-15 | 3 | -28/+46 | |
| | |