summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Merge remote-tracking branch 'canonical/pr/402'Philipp Gesang2017-02-021-1/+10
|\
| * use design size to calculate the distance for `inrange`Yan Zhou2017-02-021-1/+10
| |
* | Merge remote-tracking branch 'canonical/pr/401'Philipp Gesang2017-02-021-1/+1
|\ \
| * | Avoid more than one `inrange` when there’s no overlapYan Zhou2017-02-021-1/+1
| |/
* | [db] fix design size scalingPhilipp Gesang2017-02-021-14/+29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As discussed in issue #398. Ad futuram rei memoriam the gist of it: - For the index, all values are scaled (decipoints * sp) / 10 * (7227 / 7200). - The ``bp`` case (the default, OT-standard), needs no conversion because it matches how values are stored in the index. - The ``pt`` case essentially reverts the bp→pt part of scaling done for the database by scaling the asked size by the same factor, i. e. by 7227 / 7200. - The ``dd`` needs an extra 1238 / 1157. Requesting a font at 10pt will then: - ask for a size of 655360 for ``bp`` / default; - ask for 657817 for ``pt``; - ask for 703870 for ``dd``.
* | [features] remove unneeded tlig featuresPhilipp Gesang2017-02-021-17/+0
| | | | | | | | | | | | Fix #397 These four features should not be inserted automatically.
* | Merge branch 'canonical-master'Philipp Gesang2017-02-011-5/+5
|\|
| * Fix calculation of database optical sizesYan Zhou2017-02-021-5/+5
| | | | | | The conversion from reported design size etc., to "true `sp` value" is actually converting from `bp` to `pt`.
* | [parsers] remove “experimental” flag from kpse, my lookupsPhilipp Gesang2017-01-311-2/+0
|/ | | | These have stabilized a long time ago and will be supported.
* [db] fix duplicate files in scan listPhilipp Gesang2017-01-291-3/+1
| | | | | | Fix #394 Due to an oversight, all files except AFM got scanned twice.
* [*] bump year and versionPhilipp Gesang2017-01-299-15/+12
|
* [db] move design size handling into lookupPhilipp Gesang2017-01-291-44/+45
| | | | | Store design sizes in sp in index. Lookups are performed using sp so the design size factor can be applied at runtime.
* [conf] improve defaults handling of designsize-dimenPhilipp Gesang2017-01-292-23/+5
|
* [conf,db] make design size dimension configurablePhilipp Gesang2017-01-292-14/+74
|
* [db] scale optical sizes to ptPhilipp Gesang2017-01-291-21/+33
| | | | Fix #389
* [main] make main() no-op when called againPhilipp Gesang2017-01-291-0/+10
| | | | | | Fix #390 Suggested by @davidcarlisle.
* [fontloader] sync with Context as of 2017-01-29Philipp Gesang2017-01-297-32/+165
|
* [letterspace] address node deallocation issuesPhilipp Gesang2017-01-291-2/+6
| | | | | | With 1.0.3 the test pln-letterspace-12-double-ligature-issue-350.tex causes a crash on account of a double free. Remove the code that calls nodedirect.free() on the removed nodes until this is better understood.
* [log] handle logging more defensivelyPhilipp Gesang2017-01-291-3/+27
|
* [fontloader] sync with Context as of 2016-10-22Philipp Gesang2016-10-222-23/+79
|
* [fontloader] sync with Context as of 2016-10-20v2.8-rc3Philipp Gesang2016-10-202-23/+29
|
* [db] tentatively reintroduce fallback for italicPhilipp Gesang2016-10-191-6/+12
| | | | | | | | | | Fix assignment of LM series fonts. Currently these are broken because of borked typosub identifiers like “8oblique” that prevent exact name matching and at the same time exclude matching the (usable) subfamily. Introduce a heuristic based on the italic angle value that assigns italic as a fallback in these cases. Test: https://bitbucket.org/phg/lua-la-tex-tests/src/857c83ca98cb35153979a0613d3a742bfd93f834/lua/tla-names-3-lm.lua
* [db,conf,doc] kill off references to FF loaderPhilipp Gesang2016-10-172-21/+0
| | | | | The config option must go since the FF based code was removed already some time ago.
* [fontloader] sync with Context as of 2016-10-17Philipp Gesang2016-10-177-86/+491
|
* [tool] fix crash in verbose error messagePhilipp Gesang2016-09-291-1/+2
|
* [features,tool] fix subfont handling in file loadingPhilipp Gesang2016-09-292-7/+9
| | | | Subfont loading seems to have been broken for a while but no reports …
* [tool] remove unnecessary modulesPhilipp Gesang2016-09-291-12/+0
| | | | | These only make the loader emit warnings because of the missing runtime environment. They weren’t needed to begin with.
* [main,tool] fix version checkPhilipp Gesang2016-09-282-9/+12
| | | | | | | Fixes #382 Luaotfload will fail with an up to date Luatex on account on a buggy minimum version check. Many thanks to @davidcarlisle for the report.
* [features,parsers] add extremely important featurePhilipp Gesang2016-09-272-1/+7
| | | | | | | | | Credits to Taco for the talk at Kalenberg that inspired the feature. Extending the parser is required so we can have proper name for the feature. Happy Luatex 1.0.0
* [fontloader] sync with Context as of 2016-09-24Philipp Gesang2016-09-243-62/+74
|
* [fontloader] patch basics-gen to include missing convertersPhilipp Gesang2016-09-231-0/+20
| | | | | Fontloader crashes during loading. Hans is notified, let’s wait for him to fix it properly.
* [fontloader] sync with Context as of 2016-09-23Philipp Gesang2016-09-234-89/+275
| | | | This incorporates our patch for issue #377.
* [fontloader] HACK hot-patch loader to fix crashv2.8-rc1Philipp Gesang2016-09-201-4/+6
| | | | Patch has been upstreamed for a while but no response yet.
* [db] install required functions from font-synPhilipp Gesang2016-09-201-0/+44
| | | | | | The loader makes some assumptions about available lookup functions early on. Since fonts-syn.lua only installed dummies for most of these, we might as well do that too.
* [fontloader] sync with Context as of 2016-09-15Philipp Gesang2016-09-1512-132/+933
|
* [fontloader] sync with Context as of 2016-08-29Philipp Gesang2016-08-2914-909/+1145
|
* [features] drop code from font-otcPhilipp Gesang2016-08-151-778/+8
| | | | | | | | | addfeature() and the likes -- with less extensive logging -- is now provided directly by means of font-otc.lua so we don’t need to keep these parts around any longer. The loader installs anum features identical to ours and a slightly different “tlig” one which we override. Clean up locals and misleading comments while we’re at it.
* [scripts, init] include font-otc at the appropriate placesPhilipp Gesang2016-08-151-0/+1
|
* [fontloader] sync with Context as of 2016-08-15Philipp Gesang2016-08-153-1/+1726
| | | | | CAVEAT LECTOR This adds font-otc.lua part of which has already been included in our feature handler.
* [features] use the new feature registry for TFMPhilipp Gesang2016-07-301-30/+30
| | | | No need for patching font-tfm.lua any longer.
* [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-271-120/+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.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-04 02:19:52 +0000