ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Peter Rolf <indiego@gmx.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Standalone chart
Date: Sun, 27 Apr 2008 00:57:59 +0200	[thread overview]
Message-ID: <4813B377.3080502@gmx.net> (raw)
In-Reply-To: <859A03C6-6B27-47B6-AD4A-C0EECB08AE9D@suddenlink.net>

David Arnold schrieb:
> All,
> 
> I am trying to make a standalone chart, a single graphic to be  
> included in a Latex file by a student. I have:
> 
%%% > \startMPinclusions
> \usemodule[chart]
> 
> \setupFLOWcharts
> [option=test,
> nx=4,
> ny=3,
> dx=2\bodyfontsize,
> dy=2\bodyfontsize,
> width=12\bodyfontsize,
> height=7\bodyfontsize,
> maxwidth=\textwidth]
> 
%%% > \stopMPinclusions
> 
> \starttext
> 
%%%  > \startMPpage
\startTEXpage
> 
> \startFLOWchart[SIRS]
> \stopFLOWchart
> 
> \FLOWchart[SIRS]
> 
%%% > \stopMPpage
\stopTEXpage
> 
> \stoptext
> 
> But I am getting the following error. Any suggestions?
>

i never used flow charts, so this is just a guess...

HTH, Peter

> systems         : system commands are disabled
> (/usr/local/texlive/2007/../texmf-local/tex/context/base/pdfr-def.tex)
> systems         : begin file SIRSchart at line 16
> ! Argument of \dotripletestempty has an extra }.
> <inserted text>
>                  \par
> <to be read again>
>                     }
> \doifnextcharelse ...token =#1\def \!!stringa {#2}
>                                                    \def \!!stringb  
> {#3}\futur...
> <write> \usemodule
> dx=2...=test,rts   [chart]
> <inserted text>
>                  }\endwrite
> \nonowriteMPgraphicline ...te \write \MPwrite {#1}
>                                                    \else \long \edef  
> \ascii {...
> ...
> l.25 \stopMPpage
> 
> ?
> 
> 
> 
> ___________________________________________________________________________________
> 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  : https://foundry.supelec.fr/projects/contextrev/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________
> 

___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


      reply	other threads:[~2008-04-26 22:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22  2:00 % in URL Alan Bowen
2008-04-22  6:14 ` Wolfgang Schuster
2008-04-22 11:30   ` Alan Bowen
2008-04-22 14:48     ` Hans Hagen
2008-04-26 22:17 ` Standalone chart David Arnold
2008-04-26 22:57   ` Peter Rolf [this message]

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=4813B377.3080502@gmx.net \
    --to=indiego@gmx.net \
    --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).