summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
| * [features] straighten out logspamPhilipp Gesang2016-05-041-19/+18
| | | | | | | | | | | | | | Due to the origin in other parts of Luatex, some messages in this file were logged under the “load” facility; corrected. Also, the combo mechanism still spits debug levels of noise at log level zero; raised to two.
| * [letterspace] fix double free with disc componentsPhilipp Gesang2016-05-031-4/+1
| | | | | | | | | | | | | | | | Adress issue #350 For some reason our stack copy of the current node gets double-freed. Since the “components” field will probably vanish soon, we can get by for now by skipping the explicit free.
| * [tool] check for version info in stats tablePhilipp Gesang2016-05-031-15/+28
| | | | | | | | This could become the common check eventually.
| * [main,tool] reintroduce lost version checkPhilipp Gesang2016-05-032-19/+34
| | | | | | | | | | | | | | | | | | | | The version check was removed by accident in commit 5ce60cc98a30. This isn’t normally a problem except when people start to run the Pretest version on ancient Luatex binaries … In any case, the check must be present. While we’re at it, make the error messages consistent between the tool and a live TeX run. This can’t cover the fact that there is no (direct) means of determining the Luatex version when not running in TeX mode, so the checks still aren’t equivalent.
* | Merge pull request #352 from phi-gamma/masterPhilipp Gesang2016-05-029-37/+69
|\| | | | | fixes
| * [letterspace] remove useless state variablePhilipp Gesang2016-05-021-8/+3
| |
| * [letterspace] fix crash with fonts with missing glyphsPhilipp Gesang2016-05-021-7/+25
| | | | | | | | | | | | | | | | | | | | | | Fix issue #351 The letterspace node handler dereferences kern values of non-existant character information under some circumstances, causing Luatex to crash. To avoid this crash, check more thoroughly for the presence of the fields accessed. Discovered by @schlcht
| * [fontloader] sync with Context as of 2016-05-02Philipp Gesang2016-05-027-23/+41
| |
| * [*] update newsPhilipp Gesang2016-04-281-0/+1
| |
* | Merge pull request #348 from phi-gamma/masterPhilipp Gesang2016-04-285-31/+129
|\| | | | | Implement #263
| * [doc] extend conf manpage for the inclusion of “my:” lookupsPhilipp Gesang2016-04-281-1/+3
| |
| * [resolvers,conf] allow “my:” lookups in anon sequencesPhilipp Gesang2016-04-282-11/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows to domesticate packages that quite disrespectfully only use “anon:” lookups. Example from the test repo: \documentclass{scrartcl} \usepackage{fontspec} \directlua{ config.luaotfload = config.actions.apply (config.luaotfload, { run = { anon_sequence = { "my" } } }) } \directlua{ luatexbase.add_to_callback( "luaotfload.resolve_font", function (spec) spec.name = "comic.ttf" end, "user.openbsd_style") } \setmainfont{Adobe Premier Deluxe Overpriced} \begin{document} There is no escape. \end{document}
| * [doc] document new “anon-sequence” optionPhilipp Gesang2016-04-282-5/+25
| |
| * [tool,resolvers,conf] switch --find lookups to the actual resolversPhilipp Gesang2016-04-283-17/+30
| | | | | | | | | | | | | | | | The arguments to “--find” on the command line avoided calling the real index API functions and used crude approximations instead. In order to make “--find” obey the new “anon-sequence” configuration item, it needs to access the normal resolvers instead. This requires certain adaptations to allow for a fallback on the “file:” lookup.
| * [conf] handle corner cases when assigning the lookup sequencePhilipp Gesang2016-04-281-4/+29
| |
| * [conf,resolvers] add config option to tweak anon lookup sequencePhilipp Gesang2016-04-282-1/+40
| | | | | | | | | | | | | | | | | | Implements #263 The resolvers have already been decoupled a while ago but the goal of allowing the sequence to be reordered at will was still outstanding. Add a config option “anon-sequence” that is parsed as a comma-delimited list of sequence components.
* | Merge pull request #345 from phi-gamma/masterPhilipp Gesang2016-04-2720-343/+932
|\| | | | | first batch of fixes
| * [parsers] fix rhs parsing in configurationv2.7-fix-1Philipp Gesang2016-04-271-2/+2
| | | | | | | | | | | | | | | | Fix issue #344 An incomplete matching rule for determining configuration values caused return bytes (0x0d) to leak into the configuration if Windows style newlines are used. Fixed by adapting the pattern.
| * [db] restrict bold style fallback heuristicPhilipp Gesang2016-04-271-7/+15
| | | | | | | | | | | | @dohyunkim pointed out that due to the too broad criteria, secondary style variants like “heavy”, “black” ended up getting picked over the actual “bold”.
| * [fontloader] sync with Context as of 2016-04-27Philipp Gesang2016-04-273-22/+36
| |
| * [db] disarm fallback assignmentPhilipp Gesang2016-04-271-6/+6
| | | | | | | | | | | | | | When adapting to the new loader we repeated the mistake of classifying “bold” faces by too broad criteria, thereby sabotaging the recognition of large families from Adobe. Restore the old behavior by only treating those faces as bold fallback that advertise and exact weight of 700.
| * [db] adapt call to getinfo() for revised interfacePhilipp Gesang2016-04-271-3/+10
| |
| * [db] fix family / style matchingPhilipp Gesang2016-04-271-65/+24
| | | | | | | | | | | | | | | | | | | | Fix #342 Due to the reassigned fontname fields, certain values designating styles ended up being interpreted wrongly and members of the font families ended up in the wrong table. Thanks to @dohyunkim for spotting the issue.
| * [main] handle module load failurePhilipp Gesang2016-04-261-1/+25
| | | | | | | | | | Forward the errors received from require() in a readable manner and exit on the spot.
| * [aux] fix \fontdimen{10,114}Philipp Gesang2016-04-261-12/+11
| | | | | | | | | | | | | | | | Fix #341 Hironori Kitagawa pointed out that the patch for the other math parameters doesn’t work. Turns out Hans relocated the “mathconstants” table …
| * [aux] actually pull capheight and ascender values from the correct tablePhilipp Gesang2016-04-261-7/+12
| |
| * [aux] probe multiple characters when guessing the capital heightPhilipp Gesang2016-04-261-4/+22
| | | | | | | | | | Provide fallbacks in case no ‘X’ character is available for capheight measurement.
| * [aux] fix \fontdimen8 hackPhilipp Gesang2016-04-261-31/+63
| | | | | | | | | | | | | | | | Addresses #341 This cleans up the font patching code we inherited from Fontspec. In addition to treating the bitrot with an extra dose of fungicide, we also make the process in which the final values are chosen more transparent.
| * [fontloader] sync with Context as of 2016-04-25Philipp Gesang2016-04-255-23/+53
| |
| * [loaders,resolvers] tone down default log noisePhilipp Gesang2016-04-252-10/+8
| |
| * [db] fix version fieldPhilipp Gesang2016-04-241-1/+1
| | | | | | | | | | | | | | Fix #337 This amends the apparent failure of luaotfload-tool as reported by @eg9 and others.
| * [db,loaders] clarify support for PFBPhilipp Gesang2016-04-242-4/+13
| | | | | | | | | | | | | | | | | | | | The current PFB loader, although it is indeed completely independent of the FF libraries, is not yet feature complete. Only the loading of vectors is supported which suffices for font rendering given the AFM information. According to Hans, we have decent chance of it growing into a full-fledged reader for 1.0.
| * [fontloader] sync with Context as of 2016-04-24Philipp Gesang2016-04-244-34/+138
| |
| * [aux] make name_of_slot API more robustPhilipp Gesang2016-04-241-2/+14
| |
| * [aux] make slot_of_name API more robustPhilipp Gesang2016-04-241-15/+22
| |
| * [aux] fix features table access (issue #338)Philipp Gesang2016-04-241-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 snippetPhilipp Gesang2016-04-231-1/+1
| | | | | | | | Reported by @u-fisher on Github.
| * Revert "[db,conf] drop support for PS fonts"Philipp Gesang2016-04-212-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-21Philipp Gesang2016-04-219-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/masterPhilipp Gesang2016-04-2110-107/+61
|\| | | | | 2.7
| * [*] bump versionv2.7Philipp Gesang2016-04-215-9/+9
| |
| * [*] update newsPhilipp Gesang2016-04-211-2/+2
| |
| * [*] remove references to obsolete formats (PF{A,B}, DFONT, FEA)Philipp Gesang2016-04-207-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 combinationsPhilipp Gesang2016-04-201-6/+28
| | | | | | | | It’s sort of official now ;)
| * [db,conf] drop support for PS fontsPhilipp Gesang2016-04-202-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/masterPhilipp Gesang2016-04-206-191/+96
|\| | | | | format and feature handling, fixes for 2.7
| * [*] update newsPhilipp Gesang2016-04-201-1/+2
| |
| * [doc] rip our section about feature filesPhilipp Gesang2016-04-201-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 Gesang2016-04-201-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 combosPhilipp Gesang2016-04-201-1/+55
| |
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-06 10:40:02 +0000