Re: [NTG-context] problem with \usemodule[chart]
Hallo Eckhart, vielen Dank für Deine Antwort. Ich habe mir daraufhin einige Installationshinweise (u.a. von fiee http://www.ramm.ch/fiee/texnique/) angesehen und insbesondere die sogenannten "Aufrufe" von MetaPost angesehen und diese in die entsprechenden Konfigurationsdateien auf enable gestellt bzw. hinzugefügt. Leider gehen die meisten Text nicht von Miktex (Win) aus (was ich ja gut verstehen kann), was aber dazu führt, dass bestimmte, genannte, Dateien so unter Miktex gar existieren. Das erleichtert mir als Sozialwissenschaftler, der noch nicht mal versteht, wie ein Kühlschrank funktioniert, aber dennoch schon jahrelang recht ordentliche Text mit latex bzw. pdflatex produziert, die Sache nicht gerade. Ergo: Trotz \write18 (miktex.ini) auf enable und weiteren Modifikationen leider kein Metapost. Ich erhalte folgende Hinweise beim Aufruf: texexec --pdf flowtest initexmf: don't know how to dump metafun cannot make metafun.mem I can't find the default mem file! Hast Du vielleicht noch eine Idee, der ich nachgehen könnte? Vielen Dank nochmal und herzliche Grüße, helmut
On Tue, May 13, 2003 at 08:32:18PM +0200, schwertner@t-online.de wrote:
I'd like to draw up a simple chart (\usemodule[chart]), but I get only the "text" (not really a document) and no "shape" on the PDF. I use a current version of Miktex total (Win) and the newest ConTeXt. What can I do?
Did you enable the \write18 feature? This allows tex to run external programs, needed for inline metapost graphics like flow shapes. I don't remember how to do this for miktex, but it is described in the context installation manual, together with some more hints for a context friendly setup.
-- Eckhart
Hi Helmut, Though I a m not using Miktex it seems that you might have to make the mem file (format file ) for metafun yourself. texexec --make metafun Keep in mind, that the mem-file is dumped into the directory where you run the texexec command. So please move that mem file to the place where the other format files reside (Web2c). Do run mktexlsr in order to update the database or whatever Miktex needs to achieve the same purpose. I hope this will solve the problem. Willi
Friday, May 16, 2003 Willi Egger wrote: WE> Hi Helmut, WE> Though I a m not using Miktex it seems that you might have to make the mem WE> file (format file ) for metafun yourself. WE> texexec --make metafun WE> Keep in mind, that the mem-file is dumped into the directory where you run WE> the texexec command. Worse :) In my MiKTeX distribution it's dumped where the TeX formats are. It has to be moved where the other .mem files are ... -- Giuseppe "Oblomov" Bilotta
Buona sera Giuseppe chi lavora quasi sempre ...
Mi dispiace molto, ma MikTex è un "libro chiuso" per me :-)
Buona fine settimana Willi
----- Original Message -----
From: "Giuseppe Bilotta"
Friday, May 16, 2003 Willi Egger wrote:
WE> Hi Helmut,
WE> Though I a m not using Miktex it seems that you might have to make the mem WE> file (format file ) for metafun yourself.
WE> texexec --make metafun
WE> Keep in mind, that the mem-file is dumped into the directory where you run WE> the texexec command.
Worse :) In my MiKTeX distribution it's dumped where the TeX formats are. It has to be moved where the other .mem files are ...
-- Giuseppe "Oblomov" Bilotta
_______________________________________________ ntg-context mailing list ntg-context@ntg.nl http://www.ntg.nl/mailman/listinfo/ntg-context
Friday, May 16, 2003 Willi Egger wrote: WE> Buona sera Giuseppe chi lavora quasi sempre ... WE> Mi dispiace molto, ma MikTex è un "libro chiuso" per me :-) WE> Buona fine settimana Willi Well, you may not know aboiut MiKTeX as much as I do, but at least your Italian is much better than my Dutch :) -- Giuseppe "Oblomov" Bilotta
At 22:24 16/05/2003 +0200, you wrote:
Friday, May 16, 2003 Willi Egger wrote:
WE> Hi Helmut,
WE> Though I a m not using Miktex it seems that you might have to make the mem WE> file (format file ) for metafun yourself.
WE> texexec --make metafun
WE> Keep in mind, that the mem-file is dumped into the directory where you run WE> the texexec command.
Worse :) In my MiKTeX distribution it's dumped where the TeX formats are. It has to be moved where the other .mem files are ...
hm, so do we need to configure this in texexec.ini ? (if present) Hans ------------------------------------------------------------------------- Hans Hagen | PRAGMA ADE | pragma@wxs.nl Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com ------------------------------------------------------------------------- information: http://www.pragma-ade.com/roadmap.pdf documentation: http://www.pragma-ade.com/showcase.pdf -------------------------------------------------------------------------
Saturday, May 17, 2003 Hans Hagen wrote: HH> At 22:24 16/05/2003 +0200, you wrote:
Worse :) In my MiKTeX distribution it's dumped where the TeX formats are. It has to be moved where the other .mem files are ...
HH> hm, so do we need to configure this in texexec.ini ? (if present) No. The bug is in LocatedFormatPath: the routine asks for the appropriate directory by calling `kpsewhich --show-path=fmt`, which is correct when looking for the formats path, but not when looking for the MetaPost formats path; instead, even RunMpFormat calls LocaltedFormatPath. I assume that a correction should be something along the lines of having a LocatedMpFormatPath which instead calls `kpsewhich --show-path=mem`. Keep in mind, though, that MiKTeX supports --show-path=fmt but not --show-path=mem; you may want to ask for --show-path=fmt and then replace the last occurrence of "fmt" with "mem". -- Giuseppe "Oblomov" Bilotta
participants (4)
-
Giuseppe Bilotta -
Hans Hagen -
Helmut Schwertner -
Willi Egger