From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: future versions
Date: Wed, 25 Jul 2018 22:22:13 +0200 [thread overview]
Message-ID: <582588B2-1597-40B6-83A0-6BF956E01DC1@fiee.net> (raw)
In-Reply-To: <975c5665-107d-45b6-40aa-32eeb981094b@xs4all.nl>
Am 2018-07-25 um 19:50 schrieb Hans Hagen <j.hagen@xs4all.nl>:
>> In any case, I would very much appreciate another “frozen” release like MK II that one can use for documents that need to be retypeset over years
>> (like my lecture notes that need an update every few years).
>
> When we have luatex 1.10 that will be easier because older code can run on a newer engine then.
>
> But even then, if we make snapshots that can be downloaded for a long time, we need some way to recognize them (by year?).
LilyPond (as a somewhat similar program) requires a version statement in every source file; and then there’s a converter script that understands and updates all constructs that are part of the official syntax - of course, if you use custom scripting (Scheme in this case), you are on your own again.
Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD
___________________________________________________________________________________
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-07-25 20:22 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-24 18:43 Hans Hagen
2018-07-24 19:07 ` Hans van der Meer
2018-07-24 20:35 ` Pablo Rodriguez
2018-07-24 20:30 ` Pablo Rodriguez
2018-07-24 21:02 ` Idris Samawi Hamid ادريس سماوي حامد
2018-07-24 23:21 ` Hans Hagen
2018-08-21 8:00 ` future versions - synctex Procházka Lukáš Ing.
2018-08-21 8:33 ` Hans Hagen
2018-08-21 13:04 ` Aditya Mahajan
2018-08-21 13:19 ` Hans Hagen
2018-08-21 14:46 ` Aditya Mahajan
2018-08-21 15:17 ` Hans Hagen
2018-07-25 1:29 ` future versions Rik Kabel
2018-07-25 8:19 ` Henning Hraban Ramm
2018-07-25 13:50 ` Rik Kabel
2018-07-25 16:06 ` Hans Hagen
2018-07-25 16:18 ` Alan Braslau
2018-07-25 17:01 ` Hans Hagen
2018-07-25 11:36 ` Hans Hagen
2018-07-25 7:45 ` Robert Zydenbos
2018-07-25 10:03 ` Richard Mahoney | Indica et Buddhica
2018-07-25 12:50 ` Hans Hagen
2018-07-25 13:12 ` Weber, Matthias
2018-07-25 17:50 ` Hans Hagen
2018-07-25 20:22 ` Henning Hraban Ramm [this message]
2018-07-25 11:38 ` 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=582588B2-1597-40B6-83A0-6BF956E01DC1@fiee.net \
--to=texml@fiee.net \
--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).