[NTG-context] font pathes with colons

Hans Hagen j.hagen at xs4all.nl
Sat Jun 9 11:52:43 CEST 2018


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:
> 
> \font\duckchessfont =
>    [\directlua{tex.sprint(kpse.find_file("luafont-duckchess.lua",
>    "misc fonts"))}]:mode=node;+liga;+tlig;original=latinmodernsans
> 
> 
> This worked but I also saw in the log curious messages
> 
> luaotfload | load : font option
> "/Users/XXXX/Documents/Git/lua-font-
> pond/texmf/fonts/misc/luafont/luafont-duckchess.lua]:mode=node"
> unknown.
> 
> I investigated a bit. I'm on windows and imho this looks as if the
> syntax parser is splitting after the C: of the drive and putting the
> rest in the specification.detail field.
> 
> 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 file-detail separator?
i can support {weird name} but need to check first if it will not 
interfere with context (or luatex-plain)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------


More information about the ntg-context mailing list