ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: inmarge figures and references
Date: Mon, 09 May 2005 16:11:54 +0200	[thread overview]
Message-ID: <427F6FAA.4040703@elvenkind.com> (raw)
In-Reply-To: <f19514c9fcf04b6515704d54c6bc1b90@unibas.ch>



Jörg Hagmann wrote:
> Hi Taco,
> 
>>> 1. \inmarge figures can't be handled. Instead they appear in the 
>>> text. This is an example from the log file:
>>> ! Undefined control sequence.
>>> l.35 \inmarge
>>>              {\externalfigure[8pyruvate_lab]}
>>
>>
>> The command is called \inmargin (at least in the english interface).
> 
> 
> I was following the manual ("Context - an excursion") where \inmarge is 
> used with marginal figures. I thought that was the command to use, and 
> it works on my computer here.
> I am using \inmargin with text; does what you are saying mean the two 
> commands do the same?

\inmarge is dutch for \inmargin, and it should have been replaced in
the 'excursion" when ConTeXt switched to low-level english commands
last year. So yes, they are the same, but if you are not using the
dutch interface explicitly, then \inmarge will only work in old
ConTeXt-s.

>>> 2. The references don't work ("??"). Again, an example:
>>> references     : unknown reference [][krebsbox]
>>
>> Are you sure that texutil is started by the texexec run as it should?
> 
> No. How do I find out? And if it's not working, what should I do? (I 
> have to admit that I don't really understand the programme - I simply 
> translated into actions those few commands I could make sense of in the 
> texexec manual, such as make ...).

assuming you document is called 'test', then:

   $ texexec test

should end with:

   Output written on test.dvi (1 page, 296 bytes).
   Transcript written on test.log.

              return code : 0
                 run time : 1 seconds
     sorting and checking : running texutil

    TeXUtil 9.0.0 - ConTeXt / PRAGMA ADE 1992-2004

                   action : processing commands, lists and registers
                   option : sorting IJ under Y
                   option : converting high ASCII values
               input file : test.tui
              output file : test.tuo
          passed commands : 10
            remapped keys : 0
         register entries : 0 -> 0 entries 0 references
          synonym entries : 0 -> 0 entries
           embedded files : 1

         total run time : 2 seconds

   $

or something very much like this.

Good luck, Taco

  reply	other threads:[~2005-05-09 14:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 12:07 Jörg Hagmann
2005-05-09 12:32 ` Taco Hoekwater
2005-05-09 13:54   ` Jörg Hagmann
2005-05-09 14:11     ` Taco Hoekwater [this message]
2005-05-09 14:38       ` Jörg Hagmann
2005-05-10 12:27       ` Jörg Hagmann
2005-05-10 13:43         ` Taco Hoekwater
2005-05-10 14:39           ` luigi.scarso

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=427F6FAA.4040703@elvenkind.com \
    --to=taco@elvenkind.com \
    --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).