On 6/13/2018 1:55 PM, Ulrike Fischer wrote:
Am Sun, 10 Jun 2018 13:24:40 +0200 schrieb Hans Hagen:
i changed the parser for generic a bit so you need to check careful next
beta as i'm only testing some basic plain loading
I found something else that changed:
The otf-handler registerpalette
Am Sun, 10 Jun 2018 13:24:40 +0200 schrieb Hans Hagen:
> i changed the parser for generic a bit so you need to check careful next
> beta as i'm only testing some basic plain loading
I found something else that changed:
The otf-handler registerpalette is gone, and so coloring of fonts
like in
Am Sun, 10 Jun 2018 13:24:40 +0200 schrieb Hans Hagen:
> i changed the parser for generic a bit so you need to check careful next
> beta as i'm only testing some basic plain loading
It broke ;-(
luaotfload complained about a missing registersplit,
then about a missing addspecifier, so I
On 6/10/2018 12:58 PM, Ulrike Fischer wrote:
Am Sun, 10 Jun 2018 12:42:25 +0200 schrieb Hans Hagen:
Thanks. But if protection is possible, why doesn't [...] already
does it? I thought that in the brackets is always only a path
anyway.
because we share soem code with context and i don't want
Am Sun, 10 Jun 2018 12:42:25 +0200 schrieb Hans Hagen:
>> Thanks. But if protection is possible, why doesn't [...] already
>> does it? I thought that in the brackets is always only a path
>> anyway.
> because we share soem code with context and i don't want to support this
> [] syntax there
On 6/9/2018 11:34 PM, Ulrike Fischer wrote:
Am Sat, 9 Jun 2018 11:52:43 +0200 schrieb Hans Hagen:
As far as I can see the code which does the splitting is in
font-def.lua and so part of the generic code. Is there anything that
can be done to correct his? Or can one somehow protect the colon
Am Sat, 9 Jun 2018 11:52:43 +0200 schrieb Hans Hagen:
>> As far as I can see the code which does the splitting is in
>> font-def.lua and so part of the generic code. Is there anything that
>> can be done to correct his? Or can one somehow protect the colon
>> after c: to be interpretated as
On 6/8/2018 11:51 PM, Ulrike Fischer wrote:
I have been playing around with lua fonts and investigating where to
store and how to load them.
The best with luaotfload and latex seems to be currently to get
(with a kpse call) the absolute path and then load with the "xetex"
syntax:
