summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* [fontloader] sync with Context as of 2016-07-30Philipp Gesang2016-07-306-677/+799
| | | | Hans appears to have heard our pleas =)
* [features,fontloader] fix adding featuresPhilipp Gesang2016-07-273-11/+55
| | | | | | | | | | This makes our own features work with otf.addfeature(). However, for TFM it’s still not functional out of the box since the enhancer is installed at a time when it has not been defined yet. An answer from Hans is pending. In the meantime, we put a crude hack into our font-tfm.lua to allow injecting the enhancer retroactively on Luaotfload init.
* [loaders] take tfm path directly where appropriatePhilipp Gesang2016-07-271-2/+3
| | | | | The AFM one is still preferable when passed a PFB because of the extra checking it does.
* [features] remove check preventing application of features to TFM filesPhilipp Gesang2016-07-271-3/+4
|
* [aux] unrestrict fontname rewritingPhilipp Gesang2016-07-271-7/+5
| | | | | Since TFM fonts now take the same path as OTF and suchlike, not passing on the spec literally may actually be harmful.
* [fontloader,import,status] drop luatex-plain-tfm.luaPhilipp Gesang2016-07-273-123/+0
|
* [fontloader,import] drop font-otd.luaPhilipp Gesang2016-07-271-268/+0
|
* [fontloader] sync with Context as of 2016-07-26Philipp Gesang2016-07-268-34/+181
|
* [loaders] hook the generalized afm loader directly into tfm, pfb, and afm ↵Philipp Gesang2016-07-151-20/+4
| | | | | | | formats Latest updates to the loaders seem to have obsoleted a number of our precautions. Neat.
* [features] correctly unset subfontPhilipp Gesang2016-07-151-0/+2
| | | | | Even though it works fine as it was, the loader actually expects “false” as the value to indicate that no subfont was requested.
* [loaders] make TFM take the AFM pathPhilipp Gesang2016-07-141-1/+2
|
* [fontloader] sync with Context as of 2016-07-14Philipp Gesang2016-07-144-135/+252
|
* [features] include feature spec validationPhilipp Gesang2016-07-081-0/+36
|
* [tool] update load sequence for font-tfmPhilipp Gesang2016-07-071-2/+4
| | | | | | Also set a dummy ``pdf`` table that is referenced in the file. Whether we actually need font-tfm in luaotfload-tool should be reevaluated at some point before 2.8.
* [status,import,fontloader] add luatex-plain-tfm.lua and update scriptsPhilipp Gesang2016-07-073-3/+124
|
* [features] update otf.enhancers.addfeature()Philipp Gesang2016-07-071-15/+75
|
* [init] postpone loading of font-tfmPhilipp Gesang2016-07-071-2/+2
|
* [fontloader] sync with Context as of 2016-07-05Philipp Gesang2016-07-0522-611/+1619
|
* [*] update datev2.7-fix-3Philipp Gesang2016-06-165-6/+6
|
* [fontloader] sync with Context as of 2016-06-16Philipp Gesang2016-06-166-405/+441
|
* [doc] clarify behavior of update-live in config manpagePhilipp Gesang2016-06-151-1/+2
|
* [db] fix initialization behavior to prevent crashPhilipp Gesang2016-06-151-5/+4
| | | | | | | | | | | Reported by @dohyunkim: https://github.com/lualatex/luaotfload/pull/364#issuecomment-226059150 Under certain circumstances, update_names() was invoked with an empty table instead of a correctly initialized one, breaking the assumptions of the db populating code. This commit also guards more strongly against this kind of oversight and tidies up the db constructor.
* [fontloader] sync with Context as of 2016-06-14Philipp Gesang2016-06-143-21/+27
|
* [db] adapt error handling to new fontloader conventionsPhilipp Gesang2016-06-121-14/+21
|
* [db] fix crash with missing name dataPhilipp Gesang2016-06-121-2/+2
|
* [fontloader] import font-oclPhilipp Gesang2016-06-126-8/+315
| | | | | Some of the more absurd aspects of fonts ;) This will fork inkscape for the actual SVG processing.
* [fontloader] sync with Context as of 2016-06-12Philipp Gesang2016-06-1218-86/+1464
|
* [features] fix missing localPhilipp Gesang2016-06-111-2/+3
| | | | | | | The new addfeature() as of 499160de78a1 accesses utf8.len() which wasn’t imported at this point. Another import, utf8.char(), became irrelevant. Spotted by @doyunkim
* [init] adapt Context base path for file loaderPhilipp Gesang2016-06-101-10/+31
| | | | | | | | | Fix issue #344 The paths changed a while ago making a change necessary. We can’t just replace the path because older versions of the tree would fail, rendering bisection unusable. We compensate by testing the candidate directories beforehand.
* [fontloader] sync with Context as of 2016-05-31Philipp Gesang2016-06-105-78/+128
| | | | | | This corresponds to commit a274872832cd on the mirror repo. The changes since then were numerous but seem to introduce a couple new files we didn’t ask for =) Later.
* [db] resolve symlinks when traversing the file systemPhilipp Gesang2016-06-081-31/+41
| | | | | | | | | Addresses #359 and #325 To avoid duplicate entries, paths have to be resolved before collecting them. This necessitates loop detection of some sort, currently implemented naively as a flat table containing the directories already traversed.
* [db] include values of missing fields in diagnosticPhilipp Gesang2016-06-071-2/+3
|
* [conf] fix malformed filePhilipp Gesang2016-06-071-1/+0
| | | | | | | | This was introduced with commit 67ad1263d032 during a code removal frenzy. Many thanks to @grizzilus for pointing that one out: https://github.com/phi-gamma/luaotfload/commit/67ad1263d0328fc74928a9a1d06ea9aa0ee9a116#commitcomment-17726875
* [aux] remove double scaling of capheight from typoascenderPhilipp Gesang2016-06-031-3/+7
| | | | | | | | | Fix #358 The typographic ascender value from the metrics (Windows metrics) table comes prescaled by the fontloader but we scaled it nevertheless. This is not true, however, for the value in the metrics table. Fix the access method to treat the values differently.
* [db] fix name assignmentPhilipp Gesang2016-05-311-11/+34
| | | | | | | | | Address issue #356 The DejaVu Family needs stricter handling of fallback choices so we take the font’s avertised width into consideration. This used to be easier with the old loader since it had some decent heuristics in place for the more or less reliable “fontstyle_name”.
* [db] ditch fontforge compatibility codePhilipp Gesang2016-05-263-192/+119
| | | | | | | | Remove all the FF stuff and the config option. The transition is complete, no need to keep these things around any longer. Since we won’t be going back to the FF loader we might as well dispose of the junk identifiers and the translation layer as well.
* [fontloader] import fix by Hans for crashes with ancient Linotype Palatino filesPhilipp Gesang2016-05-251-26/+39
| | | | | | | | | | | | | The crash happens with these broken files MS used to ship: beef66370e7124eb683514ad9ad07576 palabi.ttf 975972a205fd91a532d1b7433281af70 palab.ttf be4590eba976dace111b6686f6dade52 palai.ttf 96261bb90c9babbf8042ce7f43200d65 pala.ttf on account of a broken rule in the “s_s_l” lookup. The change removes the entire lookup in this case since otherwise the rest of the font behaves *very* strange.
* [fontloader] sync with Context as of 2016-05-22Philipp Gesang2016-05-2416-101/+93
|
* [fontloader] include font-one.luaPhilipp Gesang2016-05-206-10/+424
|
* [featurs,loaders] adjust loader specifications to Context conventionsPhilipp Gesang2016-05-182-9/+7
|
* [fontloader] sync with Context as of 2016-05-18Philipp Gesang2016-05-184-569/+230
|
* [loaders] implement readable load failure messagePhilipp Gesang2016-05-131-4/+19
| | | | | | | | Add a message that includes the information relevant for troubleshooting. Due to the spammy nature of the message printed by Fontspec this is not exactly useful with Latex so disabled by default for now.
* [loaders] make AFM wrappers more consistentPhilipp Gesang2016-05-131-9/+11
|
* [features] update addfeature()Philipp Gesang2016-05-121-146/+379
|
* [features,loaders] tidy up loading of afmPhilipp Gesang2016-05-122-8/+26
|
* [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
|
* [tool] fix invocation of names.update()Philipp Gesang2016-05-091-1/+1
|
* [db] fix inclusion of AFM fontsPhilipp Gesang2016-05-091-14/+19
| | | | | The assumption that the AFM/PFB pair will reside in the same directory together is wrong for TeX Live. Hence the new lookup against kpse.
* [import,fontloader] pull new AFM/Type1 codePhilipp Gesang2016-05-097-187/+201
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-17 12:58:37 +0000