From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, HTML_MESSAGE,MAILING_LIST_MULTI,T_SCC_BODY_TEXT_LINE,URIBL_SBL_A autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 17269 invoked from network); 4 Jun 2023 21:05:25 -0000 Received: from zapf.ntg.nl (5.39.185.232) by inbox.vuxu.org with ESMTPUTF8; 4 Jun 2023 21:05:25 -0000 Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id DC4DB6E4; Sun, 4 Jun 2023 23:05:01 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl 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 a0U8QYMaW4-T; Sun, 4 Jun 2023 23:04:59 +0200 (CEST) Received: from zapf.ntg.nl (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id CDD8D1052; Sun, 4 Jun 2023 23:04:59 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by zapf.ntg.nl (Postfix) with ESMTP id 065D31052 for ; Sun, 4 Jun 2023 23:04:58 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at zapf.ntg.nl 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 jUQ2XJdpJTkm for ; Sun, 4 Jun 2023 23:04:56 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=77.238.179.148; helo=sonic304-23.consmr.mail.ir2.yahoo.com; envelope-from=broumpf-c@yahoo.com; receiver= Received: from sonic304-23.consmr.mail.ir2.yahoo.com (sonic304-23.consmr.mail.ir2.yahoo.com [77.238.179.148]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by zapf.ntg.nl (Postfix) with ESMTPS id 7C4376E4 for ; Sun, 4 Jun 2023 23:04:56 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1685912695; bh=Z4Luozr33wFV+ITTHQbIz3gN9cO11QtIDMj9JLYxJWU=; h=Date:From:To:In-Reply-To:References:Subject:From:Subject:Reply-To; b=pS56PnO6IvJc/wrnAJDs0zUvj+OOiVl6pjjZZIYMzVhjkCb3ZQCF3F7sLDzu4710Bc8rM+lyyoLnfSqHA00nk0zvUQkT5Goi8DCyLtQwRN05LaETApfV63xgk2YkEHej+oiLAD8bYQxjYLjFoqxByIcmlHImv+qGH5VPmR5ufeY6B8Sei5+v698jass13/FX3/26rrqqW/gAmjh0cukzSu8HqKRw4Q/bRh2U0Y5vpkfJ8EM/2yw1kR4H33pzt782cslOLSNKTK7DoJzjoSsz1gF42o9Y9QUvaGOUizKiI3UECxnvL8g4UTRAJo3e46lmted6Etko0/Y4eY9Q4wPZeA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1685912695; bh=Ii0rtwgJKWPmeE+8TOM4EfT7ORN4yJOc5alh9p1tyVp=; h=X-Sonic-MF:Date:From:To:Subject:From:Subject; b=OUwpd4811IiPp2NQwmioB5te0/VP/z2vyzSKn++vf6qLZJ1vgfmEb3OgQlVkcG8BSDwshmx+8U+EBwaq3shIgWK/6BX5344CjD0EL72VbUqiBvB3b5YE2yFTSqSpwqcYK/cXISKPSkWkSvi1VCOKOqnPrD+wx0wjCRKXtbAmvXeK9NxZuohZyKocbvcOYwVJi52BG7vaAE03cFMEhOK58wvNlV+MHTAWN3+AsNkC2a1/3nocZpKo97mtYpH25Ej+2PkQEXNpMp1EVx/6h+KHU5DoOqanraOJFFB9Lrpaztz7xDTito49Gj5rceWoJ2kQPfwjsa6F2QRbTAwmY/Ghyg== X-YMail-OSG: E4owstMVM1mR51t_JWIcsQesuVOJZIdIaoJHqlFvd6O6TxRNBxXMx_t1jbcFMyw vSPIJzna7Rz7_bJWpCGtuvpl5wYUcymyoAegRmVwZTGJxUjC5ceBwFcE33rCAzdhB49XoMVtclo6 FUcsWboQcLXYieci_wiBkIbuMcso_8jFyf5j9x7CZhTlOAG9ldn3G4DwIjl.QcluiAnGFYviRQSI qqdtNZ0Uyrzp_vASx_60.9VhuGbrZ9Eg0ELxc1ajzegHjXOCEameVLieNN0VldfdR5VOMhbOy7Yg pW0Ta8hM55GoG776PTUorna3Vo2sGHb1XGfoL5RKQKkcNx1Sig3Us7O7dVOe7anvM3Q_RjlyL3ul wS63IsuxEcLeDITqbQlCH6Qn97odqpjAEnsud53Mc0Fy9EkdfXd_Dsbg8.taskCtKg0quMeT.bXt .ZPvKj6HL6HTNil2ydL2rWYvbsBvntDai9HpHUvJXFqHeJhvOGzDmrVvtJVgvrJrmHUff.QT5cp9 h3K3A6.r3rfpt0isr3TI2pXw3qOmQMG70nXc0vSKl7CW_kl98jcjsTeEu4O9SNT8YE6xVE6qIuou pOxW5PYdPT1KntHVXOBYJYS26lP4v1LKUKR3naY3xq0IcD.IBoE9KjgTbLRGF5MYfeEYlL51lWRf COSnmL4w8E5OfUw4xRxwqRc9PyyarNiPkNyGCJb2YY3zzW9Dw8umXKo3o5mCZZfnINrmntw_zKPS R9VX7b54UMB9VI9zEMYM_EWdTvZQSHVOVPnE4VUOvuVjN91_pdy.S840RTs2t3lbii7gt5vgIluJ IvpvzgAqWqkvsMGenhpM7VJTgmgxQghkgRFsm2Whqiw2bMkzNpHLT96dr6325eWBGEM5hCUdLmX4 dEwUBpkkWdRNpYIvvxf2qlSYHNHs3qfE6guYFiUyzKblvGEIAvaSlPcISvdJQ8FPQkVRNfa1q6qy UvCsTMafSpYYC2j7fOo6bZXaOHFcWzEWA6jO9l1.L7Q4.Kc1D5c.aMtvzKdvGry7XZL4dLjBFmm4 b4flBCrI41VjM4W2s6a02hYHj4ZONr8jAlq_uZDAvGgWsK5jZZ33tt80Xr_5j_QgBsmiP6GLDZmr akPl4SxfCHKgWoPe_6VVVGuZVjV2Rv385dW65kR3Xk4M_ilIcDbY.LJpyfmdg_9AKTWyp__M.kis TzhAog1Ee47B9JxurfG_mIPTp3_Hb6MY9gf_kk4YineX6mdiKAaCGRRxFWEUiljy3qTTFDjLvzVC w2J8qHw5ct7Z25CIW.AMG8vyhnUalrpyQnG3NDbraETQQMiDuc0bZ0a7V1lbb1UvVR.Ibm.xJUvY pnhfFamzsDDEf7j1AZpZBVCm8IfMJ_SnUKgqe29oE9G_iyBOzlE_e6qk_J8ZNNK2Djjt8WdzFa6Y eX35GHOu0RkNQgG.45BAGFld7p8liEh2DeVisIGyYrodFFiSKT7nQ_xhEtm9Y1x775DqNVmn7N6G iDDqsLd38_7alrP.ZmfrHnYZcCc1IyqutDbTw19hAiHxlZ1_UMOFYukmOUhWbzqPWhXW8Vsr5.sc 1TDPvPDyvP4bqAR96tEvyqoEiiiqbrn9ETze9rBGYS4.ggiU82r9Qx2F0.5g_VJ7FPYLPcLh7Oid 8Jsbv1kh9Pm6F2PUxPZKe6K9qz2wYY5Az1dA09qIDZwntZM1iXeHkjjERU3RqkaT.1LHMP4DaFql VjnSuNxTe_GdpbfTwSAeosijdel6AtUdx.zkP3pyUlJtiuQN7.uClSHXkSu4tOI1eWvK.NUXHI02 yMUO7nvj4KO7BkzWKSUlBa2Ims8UobQR9BPtoskI_XlquDdqptBYT95Hf41P.uNJ6LhusYA20Ki8 mO6G7PSOhtOfwf0DFhkVXdUesLdTcChBRMrrzZhpRMU8rglGWHbSS0J3b8Wy_YwRc7i6PZEVnB6U bhgjYnXxXpH2l4QfLCGWDDrL1IqKZo6lAF9YbG8ymSoj7UXRUKHU8.dIssY.lnw0XM8Pg968kc6L BvAIn1r7Cx4AUGFeh_b70GZ.n0vq3BPbJDR8hLDeeb_AUMEnabL8sIwo141lA0whS1Uo13IBV.0i BaCE_IrpxKeXplDSKaKQI1AjUUk9hguPS2DZIWbD3XQIhlGGCWZ62bsf8GL7rLhKwibKhRByjIe0 UII7HXmBPwyZjdaFgiwmojOEN0u3yVv4tu1qG15Knv3RRXOtcHl1hMAWnALqEFqXwN3K_VZZT1rV 1D9FLfgwcKcd4Hbhgr30Og0ZMdFtmHcY- X-Sonic-MF: X-Sonic-ID: 21847cb9-bd12-4d8b-9efe-6da473d8477d Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.ir2.yahoo.com with HTTP; Sun, 4 Jun 2023 21:04:55 +0000 Date: Sun, 4 Jun 2023 21:04:54 +0000 (UTC) To: ntg-context@ntg.nl Message-ID: <1848919559.10057435.1685912694071@mail.yahoo.com> In-Reply-To: References: MIME-Version: 1.0 X-Mailer: WebService/1.1.21495 YMailNodin Subject: Re: [NTG-context] TiKz with LMTX X-BeenThere: ntg-context@ntg.nl X-Mailman-Version: 2.1.38 Precedence: list List-Id: mailing list for ConTeXt users List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: =?utf-8?q?Jig=C3=A9_via_ntg-context?= Reply-To: mailing list for ConTeXt users Cc: =?UTF-8?Q?Jig=C3=A9?= Content-Type: multipart/mixed; boundary="===============7182897882598882591==" Errors-To: ntg-context-bounces@ntg.nl Sender: "ntg-context" --===============7182897882598882591== Content-Type: multipart/alternative; boundary="----=_Part_10057434_755414419.1685912694070" ------=_Part_10057434_755414419.1685912694070 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I tried: $ mtxrun --generate and also commenting out "source/generic/**" in mtx-install-imp-tikz.lua but with no success. Same error: Driver file ``pgfsys-luatex.def'' not found. This file does not exist in my installation. $ find ~/.local/share/context -iname "*.def" /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-vtex.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-textures.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-common-postscript.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-dvisvgm4ht.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-dvipdfm.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-dvipdfmx.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-common-pdf.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-common-pdf-via-dvi.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-tex4ht.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-dvisvgm.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-dvi.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-common-svg.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-xetex.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systeml= ayer/pgfsys-dvips.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/utiliti= es/pgfutil-context.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sy= s/pgflibrarypgfplots.surfshading.pgfsys-xetex.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sy= s/pgflibrarypgfplots.surfshading.pgfsys-dvips.def /home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sy= s/pgflibrarypgfplots.surfshading.pgfsys-dvipdfmx.def Il tried using some of these files by writing them in context/tex/texmf-mod= ules/tex/generic/pgf/systemlayer/pgf.cfg , by the way, but it either doesn'= t compile or produces a bad picture. Here are some quotes from the online pgf/tikz manual ( https://tikz.dev/dri= vers#section-formats ) : > 10.2.1 Selecting the Backend Driver >=20 > When TEX typesets your document, it does not know which program you are g= oing > to use to transform the .dvi-file. If your .dvi-file does not contain any= special commands, > this would be fine; but these days almost all .dvi-files contain lots of = special commands. > It is thus necessary to tell TEX which program you are going to use later= on. >=20 > Unfortunately, there is no =E2=80=9Cstandard=E2=80=9D way of telling this= to TEX. > For the LATEX format a sophisticated mechanism exists inside the graphics= package > and pgf plugs into this mechanism. For other formats and when this pluggi= ng does not work > as expected, it is necessary to tell pgf directly which program you are g= oing to use. > This is done by redefining the macro \pgfsysdriver to an appropriate valu= e before you load pgf. > If you are going to use the dvips program, you set this macro to the valu= e pgfsys-dvips.def; > if you use pdftex or pdflatex, you set it to pgfsys-pdftex.def; and so on= . > In the following, details of the support of the different programs are di= scussed. >=20 > 10.2.2 Producing PDF Output >=20 > pgf supports three programs that produce pdf output [...]: > dvipdfm, pdftex, and vtex. The pdflatex program is the same as the pdftex= program: > it uses a different input format, but the output is exactly the same. >=20 > File pgfsys-pdftex.def > This is the driver file for use with pdfTEX, that is, with the pdftex or = pdflatex command. > It includes pgfsys-common-pdf.def. >=20 > This driver has a lot of functionality. > (Almost) everything pgf =E2=80=9Ccan do at all=E2=80=9D is implemented in= this driver. >=20 > File [...] [...] (And so on with pgfsys-dvipdfm.def pgfsys-xetex.def pgfsys-vtex.def... Basi= caly all the other drivers cited have serious shortcomings in processing Ti= Kz pictures.) So, we need the driver: pgfsys-luatex.def . Or do we? The name of this driv= er is guessed at compile time. =20 ------=_Part_10057434_755414419.1685912694070 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I tried:
$ mtxrun --generate
and also commenting= out "source/generic/**" in mtx-install-imp-tikz.lua
but with= no success.
Same error: Driver file ``pgfsys-luatex.def'' not f= ound.

This file does not exist in my installation.
$ find ~/.loca= l/share/context -iname "*.def"
/home/myname/.local/share/conte= xt/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-vtex.def
/home/m= yname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pg= fsys-textures.def
/home/myname/.local/share/context/tex/texmf-modules/te= x/generic/pgf/systemlayer/pgfsys-common-postscript.def
/home/myname/.loc= al/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvisv= gm4ht.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generi= c/pgf/systemlayer/pgfsys-dvipdfm.def
/home/myname/.local/share/context/t= ex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvipdfmx.def
/home/m= yname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pg= fsys-common-pdf.def
/home/myname/.local/share/context/tex/texmf-modules/= tex/generic/pgf/systemlayer/pgfsys-common-pdf-via-dvi.def
/home/myname/.= local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-te= x4ht.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic= /pgf/systemlayer/pgfsys-dvisvgm.def
/home/myname/.local/share/context/te= x/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvi.def
/home/myname/= .local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-c= ommon-svg.def
/home/myname/.local/share/context/tex/texmf-modules/tex/ge= neric/pgf/systemlayer/pgfsys-xetex.def
/home/myname/.local/share/context= /tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvips.def
/home/my= name/.local/share/context/tex/texmf-modules/tex/generic/pgf/utilities/pgfut= il-context.def
/home/myname/.local/share/context/tex/texmf-modules/tex/g= eneric/pgfplots/sys/pgflibrarypgfplots.surfshading.pgfsys-xetex.def
/hom= e/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sys/pg= flibrarypgfplots.surfshading.pgfsys-dvips.def
/home/myname/.local/share/= context/tex/texmf-modules/tex/generic/pgfplots/sys/pgflibrarypgfplots.surfs= hading.pgfsys-dvipdfmx.def

Il tried using some of these files by wri= ting them in context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgf.cfg = , by the way, but it either doesn't compile or produces a bad picture.<= br>
Here are some quotes from the online pgf/tikz manual ( https://tikz.= dev/drivers#section-formats ) :

> 10.2.1 Selecting the Backend Dr= iver
>
> When TEX typesets your document, it does not know whi= ch program you are going
> to use to transform the .dvi-file. If your= .dvi-file does not contain any special commands,
> this would be fin= e; but these days almost all .dvi-files contain lots of special commands.> It is thus necessary to tell TEX which program you are going to use = later on.
>
> Unfortunately, there is no =E2=80=9Cstandard=E2= =80=9D way of telling this to TEX.
> For the LATEX format a sophistic= ated mechanism exists inside the graphics package
> and pgf plugs int= o this mechanism. For other formats and when this plugging does not work> as expected, it is necessary to tell pgf directly which program you a= re going to use.
> This is done by redefining the macro \pgfsysdriver= to an appropriate value before you load pgf.
> If you are going to u= se the dvips program, you set this macro to the value pgfsys-dvips.def;
= > if you use pdftex or pdflatex, you set it to pgfsys-pdftex.def; and so= on.
> In the following, details of the support of the different prog= rams are discussed.
>
> 10.2.2 Producing PDF Output
> > pgf supports three programs that produce pdf output [...]:
> d= vipdfm, pdftex, and vtex. The pdflatex program is the same as the pdftex pr= ogram:
> it uses a different input format, but the output is exactly = the same.
>
> File pgfsys-pdftex.def
> This is the drive= r file for use with pdfTEX, that is, with the pdftex or pdflatex command.> It includes pgfsys-common-pdf.def.
>
> This driver has = a lot of functionality.
> (Almost) everything pgf =E2=80=9Ccan do at = all=E2=80=9D is implemented in this driver.
>
> File [...]
= [...]

(And so on with pgfsys-dvipdfm.def pgfsys-xetex.def pgfsys-vte= x.def... Basicaly all the other drivers cited have serious shortcomings in = processing TiKz pictures.)

So, we need the driver: pgfsys-luatex.def= . Or do we? The name of this driver is guessed at compile time.

=
=20 ------=_Part_10057434_755414419.1685912694070-- --===============7182897882598882591== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ___________________________________________________________________________________ If your question is of interest to others as well, please add an entry to the Wiki! maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context webpage : https://www.pragma-ade.nl / http://context.aanhet.net archive : https://bitbucket.org/phg/context-mirror/commits/ wiki : https://contextgarden.net ___________________________________________________________________________________ --===============7182897882598882591==--