From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: last beta this year
Date: Tue, 31 Dec 2019 11:50:43 +0100 [thread overview]
Message-ID: <56eb34e3-7f9f-fff4-d25c-29cf66fee7c1@xs4all.nl> (raw)
Hi,
I uploaded the last beta for this years so we will leave all old bugs
behind us. Here's a bit of agenda:
- mkiv will use luatex so as part of the upcoming tl code freeze that
needs the usual testing;
- next year i suppose that lmtx will be used by the majority of users
- we need to (read mojca and i will do that when we're in the mood)
adapt the garden infrastructure for installing lmtx; part of that is
also the context repository
- we have to think about how to deal with the extra modules as part of
that (basics are already there)
- idris, mohammad, wolfgang and i are trying to make right-to-left
handling of layout related items more complete and consistent, expect
more next year
- i expect to do some more luametafun stuff, maybe some cleanup of old
code, maybe a bitmore split between old mkiv and new lmtx
- i also want to do some pending font trickery, probably lmtx only
- wolfgang (he doesn't know that yet) and i (and maybe some others) are
going to think about some lightweight protection of core macros (using
some new lmtx features) .. i'm curious to know if and how frequently
users are bitten by accidental redefinitions
- aditya (he knows) has to pick up on some pending math issues so math
will get better too
- thomas (he also knows as he needs it) and i are looking into some
tricky layout things related to synchronizing content
- i want to see if the installation can be more automatic (as we
basically need a real minimalistic copy-end-run approach in for instance
texlive for lmtx)
- i need to move some pending stuff into all kind of manuals (but will
probably forget about it unless i run into new cd's to keep me occupied
while doing it)
- there will be a ctx meeting in czech (at the place we've been before)
- in addition, next year will see the wiki being improved, something
Taco and Pavneet and others are / have been working on; feel free to
contribute to that effort!
So, upto next year,
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
___________________________________________________________________________________
next reply other threads:[~2019-12-31 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-31 10:50 Hans Hagen [this message]
2019-12-31 12:52 ` Floris van Manen
2019-12-31 21:03 ` kaddour kardio
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=56eb34e3-7f9f-fff4-d25c-29cf66fee7c1@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).