From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: Axel Kielhorn via ntg-context <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Workshop at FrOSCon
Date: Sun, 10 Jul 2022 12:24:40 +0200 [thread overview]
Message-ID: <0dc1eab6-232b-9dab-20f1-3a6d1667d528@xs4all.nl> (raw)
In-Reply-To: <26E6DC6F-A7FC-4CE3-A74F-3D5701C4B444@axelkielhorn.de>
On 7/10/2022 8:36 AM, Axel Kielhorn via ntg-context wrote:
>
>
>> Am 09.07.2022 um 19:27 schrieb Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>:
>>
>> Tell them there will be a German book next year (I hope...); I’ll send you a link off-list.
>
> I’m looking forward to your book.
> In the meantime there is a short guide at:
>
> https://github.com/AKielhorn/Context-Intro
Just for the record: luametatex is *not* optimized for context, it just
provides (rather generic) stuff not present in other engines that we can
benefit from. That said: of course after decades of context we know what
is missing in tex that we could benefit from, and we do. One distinction
between luatex and luametatex is that we delegate some more to lua.
The reworked math engine is something that is probably very contextisch
if only because other macro packages are locked into "chisseled in stone
ams (and alike) math as the only thruthful and accepted by publishers
way to do it" so there the "optimized" sort of applies, in the sense
that we can fully benefit from it as well have extra features that make
certain things possible.
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 / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-07-10 10:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1654768801.20741.ntg-context@ntg.nl>
2022-06-09 11:01 ` a badin via ntg-context
2022-06-21 7:37 ` juh+ntg-context--- via ntg-context
2022-07-09 15:48 ` juh+ntg-context--- via ntg-context
2022-07-09 17:27 ` Henning Hraban Ramm via ntg-context
2022-07-09 17:49 ` Henning Hraban Ramm via ntg-context
2022-07-09 18:13 ` Hans Hagen via ntg-context
2022-07-09 19:16 ` Floris van Manen via ntg-context
2022-07-09 19:30 ` Henning Hraban Ramm via ntg-context
2022-07-09 20:31 ` Hans Hagen via ntg-context
2022-07-10 6:36 ` Axel Kielhorn via ntg-context
2022-07-10 8:22 ` Henning Hraban Ramm via ntg-context
2022-07-10 14:43 ` Axel Kielhorn via ntg-context
2022-07-10 14:56 ` Henning Hraban Ramm via ntg-context
2022-07-10 15:02 ` Axel Kielhorn via ntg-context
2022-07-10 10:24 ` Hans Hagen via ntg-context [this message]
2022-06-08 5:18 juh via ntg-context
2022-06-08 5:43 ` Henning Hraban Ramm via ntg-context
2022-06-08 13:17 ` juh+ntg-context--- via ntg-context
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=0dc1eab6-232b-9dab-20f1-3a6d1667d528@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).