summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* [aux,init] move lazy char-def loading code into earlier stage of initializationPhilipp Gesang2016-04-092-129/+131
| | | | | | | | | | | | | | The fontloader requires parts of the ``characters`` table to be present at load time. This turns out to interfere with our custom of installing the lazy loader for the table components only after the fontloader has been injected. Since inserting the code at the appropriate place in the loading chain would be tedious and unmaintainable due to the various load options, we just preinstall the metatable onto an empty table prior to loading the loader. Some precautions had to be taken regarding the ``classifiers`` subhash of the table that needs to be relocated from the data we received via mkcharacters.
* [init] force preloading of the character tablePhilipp Gesang2016-04-082-4/+8
|
* [db] ditch our gzip wrappersPhilipp Gesang2016-04-081-41/+4
| | | | | We again depend on the full Lualibs set for some time so our wrappers are irrelevant as we can just use the similar once from there.
* [init] addremove fontloader filesPhilipp Gesang2016-04-081-22/+35
|
* [import] fix dupePhilipp Gesang2016-04-081-1/+0
|
* [*] update dates, versionPhilipp Gesang2016-04-0713-18/+18
|
* [*] update newsPhilipp Gesang2016-04-071-0/+2
|
* [status] addremove fontloader files from/to listPhilipp Gesang2016-04-071-10/+18
|
* [import] addremove oversightsPhilipp Gesang2016-04-071-3/+0
|
* [fontloader] sync Context as of 2016-04-07Philipp Gesang2016-04-0732-10644/+18745
|
* [import] adapt to grand upstream restructuringPhilipp Gesang2016-04-071-49/+89
| | | | | | | | | | | | | | | | | | | | | Two not quite unrelated changes have to be accounted for: * Finally, the source for Context MkII and MkIV are being kept in separate trees, at least as far as the format is concerned. All out scripts that pull code from upstream had to be adapted. * New fontloader. This has been cooking for half a year maybe: Some of our troubles with 2.6 were caused by separating out the revised but highly experimental code from the self-contained fontloader, despite Hans’ great efforts to make it seamless. Now that the new fontloader is deemed mature enough, we have to accomodate the switchover. The fallout exceeds the bounds of Luaotfload proper: The Lualibs package had to be extended as well, adding a rather tiny library from the ``util-*`` namespace. With the latest setup, a fontloader can indeed be assembled automatically again. No testing has taken place yet, so it might not even run.
* [characters] add code for extracting the “classifiers” tablePhilipp Gesang2016-04-071-19/+83
| | | | | | | | | The extraction code itself was taken from luatex-basics-prepare.tex. In Context, this file generates “luatex-basics-chr.lua” a stripped down version of char-def.lua. Just as our exisiting mkcharacters script. Interesting that Hans chose a similar path to what we do ;) The code, which requires some functionality from char-ini.lua, has thus been added as a function to the script.
* [fontloader] sync fontloader package with Context revision 274c32699..Philipp Gesang2016-04-062-5349/+12577
|
* [import] do not abort immediately upon encountering missing filePhilipp Gesang2016-04-061-20/+32
| | | | | | Larger changes by upstream are easier to comprehend if errors during import are counted instead. The script will exit non-zero regardless if such an error occurred, but otherwise attempt to import all the files.
* [tool] status library API falloutPhilipp Gesang2016-04-051-3/+4
| | | | | With revision 5624, the status library was overhauled. Among others we lose the ``luatex_svn`` field which was rather useful for debugging :/
* *: bump version and datePhilipp Gesang2016-02-193-5/+9
| | | | Now that we’re heading towards TL 2016, this seems necessary.
* [features,parsers] implement font fallbacksPhilipp Gesang2016-02-193-25/+41
| | | | | | | | | | | | | | | | | | | | | Building on the combination mechanism, this allows defining fallback fonts of which all glyphs are pulled that aren’t currently part of the base font. Example: \input luaotfload.sty \font \lm = file:lmroman10-regular.otf:mode=base \font \cmu = file:cmunrm.otf:mode=base \font \lmu = "combo: 1->\fontid\lm; 2->\fontid\cmu,fallback" \lmu Eh bien, mon prince. Gênes et Lueques ne sont plus que des apanages, des поместья, de la famille Buonaparte. \bye This allows setting Latin Modern text that contains Cyrillic letters. Note that -- as with the other combinations -- only glyphs are considered, no other properties of the fallback font. So besides the occasional letter in a different script this functionality is probably useless.
* [parsers] rework combo syntaxPhilipp Gesang2016-02-191-17/+27
| | | | | | | | | | | Use arrows to emphasise what’s mapped. Allow whitespace to visually separate items. Also allow optional grouping with parentheses. Now it’s possible to define a combination as follows: \font \f = "combo: 1 -> 42; 2 -> 1337, U+0042-U+0084; 3 -> (55, 0x54 * 0x45 * 0x58)"
* [parsers] allow whitespace around combo elementsPhilipp Gesang2016-02-191-7/+10
| | | | | | | | | | This gives more leeway to the notation, allowing font definitions to become more readable: \font \f = "combo: 1 / \fontid\one, 2 / \fontid\two / 0x41-0x5a, 3 / \fontid\three / 0x42, 4 / \fontid\three / 0x54 * 69 * U+58"
* [features,loaders] fix lookup conflicts via introduction of “evl” lookupPhilipp Gesang2016-02-193-21/+26
| | | | | | | | This introduces a forced lookup type “evl” that bypasses the other methods. The specification is extended with the correct values including a more meaningful hash string. As a result, the loader no longer attempts to interpret the specification as a “file:” request but the backend can still resolve the necessary files.
* [features,loaders] allow for direct injection of tfmdata when defining fontsPhilipp Gesang2016-02-182-7/+56
|
* [features] handle combination definitionsPhilipp Gesang2016-02-161-7/+106
|
* [parsers,features] parse combo requestsPhilipp Gesang2016-02-152-2/+42
| | | | | | | Highly experimental at this point. The font request parser has been extended to handle combinations of already defined fonts. Nothing else has been implemented yet, so the request handler will simply error out with a message.
* [fontloader] patch font-otn.lua to skip unusable contextpos featuresPhilipp Gesang2016-02-122-3/+3
| | | | | | | Address issue #322 The annotation says it all; reportedly this is fine with TL 2016, though.
* [doc] fix typo and formatting in man pagePhilipp Gesang2016-02-041-4/+4
| | | | Spacing is off in the ``.5``, we didn’t account for markup.
* [resolvers] allow arbitrary sequence lookupsPhilipp Gesang2016-01-271-42/+84
| | | | | | | | This primarily affects the “anon” lookup. However, since we cannot any longer determine the lookup success by crude means, the resolver signature had to be modified to indicate success or failure via the return value. This does no longer match the resolver implementation of Context but the interface has become much cleaner.
* [init] fix Context module sequencev2.6-fix-5showPhilipp Gesang2016-01-221-3/+3
|
* [fontloader] revert features handler temporarilyPhilipp Gesang2016-01-222-8/+68
| | | | | | | | | | | | Address issue #318 This reverts the changes made to font-otn.lua with commit adc43c3c24.. Certain features related to directionality are not handled correctly with the most recent fontloader. As a temporary measure, revert the handling code in font-otn.lua and restore the values it references. While this appears to suppress the issue, we’ll switch back to the upstream code once we have an actual solution.
* [init] always log final fontloader choicePhilipp Gesang2016-01-211-14/+14
|
* [fontloader] re-patch font-otn.lua to avoid crashPhilipp Gesang2016-01-111-1/+1
| | | | See issue https://github.com/lualatex/luaotfload/issues/303
* [features] import feature loading codePhilipp Gesang2016-01-112-13/+19
|
* [fontloader] sync with Context as of 2016-01-11Philipp Gesang2016-01-114-16/+12
|
* [features] update name tablesPhilipp Gesang2016-01-091-607/+808
|
* [letterspace] fix wrong construction of node list after spacing ligaturesPhilipp Gesang2016-01-081-19/+28
|
* [features] excise stray feature definitionv2.6-fix-4Philipp Gesang2015-12-231-13/+0
| | | | | | Closing #309 Many thanks for @simifilm for the report!
* [fontloader] sync reference loaderPhilipp Gesang2015-12-231-2/+2
|
* [auxiliary] move callback handling to initializationPhilipp Gesang2015-12-232-24/+59
|
* [mkstatus] safer parsing of git-describe(1) outputPhilipp Gesang2015-12-231-1/+3
|
* [aux] assimilate logger to conventionv2.6-fix-3Philipp Gesang2015-12-221-32/+32
|
* [fontloader] patch font-otn to preven calt crashPhilipp Gesang2015-12-221-0/+3
|
* [init] install some more accessors required by the fontloaderPhilipp Gesang2015-12-222-2/+12
|
* [features] improve font feature injectionPhilipp Gesang2015-12-221-37/+77
|
* [fontloader] sync with Context as of 2015-12-21Philipp Gesang2015-12-2113-215/+5724
|
* [init] set up stubs for pre-0.87 LuatexPhilipp Gesang2015-12-215-5012/+44
|
* [features] import latest changes to the feature handlerPhilipp Gesang2015-12-211-8/+6
|
* [features] conditionally pull in old feature mechanismPhilipp Gesang2015-12-211-1/+145
| | | | | Pretty hackish and probably not supported forever, but this is required on account of the changes to the loader since TL 2014.
* [letterspace] fix oversight in kern handlingPhilipp Gesang2015-12-211-0/+1
|
* [letterspace] employ dedicated accessors where appropriatePhilipp Gesang2015-12-211-35/+50
|
* [features] pull in upstream fixesPhilipp Gesang2015-12-211-6/+10
| | | | Fixes the crash but apparently not the feature.
* [letterspace] fix access of invalid node fieldPhilipp Gesang2015-12-181-3/+3
| | | | | | | | This addresses one error reported by u/priyadarshan: https://github.com/lualatex/luaotfload/issues/310 Some chained node field access got garbled during the update to nuts.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-02 08:05:34 +0000