ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: mkiv goes beta
Date: Mon, 06 Aug 2007 12:52:32 +0200	[thread overview]
Message-ID: <46B6FD70.8040603@wxs.nl> (raw)

Hi,

ConTeXt MKiV goes beta.

Now, why today, 06/08/07? It happens to be the birthday of one of the 
most demanding users on this list and when at bachotek 2007 we discussed 
the moment of going beta Arthur suggested that this would be the perfect 
day. I could not agree more, especially because Mojca is one of the most 
demanding and testing users and eagerly awaiting new things.

	So, Mojca, here's your birthday present!

It's part of a package from Taco, Arthur, Patrick and me ..

- of course there is the luaTeX binary, even better than the beta (be
   patient with taco in fixing bugs)
- then there is a new wiki page (cleverly hidden till today, you don't
   want to know what tricks arthur used to get it all running well)
- of course you can now also try luaTeX/MkIV on the wiki running page
   (don't complain too much to patrick about performance)
- and yes, you need the latest ConTeXt zip as well (i cross my fingers
   that it works ok)

On the website there is the usual zip, but also a new magazine, one that 
tells how to install luaTeX:

	http://www.pragma-ade.com/general/magazines/mag-0012.pdf

When I was preparing this release I had "Major Impacts 2" and "Split 
Decision" (by Steve Morse) running in loop-mode on the sqeezebox. I 
realize that LuaTeX will have a major impact on ConTeXt, as has the 
decision to split into MkII and MkIV. The experiences of many years of 
user demand and usage will be reflected in upcoming releases. The 
challenge will be to get the mosy ou tof all engines.

A few extra notes:

- typescripts are reorganized so that in luaTeX open type fonts
   are used instead, by default some features are enabled
- using type one fonts is possible (no encoding needed), but the
   backend needs a fix to support wide fonts, Taco is working on this
- typesetting arab and such is possible, more on this later on
   this list; scripts like chinese is work in progress
- there is much experimental, unused code, but expect to see more
   of it coming into action the next months
- make sure to install lua itself because 'luac' is needed to
   bytecompile cached data (much faster)
- make sure to set the TEXMFCACHE environment variable as well as
   TEXMFCNF and TEXMF; caching is really needed and because we no
   longer use kpse MkIV needs to know what tree to use

I uploaded the lot, minimals included. Expect more frequent uploades 
since I'm not sure if thinks work for all platforms. Also, be prepared 
to keep your own binaries uptodate.

And ... from now on xetex users should use the official 
\definefontfeature interface as well.

Happy testing ...

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
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2007-08-06 10:52 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 10:52 Hans Hagen [this message]
2007-08-06 11:40 ` Steffen Wolfrum
2007-08-06 11:54 ` luigi scarso
2007-08-06 14:13 ` Peter Rolf
2007-08-06 14:25   ` Thomas A. Schmitz
2007-08-06 14:42     ` Arthur Reutenauer
2007-08-06 17:03       ` Taco Hoekwater
2007-08-06 17:06         ` Hans Hagen
2007-08-06 18:32         ` Arthur Reutenauer
2007-08-06 18:43           ` Hans Hagen
2007-08-06 19:10             ` Thomas A. Schmitz
2007-08-06 21:46               ` Taco Hoekwater
2007-08-07 13:25                 ` Thomas A. Schmitz
2007-08-07 13:37                   ` Taco Hoekwater
2007-08-07 17:19                     ` Thomas A. Schmitz
     [not found]             ` <20070806190351.GJ26634@phare.normalesup.org>
2007-08-06 19:26               ` Hans Hagen
2007-08-06 19:46                 ` Arthur Reutenauer
2007-08-06 20:08                   ` Hans Hagen
2007-08-06 23:55                     ` Arthur Reutenauer
2007-08-07  7:28                       ` Hans Hagen
2007-08-06 20:09                   ` Hans Hagen
2007-08-07  2:44       ` Arthur Reutenauer
2007-08-06 17:56 ` luigi scarso
2007-08-06 18:06   ` Arthur Reutenauer
2007-08-06 18:50     ` luigi scarso
2007-08-06 21:50       ` Taco Hoekwater
2007-08-06 22:07         ` luigi scarso
2007-08-06 20:38 ` luigi scarso
2007-08-06 20:42 ` Peter Rolf
2007-08-07  7:25   ` Hans Hagen
2007-08-07 14:04     ` Peter Rolf
2007-08-07 14:24       ` Arthur Reutenauer
2007-08-07 15:08         ` Peter Rolf
2007-08-06 23:18 ` luigi scarso
2007-08-07  7:39   ` Taco Hoekwater
2007-08-08  7:40   ` Taco Hoekwater

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=46B6FD70.8040603@wxs.nl \
    --to=pragma@wxs.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).