From mboxrd@z Thu Jan  1 00:00:00 1970
X-Msuck: nntp://news.gmane.io/gmane.comp.tex.context/109095
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Rik Kabel <ConTeXt@rik.users.panix.com>
Newsgroups: gmane.comp.tex.context
Subject: Re: Which version of MkIV should we use?
Date: Mon, 26 Oct 2020 08:05:15 -0400
Message-ID: <659f37d4-c130-4ea3-843d-a8df45d272ab@rik.users.panix.com>
References: <d60cb74b-f45d-c1e9-c120-39a88b898e80@rik.users.panix.com>
 <4193ed55-5343-c49a-b6ec-1ded8fbb3310@xs4all.nl>
Reply-To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="===============7668861791874320127=="
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="27027"; mail-complaints-to="usenet@ciao.gmane.io"
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Firefox/68.0 Thunderbird/68.12.1
To: Hans Hagen <j.hagen@xs4all.nl>,
 mailing list for ConTeXt users <ntg-context@ntg.nl>
Original-X-From: ntg-context-bounces@ntg.nl Mon Oct 26 13:06:10 2020
Return-path: <ntg-context-bounces@ntg.nl>
Envelope-to: gctc-ntg-context-518@m.gmane-mx.org
Original-Received: from zapf.boekplan.nl ([5.39.185.232] helo=zapf.ntg.nl)
	by ciao.gmane.io with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <ntg-context-bounces@ntg.nl>)
	id 1kX1GM-0006se-3C
	for gctc-ntg-context-518@m.gmane-mx.org; Mon, 26 Oct 2020 13:06:10 +0100
Original-Received: from localhost (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id C3D391A993D;
	Mon, 26 Oct 2020 13:05:25 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
	by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 5TLBmv1Ox7wF; Mon, 26 Oct 2020 13:05:21 +0100 (CET)
Original-Received: from zapf.ntg.nl (localhost [127.0.0.1])
	by zapf.ntg.nl (Postfix) with ESMTP id 093341A993E;
	Mon, 26 Oct 2020 13:05:21 +0100 (CET)
Original-Received: from localhost (localhost [127.0.0.1])
 by zapf.ntg.nl (Postfix) with ESMTP id 38A631A993C
 for <ntg-context@ntg.nl>; Mon, 26 Oct 2020 13:05:20 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at zapf.boekplan.nl
Original-Received: from zapf.ntg.nl ([127.0.0.1])
 by localhost (zapf.ntg.nl [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id MnHPtap_8ASw for <ntg-context@ntg.nl>;
 Mon, 26 Oct 2020 13:05:19 +0100 (CET)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=166.84.1.89;
 helo=mailbackend.panix.com; envelope-from=context@rik.users.panix.com;
 receiver=<UNKNOWN> 
Original-Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
 (No client certificate requested)
 by zapf.ntg.nl (Postfix) with ESMTPS id 10E581A9936
 for <ntg-context@ntg.nl>; Mon, 26 Oct 2020 13:05:18 +0100 (CET)
Original-Received: from [192.168.0.6] (cpe-24-194-26-93.nycap.res.rr.com [24.194.26.93])
 by mailbackend.panix.com (Postfix) with ESMTPSA id 4CKYSD6QKgz14J5;
 Mon, 26 Oct 2020 08:05:16 -0400 (EDT)
In-Reply-To: <4193ed55-5343-c49a-b6ec-1ded8fbb3310@xs4all.nl>
Content-Language: en-US
X-BeenThere: ntg-context@ntg.nl
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: mailing list for ConTeXt users <ntg-context.ntg.nl>
List-Unsubscribe: <https://mailman.ntg.nl/mailman/options/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=unsubscribe>
List-Archive: <http://mailman.ntg.nl/pipermail/ntg-context/>
List-Post: <mailto:ntg-context@ntg.nl>
List-Help: <mailto:ntg-context-request@ntg.nl?subject=help>
List-Subscribe: <https://mailman.ntg.nl/mailman/listinfo/ntg-context>,
 <mailto:ntg-context-request@ntg.nl?subject=subscribe>
Errors-To: ntg-context-bounces@ntg.nl
Original-Sender: "ntg-context" <ntg-context-bounces@ntg.nl>
Xref: news.gmane.io gmane.comp.tex.context:109095
Archived-At: <http://permalink.gmane.org/gmane.comp.tex.context/109095>

This is a multi-part message in MIME format.
--===============7668861791874320127==
Content-Type: multipart/alternative;
 boundary="------------36E5CFF1E4B96A0BA354585C"
Content-Language: en-US

This is a multi-part message in MIME format.
--------------36E5CFF1E4B96A0BA354585C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

On 10/26/2020 04:37, Hans Hagen wrote:
> On 10/26/2020 12:09 AM, Rik Kabel wrote:
>> Hello all,
>>
>> I have noticed some differences between the MkIV installed as part of 
>> LMTX and the MkIV installed via first-setup.
>>
>> Which should be used going forward when one wants to use MkIV?
>>
>> (One difference: \contextkind is defined in file context.mkiv 
>> installed via first-setup. It is not defined in the file of the same 
>> name installed as part of LMTX. Another, more significant difference, 
>> is loading modules.)
>
> mkiv works with luatex, lmtx needs luametatex
>
> currently the functionality is mostly the same but further development 
> happens in lmtx
>
> so, if mkiv works for you, just keep using it .. you can try your 
> document with lmtx and normally that should work ok
>
> there is a distinction between
>
> - core functionality (seldom changes)
> - tricky things (migh tbe done better in lmtx)
> - more radical new things hard to do in regular tex (will be in lmtx 
> only)
>
> the luametatex engine is more advanced than luatex (which we cannot 
> change any more in fundamental ways as it's also used outside context) 
> but with luametatex we can do (maybe) crazy things; the luametatex 
> enfine has all kind of improvements in the rendening, adds 
> functionality that makes implementations somewhat cleaner, is faster 
> and uses less memory, redesigns/organizes some internals (e.g. get rid 
> of the sometimes fuzzy accumulated engine mix), adds more interfaces 
> in lua, is self contained, etc ... see presentation(s) last ctx meeting.
>
> currently i'm applying some of the more drastic new thing: more 
> advance macro argument parsing options, several levels of (macro) 
> protection, etc which actually might lead to issues (simple to deal 
> with as most are interface related, not functionality)
>
> so ... you can use mkiv and/or snapshot the current lmtx and/or try 
> the latest greatest when it showsup
>
> Hans
>
> -----------------------------------------------------------------
>                                           Hans Hagen | PRAGMA ADE
>               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
>        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
> -----------------------------------------------------------------

Hans,

Let me rephrase the question.

With the following example:

    \starttext

    \contextkind

    \stoptext

The standalone installation returns a document containing "beta" and 
context --luatex with the LMTX installation complains of an undefined 
control sequence.

The file context.mkiv differs between the two installations.

If the two are expected to differ, I am asking which is the reliable 
version.

You had stated in an earlier email that the --luatex option provided to 
an LMTX installation will produce an MkIV result, but that does not seem 
to still be the case.

-- 
Rik


--------------36E5CFF1E4B96A0BA354585C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    On 10/26/2020 04:37, Hans Hagen wrote:<br>
    <blockquote type="cite"
      cite="mid:4193ed55-5343-c49a-b6ec-1ded8fbb3310@xs4all.nl">On
      10/26/2020 12:09 AM, Rik Kabel wrote:
      <br>
      <blockquote type="cite">Hello all,
        <br>
        <br>
        I have noticed some differences between the MkIV installed as
        part of LMTX and the MkIV installed via first-setup.
        <br>
        <br>
        Which should be used going forward when one wants to use MkIV?
        <br>
        <br>
        (One difference: \contextkind is defined in file context.mkiv
        installed via first-setup. It is not defined in the file of the
        same name installed as part of LMTX. Another, more significant
        difference, is loading modules.)
        <br>
      </blockquote>
      <br>
      mkiv works with luatex, lmtx needs luametatex
      <br>
      <br>
      currently the functionality is mostly the same but further
      development happens in lmtx
      <br>
      <br>
      so, if mkiv works for you, just keep using it .. you can try your
      document with lmtx and normally that should work ok
      <br>
      <br>
      there is a distinction between
      <br>
      <br>
      - core functionality (seldom changes)
      <br>
      - tricky things (migh tbe done better in lmtx)
      <br>
      - more radical new things hard to do in regular tex (will be in
      lmtx only)
      <br>
      <br>
      the luametatex engine is more advanced than luatex (which we
      cannot change any more in fundamental ways as it's also used
      outside context) but with luametatex we can do (maybe) crazy
      things; the luametatex enfine has all kind of improvements in the
      rendening, adds functionality that makes implementations somewhat
      cleaner, is faster and uses less memory, redesigns/organizes some
      internals (e.g. get rid of the sometimes fuzzy accumulated engine
      mix), adds more interfaces in lua, is self contained, etc ... see
      presentation(s) last ctx meeting.
      <br>
      <br>
      currently i'm applying some of the more drastic new thing: more
      advance macro argument parsing options, several levels of (macro)
      protection, etc which actually might lead to issues (simple to
      deal with as most are interface related, not functionality)
      <br>
      <br>
      so ... you can use mkiv and/or snapshot the current lmtx and/or
      try the latest greatest when it showsup
      <br>
      <br>
      Hans
      <br>
      <br>
      -----------------------------------------------------------------
      <br>
                                                Hans Hagen | PRAGMA ADE
      <br>
                    Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      <br>
             tel: 038 477 53 69 | <a class="moz-txt-link-abbreviated" href="http://www.pragma-ade.nl">www.pragma-ade.nl</a> | <a class="moz-txt-link-abbreviated" href="http://www.pragma-pod.nl">www.pragma-pod.nl</a>
      <br>
      -----------------------------------------------------------------
      <br>
    </blockquote>
    <br>
    <p>Hans,</p>
    <p>Let me rephrase the question.</p>
    <p>With the following example:</p>
    <blockquote>
      <p><tt>\starttext</tt></p>
      <p><tt>\contextkind</tt></p>
      <p><tt>\stoptext</tt><br>
      </p>
    </blockquote>
    <p>The standalone installation returns a document containing "beta"
      and <tt>context --luatex</tt> with the LMTX installation
      complains of an undefined control sequence.<br>
    </p>
    <p>The file context.mkiv differs between the two installations.</p>
    <p>If the two are expected to differ, I am asking which is the
      reliable version.</p>
    <p>You had stated in an earlier email that the --luatex option
      provided to an LMTX installation will produce an MkIV result, but
      that does not seem to still be the case.</p>
    <p>-- <br>
      Rik</p>
  </body>
</html>

--------------36E5CFF1E4B96A0BA354585C--

--===============7668861791874320127==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18KSWYgeW91ciBxdWVzdGlvbiBpcyBvZiBpbnRlcmVz
dCB0byBvdGhlcnMgYXMgd2VsbCwgcGxlYXNlIGFkZCBhbiBlbnRyeSB0byB0aGUgV2lraSEKCm1h
aWxsaXN0IDogbnRnLWNvbnRleHRAbnRnLm5sIC8gaHR0cDovL3d3dy5udGcubmwvbWFpbG1hbi9s
aXN0aW5mby9udGctY29udGV4dAp3ZWJwYWdlICA6IGh0dHA6Ly93d3cucHJhZ21hLWFkZS5ubCAv
IGh0dHA6Ly9jb250ZXh0LmFhbmhldC5uZXQKYXJjaGl2ZSAgOiBodHRwczovL2JpdGJ1Y2tldC5v
cmcvcGhnL2NvbnRleHQtbWlycm9yL2NvbW1pdHMvCndpa2kgICAgIDogaHR0cDovL2NvbnRleHRn
YXJkZW4ubmV0Cl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fCg==

--===============7668861791874320127==--