From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Is the chart module broken?
Date: Fri, 19 Nov 2010 13:21:29 -0500 (EST) [thread overview]
Message-ID: <alpine.LNX.2.01.1011191319200.26855@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <AANLkTimfkn9J6SdCmG94_bbHcHYorKRds4Jz52MG0jGv@mail.gmail.com>
On Fri, 19 Nov 2010, Cecil Westerhof wrote:
> 2010/11/19 Hans Hagen <pragma@wxs.nl>
>
>> On 19-11-2010 8:43, Cecil Westerhof wrote:
>>
>> The only things I see that could mean something are:
>>> systems : no file 'cont-sys.tex', using 'cont-sys.rme' instead
>>>
>>
>> this is harmless but you can copy the file cont-sys.rme to cont-sys.tex and
>> tweak its content
>
>
> I did not think so, but better safe as sorry.
>
>
>
> pdfTeX warning: pdftex: no GlyphToUnicode entry has been inserted yet!
>>
>> But I do not know if that is a problem.
>>
>> The pfd is made with:
>> texexec --automp flowchart
>>
>> Without the --automp I get a message about mpost.
>>
>
> Is mpost run or not? Your code looks ok and generates an image here, so it
>> looks like mpost is not run on your system.
>>
>
> I tried to make it after running 'texexec --make metafun'.
> It is still not run. I get:
> systems : begin file flowchart at line 3
> (./flowchart-flw-1.tmp) (./flowchart-flw-1.tmp) (./flowchart-flw-1.tmp)sh:
> mpost: opdracht niet gevonden
>
> locate mpost gives:
> /home/cecil/ConTeXt/tex/texmf-linux/bin/mpost
> /home/cecil/ConTeXt/tex/texmf/metapost/base/mpost.mp
> /usr/lib/texmf/doc/man/man1/mpost.man1.pdf
> /usr/share/doc/packages/libSDL-devel/html/sdlsempost.html
> /usr/share/pstoedit/mpost.fmp
You pdftex is from texlive, but you do not have a metapost executable from
texlive. Either install metapost in texlive or use minimals (You already
seem to have the minimals installed. You need to run "source
~/ConTeXt/tex/setuptex" to add the minimals' binaries to the path).
Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2010-11-19 18:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 13:52 Cecil Westerhof
2010-11-03 18:41 ` Hans Hagen
2010-11-19 6:57 ` Cecil Westerhof
2010-11-19 7:43 ` Cecil Westerhof
2010-11-19 17:29 ` Hans Hagen
2010-11-19 18:12 ` Cecil Westerhof
2010-11-19 18:21 ` Aditya Mahajan [this message]
2010-11-19 20:19 ` Cecil Westerhof
2010-11-19 18:47 ` Hans Hagen
2010-11-19 20:23 ` Cecil Westerhof
2010-11-19 20:38 ` Hans Hagen
2010-11-20 5:04 ` Cecil Westerhof
2010-11-20 11:56 ` Hans Hagen
2010-11-20 16:08 ` Cecil Westerhof
2010-11-20 16:12 ` Aditya Mahajan
2010-11-20 20:26 ` Willi Egger
2010-11-20 20:41 ` Otared Kavian
2010-11-21 6:19 ` Cecil Westerhof
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=alpine.LNX.2.01.1011191319200.26855@ybpnyubfg.ybpnyqbznva \
--to=adityam@umich.edu \
--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).