ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: Re: using lua fonts
Date: Wed, 9 May 2018 13:05:34 +0200	[thread overview]
Message-ID: <e4c5d65f-04b0-750a-3e99-7aadd41d18bf@xs4all.nl> (raw)
In-Reply-To: <es1ee4hrx6b4.dlg@nililand.de>

On 5/9/2018 12:40 PM, Ulrike Fischer wrote:
> 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.

normally function that are part of the generic loader code are publis 
(one can argue about the low level helpers as these are only loaded for 
the code to work i.e. i have no clue how useful these are outside 
context) .. that code doesn't change that much nowadays (just assume 
that i also use it in modules sometimes and i don't want to change that 
too often)

then there is the wrapper code (that hooks into callbacks) which is also 
mostly stable (unless we add something fundamental)

for instance, the effects feature has a sort of sub syntax that suits 
context feature definitions, so for latex you probably need to map onto 
that somehow ... i happily leave that to others to figure out as i don't 
want to impose something (the same is true for variable fonts)

the big font manual is a context one so there can be examples that 
assume the context user interface and there is not much we can do about 
that (and i don't know much about latex apart from what i occasionally 
see at some tex meeting) ... wrrt the font loader: the luatex-plain 
version is sort of the generic reference ... anything written on top of 
that is specific for a macro package

another difference is the font database ... i'm pretty sure that the 
context one is quite generic but latex folks wanted their own so ...

> 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?

anyway, if something doesn't work at some point we can always see why 
and provide a compatibility hack in luatex-fonts-hacks or so

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
___________________________________________________________________________________

      reply	other threads:[~2018-05-09 11:05 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
2018-05-09 11:05       ` Hans Hagen [this message]

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=e4c5d65f-04b0-750a-3e99-7aadd41d18bf@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).