From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: font pathes with colons
Date: Sun, 10 Jun 2018 12:58:34 +0200 [thread overview]
Message-ID: <zmjydptaavn8.dlg@nililand.de> (raw)
In-Reply-To: <3f1c7854-8df3-a5aa-12de-90c85a3c6670@xs4all.nl>
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 (conflicts too much)
Ah ok. I'm not really bound to a specific syntax as long as
luaotfload at the end gets the correct data.
The problem is that luaotfload is not really maintained currently,
so it is difficult to improve its handling of lua-fonts. The current
setup has some problems with them:
I tried at first the {file:luafont.lua} syntax, but luaotfload
doesn't look in fonts/misc in this case (which imho is a more
logical place then tex/luatex), and also it constantly triggered the
rebuilding of the database. Absolute pathes found with kpathsea
looked like the way out -- apart from the problem with the colon.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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-10 10:58 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
2018-06-09 21:34 ` Ulrike Fischer
2018-06-10 10:42 ` Hans Hagen
2018-06-10 10:58 ` Ulrike Fischer [this message]
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=zmjydptaavn8.dlg@nililand.de \
--to=news3@nililand.de \
--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).