From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Difference between MKII, XeTeX and MKIV
Date: Fri, 18 Mar 2011 11:02:48 +0100 [thread overview]
Message-ID: <4D832DC8.3030609@wxs.nl> (raw)
In-Reply-To: <3A66E444-F747-4661-9D7E-AEFBCDA172B0@pobox.com>
On 18-3-2011 3:54, mathew wrote:
> On Mar 14, 2011, at 16:49, Marco wrote:
>> I totally agree. But Cecil mentioned in another thread: »My document is mostly
>> text.« Even if a few mp graphics are involved luatex is still noticeably
>> slower.
>
> I look at it from the perspective that the last time I used TeX, my 8MHz Atari ST took several seconds to process each page. And then it took several seconds per page for the previewer to show me the DVI. And I couldn't do anything else on the machine while it was working.
>
> My way of working now is that I keep a short scratchpad document in TeXworks, and use it to sort out my formatting and macros, taking advantage of the live preview. When I'm done, I copy the definitions into my actual working document, which I edit in vim. I only typeset the entire working document once or twice an hour, if that; vim catches syntax errors. So if LuaTex takes a few seconds longer to do the typesetting, it's completely unimportant.
it's no problem to get a 250 pages per second throughput in mkiv but as
soon as you add more interesting things to a page work needs to be done
and that takes runtime
on the average i get some 10-15 pages per second for documents of normal
complexity on my (by now) 5 year old laptop that i use for development
which is quite ok (mk.pdf: 10 pps, hybrid.pdf: 11 pps, cld-mkiv: 15 pps)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2011-03-18 10:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 17:22 Cecil Westerhof
2011-03-14 18:13 ` Marco
2011-03-14 18:26 ` Cecil Westerhof
2011-03-14 18:44 ` Marco
2011-03-14 19:31 ` Mojca Miklavec
2011-03-14 21:49 ` Marco
2011-03-18 2:54 ` mathew
2011-03-18 10:02 ` Hans Hagen [this message]
2011-03-14 18:52 ` 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=4D832DC8.3030609@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).