From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: using lua fonts
Date: Wed, 9 May 2018 12:40:19 +0200 [thread overview]
Message-ID: <es1ee4hrx6b4.dlg@nililand.de> (raw)
In-Reply-To: <c0df870e-9779-1555-2190-14d7b087b0fd@xs4all.nl>
Am Wed, 9 May 2018 09:56:50 +0200 schrieb Hans Hagen:
> watch how i replaced the * by : because only context has the * syntax
Thank you very much for this explanation. I was wondering about the
same thing and replacing this made the code going.
Perhaps a general remark: I and certainly Henry too are quite aware
that some of the code is context specific. But it is often quite
difficult to see the boundaries -- which part of the examples are
generic and which rely on context (and on how much in context). It
is also not easy to decide which (lua) functions are "public" and
won't break at the next update of the font handler.
Henri: As you are interested in these things too, do you think it
would be a good idea to setup a github repository where we collect
such (plain and latex and context) examples?
--
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-05-09 10:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 18:26 Ulrike Fischer
2018-05-08 8:43 ` Hans Hagen
2018-05-08 14:01 ` Ulrike Fischer
2018-05-08 14:17 ` Hans Hagen
2018-05-08 14:46 ` Ulrike Fischer
2018-05-09 1:02 ` Henri Menke
2018-05-09 7:56 ` Hans Hagen
2018-05-09 10:40 ` Ulrike Fischer [this message]
2018-05-09 11:05 ` 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=es1ee4hrx6b4.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).