From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: for the brave
Date: Tue, 13 Jan 2009 19:08:19 +0100 [thread overview]
Message-ID: <496CD893.403@wxs.nl> (raw)
Hi,
I uploaded beta zip with a prelude to the new structure related code. I
hope that I didn't forget files.
context --make xp
will generate the experimental format (you really need a luatools
--generate because there are many new files).
With
context --interface=xp yourfile
will use that format. Eventually the xp format will go away but this is
a nice intermediate step for those who are willing to help debugging the
code.
Those who look into the source ... it all happens in strc-*.tex|lua and
when you look in the tua/tuc file you see what is carried around (this
will be optimized). Much code still needs a rewrite.
The format file is slightly smaller and less hash space is used, in
spite of more functionality. This is a side effect of a more dynamic
inheritance model (slower, but not so much an issue noaways and
compensated by speedups in other areas like one time multipass data
reading).
For xml users: although somewhat experimental, we now have roundtrip xml
in lists (and some other constructs, more to come).
\setuphead[chapter][expansion=xml]
This only works for mkiv xml, as we also keep track of the document root
in order to apply the right setups.
For Aditya: numbering of math is redone and soon we have to split up
strc-mat into pieces (when we start doing unicode math) but you can
already have a look at it.
Don't worry too much if your documents crash. I simply cannot test
everything so it might be a good opportunity for volunteers to help
documenting behaviour and making tests.
The main incompatibilities are in the numbering: we now use sets for
numbering, seperators, converters etc as well as processors for specific
layout of these thingies. This info is carried around so that
intermediate style changes are reflected in tables of contents and
references (of course they can be overloaded). It's the price we pay fro
more flexibility.
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
___________________________________________________________________________________
next reply other threads:[~2009-01-13 18:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 18:08 Hans Hagen [this message]
2009-01-13 18:26 ` Diego Depaoli
2009-01-13 19:27 ` Hans Hagen
2009-01-13 18:29 ` luigi scarso
2009-01-13 18:39 ` Wolfgang Schuster
2009-01-13 18:53 ` luigi scarso
2009-01-13 19:07 ` Mojca Miklavec
2009-01-13 19:14 ` luigi scarso
2009-01-13 19:03 ` Wolfgang Schuster
2009-01-13 19:26 ` Wolfgang Schuster
2009-01-13 19:38 ` Wolfgang Schuster
2009-01-13 20:46 ` Wolfgang Schuster
2009-01-22 4:03 ` Aditya Mahajan
2009-01-22 13:19 ` Wolfgang Schuster
2009-01-28 2:22 ` Aditya Mahajan
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=496CD893.403@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).