Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | [db,fontloader] fix subfont table handling (by Dohyun Kim) | Philipp Gesang | 2016-04-18 | 1 | -1/+1 |
| | | | | | | 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. | ||||
* | [fontloader] sync with Context as of 2016-04-17 | Philipp Gesang | 2016-04-17 | 1 | -5/+1 |
| | |||||
* | [fontloader] sync with Context as of 2016-04-15 | Philipp Gesang | 2016-04-15 | 1 | -17/+26 |
| | |||||
* | [fontloader] sync with Context as of 2016-04-11 | Philipp Gesang | 2016-04-11 | 1 | -70/+150 |
| | | | | | | | | | | | | | | | 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** | ||||
* | [fontloader] sync Context as of 2016-04-07 | Philipp Gesang | 2016-04-07 | 1 | -0/+2202 |