summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* [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
|
* [*] update newsPhilipp Gesang2016-04-181-0/+1
|
* [fontloader] sync with Context as of 2016-04-18Philipp Gesang2016-04-184-33/+145
|
* [doc] update file listPhilipp Gesang2016-04-181-16/+28
|
* [db] fix misleading error messagePhilipp Gesang2016-04-181-4/+2
| | | | | | | No such warnings with the new loader. Instead we need to test for the ``fontname`` / ``fullname`` fields. Thanks to @dohyunkim for reporting.
* [conf] move “use-fontforge” option into section “[db]”Philipp Gesang2016-04-171-18/+18
| | | | | Only font indexing is affected by “use-fontforge”. The fontloader itself will always use the new code.
* [doc] describe “use-fontforge” option in man pagePhilipp Gesang2016-04-171-18/+24
|
* [features] account for subfont indexing changesPhilipp Gesang2016-04-171-0/+4
| | | | | | The new Lua based loader consistently numbers subfonts from one, not zero like the Fontforge one. We correct the value immediately before passing a handled font request on to the loader.
* [features] adjust feature processor to new data structuresPhilipp Gesang2016-04-171-4/+10
|
* [db] undo commented out texmf tree processingPhilipp Gesang2016-04-171-1/+1
| | | | D’oh! Too much debugging =)
* [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.
* [features] fix buggy state checkPhilipp Gesang2016-04-171-2/+1
|
* [fontloader] sync with Context as of 2016-04-17Philipp Gesang2016-04-175-164/+207
|
* [tool] adapt fullinfo to new loaderPhilipp Gesang2016-04-161-4/+13
| | | | | Note that this will explode on the current loader code due to a typo in font-otr.lua. Patch submitted upstream, please be patient.
* [fontloader] sync with Context as of 2016-04-16Philipp Gesang2016-04-167-10/+184
|
* [features] rely on config to detect runtime modePhilipp Gesang2016-04-161-6/+7
|
* [tool] annihilate references to FFPhilipp Gesang2016-04-161-101/+36
| | | | | | | The tables emitted by the new font reader functions do not correspond to their Fontforge counterparts. Thus, some of the display routines had to be rewritten, in some cases like the names table this resulted in the removal of a good deal of obsolete code.
* [fontloader] sync with Context as of 2016-04-15Philipp Gesang2016-04-153-28/+46
|
* [db] fix extraction of name info important for family clusteringPhilipp Gesang2016-04-151-76/+98
| | | | | | | … or perhaps more accurately, “megafamily”. For the time being we prefer the “windows” versions of the fonts due to the higher quality of the “typographic family” and “subfamily” fields. Another advantage of the new loader over FF is that we’re even given that choice.
* [db] pull raw name information with getinfo()Philipp Gesang2016-04-131-3/+9
| | | | | | This facility was added by Hans to accomodate our peculiar requirements: There should be no fallback from prefmodifiers to familyname since that removes valuable information about larger font sets like the Adobe ones.
* [init] avoid infinite recursion in characters.__indexPhilipp Gesang2016-04-131-1/+1
| | | | Fallout of the new character table loading routine.
* [db] add some stats regarding the new loaderPhilipp Gesang2016-04-131-25/+99
|
* [db] adjust names extraction to Lua loaderPhilipp Gesang2016-04-121-59/+79
|
* [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**
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-01 03:29:00 +0000