From: Floris van Manen <vm@klankschap.nl>
To: Wolfgang Schuster <wolfgang.schuster.lists@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [ibmplex setup script]
Date: Sun, 3 May 2020 11:24:07 +0200 [thread overview]
Message-ID: <1d5ce7bc-7937-9eab-5040-e713d9d64e7d@klankschap.nl> (raw)
In-Reply-To: <ab4c72f6-1edd-a665-f562-0fdaaada9bd6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Thank you Wolfgang!
Your example works as intended.
I really get lost in the font definition files, as it is difficult to
understand which variable point to what other definition.
Is there a (simple) picture where the scripts are annotated with arrows,
to know which variable points to where? All the way back to the
mtxrun --script fonts --list --all --pattern=*
reply?
With all the options available it is a steep learning curve, but i hope
to be able to understand it at some point.
Thanks for the working solution.
.Floris
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2456 bytes --]
[-- Attachment #3: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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:[~2020-05-03 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 22:20 Floris van Manen
2020-05-03 8:49 ` Wolfgang Schuster
2020-05-03 9:24 ` Floris van Manen [this message]
2020-05-03 11:36 ` Floris van Manen
2020-05-03 15:20 ` Henning Hraban Ramm
2020-05-03 16:24 ` Floris van Manen
2020-05-03 17:01 ` Wolfgang Schuster
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=1d5ce7bc-7937-9eab-5040-e713d9d64e7d@klankschap.nl \
--to=vm@klankschap.nl \
--cc=ntg-context@ntg.nl \
--cc=wolfgang.schuster.lists@gmail.com \
/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).