From: Hans Hagen <pragma@wxs.nl>
To: ulfmartin@web.de, mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: ConTeXt versioning model critique
Date: Sat, 14 Apr 2007 22:47:56 +0200 [thread overview]
Message-ID: <46213DFC.6000903@wxs.nl> (raw)
In-Reply-To: <4620ED5C.2000003@web.de>
Ulf Martin wrote:
> I wonder how people (esp. at Pragma) currently deal with this. What
> happens if you have a ConTeXt doc from say 1997 that compiles into the
> resp. PDF with some ConTeXt version from that time but not today
> anymore? Which ConTeXt versions does one have to keep in order to be
> able to use such a document? (A good example for this kind of trouble
> seem to be the current issues with XeTeX, but I haven't followed this in
> detail -- but it kept me away from updating my ConTeXt installation
> since December...).
>
for projects where we use relatively new features (which evolve) we use
frozen trees; actually some of this code is not even documented (simply
no time; take synchronized graphics)
with regards to commands and such ... context is just (supposed to be)
downward compatible; even kind of obsolete is still there; with regards
to different solutions to problems, we often provide control usign low
level mode indicators
concerning xetex ... keep in mind that there xetex is the moving target
(changes/extensions in interface) and to some extend this was true for
pdftex as well, but there we could silently adapt
> Also remember that Knuth originally intended TeX to be an "eternal"
> formatting system (thus we have at least the option to expand all macros
> into plain TeX and keep that as the source file).
>
plain tex is just a format and unsuitable as expanded format
well, i have some experimental code that dumps the expanded token list
into a file; nu fun ... a 50 page moderately complex doc becomes some 25
meg -)
but then, if the sole reason is to reprocess the doc ... just save the
pdf file -)
> This raises another question: is ConTeXt developed in an test driven
> way? I.e. are there test documents (including e.g. XML documents,
> bibligraphic references etc.) that have to pass comilation in order for
> changes to be published? If so, they would probably define a standard
> set of commands that could go into The ConTeXt Companion.
>
>
Sanjoy has set up an advanced test system ... so anything that you
contribute can go in there
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2007-04-14 20:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1176544802.32527.ntg-context@ntg.nl>
2007-04-14 11:29 ` Vyatcheslav Yatskovsky
2007-04-14 15:03 ` Ulf Martin
2007-04-14 20:47 ` Hans Hagen [this message]
2007-04-14 21:19 ` luigi scarso
2007-04-20 12:31 ` fdu.xiaojf
2007-04-20 13:17 ` Taco Hoekwater
2007-04-23 1:15 ` fdu.xiaojf
2007-04-20 20:57 ` Hans Hagen
2007-04-20 21:42 ` Table of contents and 2UP or 2SIDE Horacio Suarez
2007-04-21 6:23 ` Hans Hagen
2007-04-14 12:28 ` Some progress with XeTeX Vyatcheslav Yatskovsky
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=46213DFC.6000903@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=ulfmartin@web.de \
/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).