-
Notifications
You must be signed in to change notification settings - Fork 8
loading another fontloader #344
Comments
···<date: 2016-04-26, Tuesday>···<from: u-fischer>···
Works here. We’re just using Please post the output of this snippet fed into
|
It works for the "simple" value if I add a semikolon at the end:
Perhaps a (windows) line ending issue? I couldn't yet get it working to setup a path to context-minimals. I tried all sort of variants of
but nothing worked. I get messages about empty prefix and then non-existing pathes:
|
The following syntax seems to work:
(the space after the colon is important.) Then luaotfload started to use the right prefix. But it still didn't find the files as luaotfload-init.lua declares
But actually the files are in base/mkiv. After using
it worked. |
···<date: 2016-04-26, Tuesday>···<from: u-fischer>···
The semicolon is the comment character and unnecessary at the
Hans split the package by format recently. |
Yes I know. After I started to suspect that the end-of-line could be a problem I used it like a % in tex to hide it.
But it doesn't. I just tried it out: With Unix line endings (LF)
That explains it. Can one inject |
···<date: 2016-04-27, Wednesday>···<from: u-fischer>···
I can reproduce that. Somehow the |
Fix issue lualatex#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.
Fix issue lualatex#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.
With the update from today CF+LF ending is no longer a problem. But it still doesn't work to load the fontloader from context-minimals with
I had to change again line 226 from luaotfload-init.lua to
(then it worked even without the space after the first colon). |
Fix issue lualatex#344 The paths changed a while ago making a change necessary. We can’t just replace the path because older versions of the tree would fail, rendering bisection unusable. We compensate by testing the candidate directories beforehand.
Path fixed, please check the new release. |
According to the documentation (2016/04/21 v2.7) and luaotfload.conf.main5.pdf it should be possible to load another fontloader with a suitable setting in luaotfload.conf
I tried various variants and they all failed with one exception
reference gives the error:
which is surprising as kpsewhich finds the lua without problems:
fontloader=default
andfontloader=context
fails with similar messages (not so surprising as the files are not there).fontloader=context:
loads the files from the texlive context.I failed to find a way to tell luaotfload the path to my standalone context. Depending on the path (the colons) luaotfload used the context in texlive or the default fontloader.
The text was updated successfully, but these errors were encountered: