summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* [*] update newsPhilipp Gesang2016-04-281-0/+1
|
* [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.
* [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.
* [*] 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.
* [*] 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
|
* [aux] make fontname substitution more robustPhilipp Gesang2016-04-191-2/+7
| | | | | | | | | Another take on https://github.com/lualatex/luaotfload/issues/334 The parsing issues we aim to prevent occur with spaces because Luatex treats them as argument separators. Hence apply quoting only if necessary. Also use the appropriate format string as a defense against garbage inputs.
* [main] fix oversight in comment (thanks, Èlie)Philipp Gesang2016-04-191-1/+1
|
* [aux] fix crash with tfm fontsPhilipp Gesang2016-04-191-1/+4
| | | | | | | Fixes https://github.com/lualatex/luaotfload/issues/334 Old-style font definitions only need a font name, so the extra quotes aren’t necessary to feed the \fontname string back into \font.
* [features] cull legacy feature handlerPhilipp Gesang2016-04-191-145/+1
|
* [features] do not attempt to add features on incomplete fontsPhilipp Gesang2016-04-191-8/+18
|
* [doc] start chapter on font combosPhilipp Gesang2016-04-191-0/+31
|
* [*] shred 2014 fontloaderPhilipp Gesang2016-04-197-13969/+3
| | | | | | 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-182-2/+2
| | | | | | 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.
* [doc] update graph for current file listPhilipp Gesang2016-04-181-12/+52
|
* [tool,doc] inter fontloader warnings optionPhilipp Gesang2016-04-182-45/+7
| | | | | The option has become redundant with the new loader so we might as well get rid of it.
* [passim] update maintainer contactPhilipp Gesang2016-04-186-10/+8
|