From: Steffen Wolfrum <context@st.estfiles.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: backward compatibility [URGENT]
Date: Thu, 6 Dec 2007 21:06:39 +0100 [thread overview]
Message-ID: <6BD7AE23-A8FC-4654-8E40-C6D2D7E022F4@st.estfiles.de> (raw)
In-Reply-To: <475832D1.5050101@wxs.nl>
Am 06.12.2007 um 18:35 schrieb Hans Hagen:
> Steffen Wolfrum wrote:
>> Hi,
>>
>> re-typesetting a book (that was last set with ConTeXt ver:
>> 2007.08.09) I had to see that several pages now have a different
>> line-
>> break (and so the page-break and the TOC and the index register are
>> changed) ... quite a mess.
>>
>> I guess is not so easy to find out what changes in the ConTeXt source
>> result in these changes now.
>> So to continue work it will be probably better to downgrade again my
>> ConTeXt.
>>
>> Is there an easy way to do this, like using sudo ctxtools --
>> updatecontext and use the respective files from the museum?
>
> hm, not that much was changed in toc/register code, so maybe you can
> diff and see what happened; we're talking mkii i presume
only, what should I diff?? my project's files haven't changed (just
used the old ones again).
and the tex/context source files were updated and thus overwritten.
isn't there a way to point the command ...
sudo ctxtools --updatecontext
... to the respective (2007.08.09) files in the museum and downgrade
my system again?
Steffen
___________________________________________________________________________________
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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2007-12-06 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 17:31 Steffen Wolfrum
2007-12-06 17:35 ` Hans Hagen
2007-12-06 20:06 ` Steffen Wolfrum [this message]
2007-12-07 8:50 ` Steffen Wolfrum
[not found] ` <47590D11.4090800@wxs.nl>
[not found] ` <2F0ABBD5-2A3A-42FA-BAA2-BA027265EA7C@st.estfiles.de>
2007-12-07 9:36 ` Hans Hagen
2007-12-07 10:04 ` Steffen Wolfrum
2007-12-07 10:25 ` [found it!] backward compatibility Steffen Wolfrum
2007-12-07 10:46 ` Wolfgang Schuster
2007-12-07 11:43 ` Steffen Wolfrum
2007-12-07 12:21 ` Taco Hoekwater
2007-12-06 17:53 ` backward compatibility [URGENT] Idris Samawi Hamid
2007-12-06 17:57 ` Taco Hoekwater
2007-12-06 19:58 ` Aditya Mahajan
2007-12-07 9:10 ` 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=6BD7AE23-A8FC-4654-8E40-C6D2D7E022F4@st.estfiles.de \
--to=context@st.estfiles.de \
--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).