ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: Serious bug?
Date: Wed, 24 Dec 2008 11:29:32 +0100	[thread overview]
Message-ID: <6faad9f00812240229w2a374c0frc0fb0c0290aeb699@mail.gmail.com> (raw)
In-Reply-To: <COL106-DS4E42FC5EEC6910388A2F0A4ED0@phx.gbl>

On Wed, Dec 24, 2008 at 3:45 AM, Fengnan Gao <fnsteed@hotmail.com> wrote:
> Hi, all
>
> Can I roll back and use the old version when context isn't broken? I have
> several documents which need to be processed ASAP. Thanks.

Hello Fengan,

you need both an older version of luatex and an older version of ConTeXt.

Suggestion 1:
You can download mswincontext.zip from PRAGMA, though that one dates
months back. If that is not an issue, you can use that one.

Suggestion 2:
Change first-setup.bat, so that --context=beta switch will read
--context=2008.10.31 and run first-setup.bat again. This will give you
the version of ConTeXt that's still OK, but the same broken LuaTeX, so
you need to download some older version of luatex binary from
http://foundry.supelec.fr/projects/luatex (0.30.3 should be fine).

You need to delete the contents of texmf-cache and regenerate formats.

I would like to fix this, but I don't know how. One option is to
revert both ConTeXt and LuaTeX to an older version. A much better
thing would be to fix font-otf.lua. Hans? Taco?

Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-12-24 10:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-21  7:19 Fengnan Gao
2008-12-21 11:08 ` Yue Wang
2008-12-22 19:24 ` Alan STONE
2008-12-23 12:32   ` Taco Hoekwater
2008-12-23 18:30     ` Taco Hoekwater
2008-12-24  2:45       ` Fengnan Gao
2008-12-24 10:29         ` Mojca Miklavec [this message]
2008-12-24 13:49         ` Alan STONE
2008-12-22 23:05 ` Mojca Miklavec
2008-12-23 12:31   ` Taco Hoekwater
2008-12-24 10:03     ` Taco Hoekwater
2008-12-24 12:54       ` Alan STONE
2008-12-24 13:21         ` Taco Hoekwater
2008-12-24 16:32           ` Alan STONE
2008-12-26  8:40       ` Taco Hoekwater
2008-12-23 15:21 ` Derek CORDEIRO
2008-12-23 15:28   ` Derek CORDEIRO
2008-12-21 12:58 Fengnan Gao
2008-12-21 14:18 ` Yue Wang
2008-12-21 14:28   ` Fengnan Gao
2008-12-22  1:53   ` Fengnan Gao
2008-12-22  7:26     ` Mojca Miklavec
2008-12-22  7:35       ` Mojca Miklavec
2008-12-21 14:26 ` Hans Hagen
2008-12-21 20:52 ` Mojca Miklavec
2008-12-22  9:58   ` Taco Hoekwater
2008-12-21 14:36 Fengnan Gao
2008-12-22 12:56 Fengnan Gao
2008-12-22 16:04 ` Mojca Miklavec
2008-12-23 18:22   ` Taco Hoekwater
2008-12-24 13:27     ` Alan STONE
2008-12-22 17:55 ` Taco Hoekwater
2008-12-22 18:25   ` Taco Hoekwater
2008-12-22 18:57 Tad Ashlock

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=6faad9f00812240229w2a374c0frc0fb0c0290aeb699@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).