Tomi Lindberg wrote:
texexec seems to fill pages better while context at times leaves a lot of air at the end of page if in middle of a list.
texexec adds a \stoptext cq \end to the input line (that specifies the main file) so this hides an error; in mkiv i no longer do that ... files should be just ok
Indexes are definately in favor of texexec. context fails to order 'ä' and 'ö' correctly - it just thinks they're 'a' and 'o' while texexec works as it should. Also context doesn't add 'titles' for letters. And finally there's a weird 'unknown' entry at the start of context index.
depends ... i assume you're talking mkiv here? we need to add more languages to it (sorting vectors) and of course there can be bugs in the code
texexec makes an extra empty page at the end of document while context doesn't. Compared to the above this seems a minor gain though.
unrelated to texexec/context ... texexec is just a ruby script that runs tex for you; it's marks being reset that can add a node to the end of the document (depends a bit on the style) while luatex has a clearmarks primitive that we use and which has no side effects (unfortunately clearmarks was never added to etex) ----------------------------------------------------------------- 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 -----------------------------------------------------------------