From: Tobias Burnus <burnus@gmx.de>
Subject: ConTeXt: Chapter numberation and MetaPost figues
Date: Fri, 10 Sep 1999 16:47:31 +0200 [thread overview]
Message-ID: <37D91A03.B0954752@gmx.de> (raw)
Hi all,
is there a nice way to set the chapter number, I need only the even ones (thus:
Chapter 2, 4, ...). Which screw have I to turn, to set the value manually.
Second: I use something like this:
\startkombination[2*1]
{\externeabbildung[mp_abb.1][breite=2.5cm]}{a) Leiter}
{\externeabbildung[mp_abb.2][breite=2.5cm]}{b) Halbleiter}
\stopkombination
I have a mp_add.mp file, in which I have beginfig(1), ...(2),
Using above code, ConTeXt tells me in nice German-Dutch:
figures : Dimensionen von ./mp_abb.1 geladen von Abbildungsdatei selbst
[MP color conversion ./mp_abb.1 not needed] [MP to PDF ./mp_abb.1] (./mp_abb.1)
{/usr/local/teTeX/share/texmf/dvips/config/pdftex.map} (./main.tuo)
figures : Abbildungobject mp_abb.2 ist herbraucht
^^^^^^^^^-Reused
(,,wiederverwendet'')
How can I solve this problem? I don't want to have two same figues in one
document.
Tobias
next reply other threads:[~1999-09-10 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-10 14:47 Tobias Burnus [this message]
1999-09-10 15:45 ` Hans Hagen
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=37D91A03.B0954752@gmx.de \
--to=burnus@gmx.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).