From: "Jigé via ntg-context" <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Jigé <broumpf-c@yahoo.com>
Subject: Re: [NTG-context] TiKz with LMTX
Date: Sun, 4 Jun 2023 21:04:54 +0000 (UTC) [thread overview]
Message-ID: <1848919559.10057435.1685912694071@mail.yahoo.com> (raw)
In-Reply-To: <mailman.1302.1685898062.41142.ntg-context@ntg.nl>
[-- Attachment #1.1: Type: text/plain, Size: 4422 bytes --]
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/systemlayer/pgfsys-vtex.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-textures.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-common-postscript.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvisvgm4ht.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvipdfm.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvipdfmx.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-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-tex4ht.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvisvgm.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvi.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-common-svg.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-xetex.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/systemlayer/pgfsys-dvips.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgf/utilities/pgfutil-context.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sys/pgflibrarypgfplots.surfshading.pgfsys-xetex.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sys/pgflibrarypgfplots.surfshading.pgfsys-dvips.def
/home/myname/.local/share/context/tex/texmf-modules/tex/generic/pgfplots/sys/pgflibrarypgfplots.surfshading.pgfsys-dvipdfmx.def
Il tried using some of these files by writing 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.
Here are some quotes from the online pgf/tikz manual ( https://tikz.dev/drivers#section-formats ) :
> 10.2.1 Selecting the Backend Driver
>
> When TEX typesets your document, it does not know which program you are going
> 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.
>
> Unfortunately, there is no “standard” 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 plugging does not work
> as expected, it is necessary to tell pgf directly which program you are going to use.
> This is done by redefining the macro \pgfsysdriver to an appropriate value before you load pgf.
> If you are going to use 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 programs are discussed.
>
> 10.2.2 Producing PDF Output
>
> 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.
>
> 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.
>
> This driver has a lot of functionality.
> (Almost) everything pgf “can do at all” is implemented in this driver.
>
> File [...]
[...]
(And so on with pgfsys-dvipdfm.def pgfsys-xetex.def pgfsys-vtex.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.
[-- Attachment #1.2: Type: text/html, Size: 4727 bytes --]
[-- Attachment #2: Type: text/plain, Size: 496 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
next parent reply other threads:[~2023-06-04 21:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1302.1685898062.41142.ntg-context@ntg.nl>
2023-06-04 21:04 ` Jigé via ntg-context [this message]
[not found] <mailman.49.1686219733.1391.ntg-context@ntg.nl>
2023-06-08 18:37 ` Jigé via ntg-context
2023-06-09 3:57 ` Aditya Mahajan via ntg-context
2023-06-09 6:13 ` Hans Hagen via ntg-context
2023-06-09 16:43 ` Aditya Mahajan via ntg-context
2023-06-12 16:49 ` Carlos via ntg-context
2023-06-12 16:59 ` Hans Hagen via ntg-context
[not found] <mailman.1332.1685970748.41142.ntg-context@ntg.nl>
2023-06-05 14:52 ` Jigé via ntg-context
[not found] <mailman.1322.1685946193.41142.ntg-context@ntg.nl>
2023-06-05 10:33 ` Jigé via ntg-context
2023-06-05 11:02 ` Floris van Manen via ntg-context
2023-06-05 12:49 ` Carlos via ntg-context
2023-06-05 13:06 ` Floris van Manen via ntg-context
2023-06-05 13:40 ` Carlos via ntg-context
2023-06-05 19:43 ` Carlos via ntg-context
2023-06-05 20:16 ` Carlos via ntg-context
[not found] <1949632129.10002246.1685869873625.ref@mail.yahoo.com>
2023-06-04 9:11 ` Jigé via ntg-context
2023-06-04 14:44 ` Hans Hagen via ntg-context
2023-06-04 15:10 ` Floris van Manen via ntg-context
2023-06-04 16:18 ` Hans Hagen via ntg-context
2023-06-04 21:58 ` Floris van Manen via ntg-context
2023-06-05 5:43 ` Mikael Sundqvist via ntg-context
2023-06-05 8:35 ` vm via ntg-context
2023-06-05 17:40 ` Aditya Mahajan via ntg-context
2023-06-06 2:32 ` Aditya Mahajan via ntg-context
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=1848919559.10057435.1685912694071@mail.yahoo.com \
--to=ntg-context@ntg.nl \
--cc=broumpf-c@yahoo.com \
/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).