summaryrefslogtreecommitdiff
path: root/src/fontloader
Commit message (Collapse)AuthorAgeFilesLines
* [fontloader] sync with Context as of 2016-05-22Philipp Gesang2016-05-2416-101/+93
|
* [fontloader] include font-one.luaPhilipp Gesang2016-05-201-0/+405
|
* [fontloader] sync with Context as of 2016-05-18Philipp Gesang2016-05-184-569/+230
|
* [fontloader] import new AFM loader directly from HansPhilipp Gesang2016-05-121-166/+216
|
* [fontloader] sync with Context as of 2016-05-11Philipp Gesang2016-05-115-543/+457
|
* [import,fontloader] pull new AFM/Type1 codePhilipp Gesang2016-05-091-161/+175
|
* [fontloader] sync with Context as of 2016-05-09Philipp Gesang2016-05-097-1184/+1226
| | | | | | Fixes #349 and #357. Also the new AFM code is due, let’s see what else we need to use it.
* [fontloader] sync with Context as of 2016-05-02Philipp Gesang2016-05-027-23/+41
|
* [fontloader] sync with Context as of 2016-04-27Philipp Gesang2016-04-273-22/+36
|
* [fontloader] sync with Context as of 2016-04-25Philipp Gesang2016-04-255-23/+53
|
* [fontloader] sync with Context as of 2016-04-24Philipp Gesang2016-04-244-34/+138
|
* [fontloader] sync with Context as of 2016-04-21Philipp Gesang2016-04-219-107/+370
| | | | | Hans fixed a couple issues due to our reports. Also, brand new Lua based PFB loader.
* [*] shred 2014 fontloaderPhilipp Gesang2016-04-191-13936/+0
| | | | | | 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-19Philipp Gesang2016-04-192-4/+4
|
* [db,fontloader] fix subfont table handling (by Dohyun Kim)Philipp Gesang2016-04-181-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-18Philipp Gesang2016-04-184-33/+145
|
* [fontloader] quick fix by Hans for issue #326Philipp Gesang2016-04-171-2/+8
| | | | | | | Addresses #326 This is a hot-fix with non-official code. The actual fix will come downstream later from Context as usual.
* [fontloader] sync with Context as of 2016-04-17Philipp Gesang2016-04-175-164/+207
|
* [fontloader] sync with Context as of 2016-04-16Philipp Gesang2016-04-167-10/+184
|
* [fontloader] sync with Context as of 2016-04-15Philipp Gesang2016-04-153-28/+46
|
* [fontloader] sync with Context as of 2016-04-11Philipp Gesang2016-04-114-139/+315
| | | | | | | | | | | | | | | 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-07Philipp Gesang2016-04-0732-10644/+18745
|
* [fontloader] sync fontloader package with Context revision 274c32699..Philipp Gesang2016-04-062-5349/+12577
|
* [fontloader] patch font-otn.lua to skip unusable contextpos featuresPhilipp Gesang2016-02-121-2/+2
| | | | | | | Address issue #322 The annotation says it all; reportedly this is fine with TL 2016, though.
* [fontloader] revert features handler temporarilyPhilipp Gesang2016-01-222-8/+68
| | | | | | | | | | | | 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.
* [fontloader] re-patch font-otn.lua to avoid crashPhilipp Gesang2016-01-111-1/+1
| | | | See issue https://github.com/lualatex/luaotfload/issues/303
* [fontloader] sync with Context as of 2016-01-11Philipp Gesang2016-01-114-16/+12
|
* [fontloader] sync reference loaderPhilipp Gesang2015-12-231-2/+2
|
* [fontloader] patch font-otn to preven calt crashPhilipp Gesang2015-12-221-0/+3
|
* [init] install some more accessors required by the fontloaderPhilipp Gesang2015-12-221-1/+4
|
* [fontloader] sync with Context as of 2015-12-21Philipp Gesang2015-12-2113-215/+5724
|
* [init] set up stubs for pre-0.87 LuatexPhilipp Gesang2015-12-212-5000/+0
|
* [package] remove luaotfload-packagePhilipp Gesang2015-12-121-99/+0
| | | | Not required since we now package the loader ourselves. Good riddance.
* [*] bump version and datePhilipp Gesang2015-12-091-2/+1
| | | | | We still had some 2014 values lingering around dark corners. In theory this is all meaningless wrt. the Git repo.
* [fontloader] sync with Context as of 2015-11-21Philipp Gesang2015-11-217-175/+122
|
* [fontloader] sync with Context as of 2015-10-29Philipp Gesang2015-10-2923-2145/+4796
|
* [init,main,package] split initialization in early and late stagePhilipp Gesang2015-07-221-1/+5
| | | | | | | | | | | | | | | | | | | | | This is a big move. Due to the restructuring of the initialization we can now separate the early tasks -- mostly dirty stuff like writing globals -- from the later stage where we actually inject the actual font loader. As a consequence, the basic configuration is now present before the font loader is injected. It’s not complete, though, in that the reconfiguration step must still be executed after the font loader is there, since some config variables require values to be set up by the loader. A decision is pending regarding how we address the situation; possible approaches are, in order of increasing complexity: * reconfigure twice, skip some of the steps the first time through * split reconfiguration into two stages * make configuration independent of fontloader values Design-wise, the last point would be the most desirable, naturally. Though the fontloader has been known to require extensive static preparation which might very well make that strategy impossible or unjustifiably demanding. We’ll see how it plays out …
* [import,fontloader] move imported package out of the wayPhilipp Gesang2015-07-211-0/+0
|
* [fontloader] sync with Context as of 2015-05-26Philipp Gesang2015-05-2611-446/+841
|
* [fontloader] sync with Context as of 2015-05-12Philipp Gesang2015-05-122-9/+15
|
* [fontloader] sync with Context as of 2015-05-04Philipp Gesang2015-05-042-21/+32
|
* [fontloader] sync with Context as of 2015-05-03Philipp Gesang2015-05-032-7/+60
|
* [fontloader] sync with Context as of 2015-04-20Philipp Gesang2015-04-202-1/+8
|
* [fontloader] sync with Context as of 2015-04-15Philipp Gesang2015-04-152-3/+21
|
* [fontloader] sync with Context as of 2015-04-13Philipp Gesang2015-04-134-34/+99
|
* [fontloader] unpackage functionality provided by the LualibsPhilipp Gesang2015-03-291-10/+16
|
* [fontloader] add and document dedicated packaging entrypointPhilipp Gesang2015-03-291-0/+90
|
* [fontloader] sync with Context as of 2015-03-29Philipp Gesang2015-03-292-236/+122
|
* [fontloader] sync with Context as of 2015-03-25Philipp Gesang2015-03-253-46/+246
|
* [fontloader] switch fallback to code from 2014 (works with Luatex 0.76)Philipp Gesang2015-03-181-657/+981
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-09 17:33:52 +0000