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: Re: Difference between MKII, XeTeX and MKIV
Date: Mon, 14 Mar 2011 19:52:20 +0100	[thread overview]
Message-ID: <4D7E63E4.4060706@wxs.nl> (raw)
In-Reply-To: <AANLkTikFDAOvH+N3wAoG2NfAVWTg58kGYHGSHxWE=uRN@mail.gmail.com>

On 14-3-2011 7:26, Cecil Westerhof wrote:
> 2011/3/14 Marco<netuse@lavabit.com>
>
>> On 2011-03-14 Cecil Westerhof<cldwesterhof@gmail.com>  wrote:
>>
>>> When installing minimals you have MKII, XeTeX and MKIV. I understand that
>>> you should normally use MKIV, but when are the other two used?
>>
>> MKII can be used either with pdftex or xetex (as you wish, compare
>> advantages/disadvantages). MKIV can only be used with luatex.
>>
>> You have to differ between ConTeXt »versions« (mkii, mkiv) and TeX backends
>> (pdftex, xetex, luatex).
>>
>
> And where do I find the advantages/disadvantages? Or can I just always use
> MKIV?

As already mentioned speed depends on the kind of document. In general 
context runs slower with xetex and luatex if only because these are 
unicode engines while pdftex is 8 bit.

Occasionally i do speed tests and it also depends on the operating 
system, file caching etc. For luatex the size of the cpu cache also 
matters. Although pdftex/mkiv is always faster unless on eused metapoist 
in which case mkiv is a clear winner (the metafun manual runs in tens of 
seconds in mkiv but takes many minutes in mkii.  Comparing xetex/mkii 
and luatex/mkiv is difficult as xetex also pipes its output to a dvi 
backend. On some tests mkiv is faster, on some others mkii but I must 
admit that i only tested simple document.

On a raw simple document, pdftex can be twice as fast as xetex or 
luatex. The more lua driven features are used, the slower mkiv becomes 
but in general it does a better job then.

Anyhow .. only luatex/mkiv will evolve so best stick to that.

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
___________________________________________________________________________________


      parent reply	other threads:[~2011-03-14 18:52 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
2011-03-14 18:52     ` Hans Hagen [this message]

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=4D7E63E4.4060706@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).