From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: Re: font pathes with colons
Date: Sat, 9 Jun 2018 11:52:43 +0200 [thread overview]
Message-ID: <07a41b86-c8fe-f984-16bd-9cb27bf0d4e5@xs4all.nl> (raw)
In-Reply-To: <4wpyftzey9rw$.dlg@nililand.de>
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
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-06-09 9:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 21:51 Ulrike Fischer
2018-06-09 9:52 ` Hans Hagen [this message]
2018-06-09 21:34 ` Ulrike Fischer
2018-06-10 10:42 ` Hans Hagen
2018-06-10 10:58 ` Ulrike Fischer
2018-06-10 11:24 ` Hans Hagen
2018-06-11 16:35 ` Ulrike Fischer
2018-06-13 11:55 ` Ulrike Fischer
2018-06-13 13:57 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=07a41b86-c8fe-f984-16bd-9cb27bf0d4e5@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).