From: Thomas Lohmann <lohmannt@web.de>
Subject: charts
Date: Wed, 22 Aug 2001 00:58:36 +0200 [thread overview]
Message-ID: <3B82E79C.C11ACFCD@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
Hello all,
I don´t get charts using the chart module. The commands are ignored, but
running texexec builds the file flw-1.tmp with them. The tex-file is
-----------------------
\usemodule[chart]
\starttext
\startFLOWchart[cells]
\startFLOWcell
\name {first}
\location {1,1}
\shape {singledocument}
\text {not realy a document}
\stopFLOWcell
\stopFLOWchart
\stoptext
---------------------------
The log-file is attached
---------------------------
What´s wrong?
Greetings,
Thomas Lohmann
[-- Attachment #2: test.log --]
[-- Type: text/plain, Size: 1740 bytes --]
This is pdfeTeX, Version 3.14159-13d-2.1 (Web2C 7.3.1) (format=cont-en 2000.7.29) 21 AUG 2001 21:48
entering extended mode
**&cont-en test
(test.tex[/var/lib/texmf/pdftex/config/pdftex.cfg]
ConTeXt ver: 2000.1.31 fmt: 2000.7.29 int: english mes: english
language : language en is active
system : cont-new loaded
(/usr/share/texmf/tex/context/base/cont-new.tex
systems : beware: some patches loaded from cont-new.tex!
line 43: inserting E-TEX code \unless
)
system : cont-old loaded
(/usr/share/texmf/tex/context/base/cont-old.tex
loading : Context Old Macros
)
system : cont-fil loaded
(/usr/share/texmf/tex/context/base/cont-fil.tex
loading : Context File Synonyms
)
bodyfont : 12pt rm is loaded
language : patterns 2-deo-2 2-en-2 2-uk-2 2-de-2 2-fr-2 2-sp-2 2-nl-2 loa
ded
specials : tex,postscript,rokicki loaded
\openout2 = `test.tui'.
system : test.top loaded
(./test.top) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo)
(./test.tuo) (./test.tuo) (./test.tuo) (./test.tuo)
system : macros of module chart loaded
(/usr/share/texmf/tex/context/base/m-chart.tex) (./test.tuo)
systems : begin file test at line 3
system : saving buffer flw-1
\openout4 = `flw-1.tmp'.
systems : end file test at line 14
)
Here is how much of TeX's memory you used:
366 strings out of 32413
3992 string characters out of 406753
298038 words of memory out of 1100001
21347 multiletter control sequences out of 10000+25000
9049 words of font info for 28 fonts, out of 400000 for 1000
22 hyphenation exceptions out of 1000
27i,1n,44p,125b,234s stack positions out of 1500i,500n,1500p,50000b,5000s
No pages of output.
next reply other threads:[~2001-08-21 22:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-21 22:58 Thomas Lohmann [this message]
2001-08-22 12:29 ` charts Hans Hagen
2001-08-24 20:05 ` charts Thomas Lohmann
-- strict thread matches above, loose matches on Subject: below --
2005-04-04 20:28 Charts David Waller
2005-04-04 20:47 ` Charts Willi Egger
2005-04-05 19:59 ` Charts David Waller
2005-04-05 20:39 ` Charts Patrick Gundlach
2005-04-06 17:06 ` Charts Willi Egger
2005-04-06 18:06 ` Charts David Waller
2000-01-10 14:53 Undefined control sequence guravage
2000-01-10 19:56 ` Charts Slawek Zak
2000-01-10 20:47 ` Charts Berend de Boer
2000-01-11 9:32 ` Charts Hans Hagen
2000-01-11 16:07 ` Charts Slawek Zak
2000-01-11 16:07 ` Charts Hans Hagen
2000-01-11 18:23 ` Charts Slawek Zak
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=3B82E79C.C11ACFCD@web.de \
--to=lohmannt@web.de \
/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).