ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Stone <software.list.1es9s@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: New structure ...
Date: Tue, 19 May 2009 17:48:54 +0200	[thread overview]
Message-ID: <326847810905190848j25d7da76of78729d6d3b19fa4@mail.gmail.com> (raw)
In-Reply-To: <AFA0274A-8048-446E-A1B2-0286AD078622@boede.nl>


[-- Attachment #1.1: Type: text/plain, Size: 1426 bytes --]

On Tue, May 19, 2009 at 5:17 PM, Willi Egger <w.egger@boede.nl> wrote:

> Don't worry, Holland is still fine...
>
>
> But the problem I refer to is not in the dimension whether or not it is
> spelled correcltly.
> The error is still the same:
>
> ! Undefined control sequence.
> <argument> \reporttextprefixerror
>
> \secondoftwoarguments #1#2->#2
>
> \rightlabeltext ...ts \let \reporttextprefixerror
>                                                  \doreporttextprefixerror
> \...
> \labeltexts ...eftlabeltext {#1}#2\rightlabeltext
>                                                  {#1}
> \doifundefinedelse #1->\ifcsname #1
>                                   \endcsname \@EA \secondoftwoarguments
> \el...
> <argument> ... {\??ef \??ef XY\currentheadnumber }
>                                                   {\useexternalfigure
> [\s!d...
> ...
> l.14 ...er][width=\the\dimexpr.5\textwidth\relax]}
>
>
> \starttext
> \chapter{One}
> \placefigure
>        [here]
>        []
>        {A figure}
>
>  {\externalfigure[XY\currentheadnumber][width=\the\dimexpr.5\textwidth\relax]}
> \stoptext
>
> Willi


With...

\starttext
\chapter{One}
\placefigure
[here]
[]
{A figure}
% {\externalfigure[XY\currentheadnumber][width=0.5/textwidth]}
{\externalfigure[XY\currentheadnumber][width=0.5\textwidth]}
% {\externalfigure[XY\currentheadnumber][width=\the\dimexpr.5\texwidth\relax]}
\stoptext

I get: see attachment.
-- 
Alan

[-- Attachment #1.2: Type: text/html, Size: 2258 bytes --]

[-- Attachment #2: headnumber-test.pdf --]
[-- Type: application/pdf, Size: 9080 bytes --]

[-- Attachment #3: Type: text/plain, Size: 487 bytes --]

___________________________________________________________________________________
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:[~2009-05-19 15:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  9:41 Willi Egger
2009-05-19  9:58 ` Alan Stone
2009-05-19 13:13   ` Willi Egger
2009-05-19 13:21     ` luigi scarso
2009-05-19 13:49   ` Hans Hagen
2009-05-19 14:00     ` luigi scarso
2009-05-19 15:17       ` Willi Egger
2009-05-19 15:48         ` Alan Stone [this message]
2009-05-21 19:22           ` Willi Egger
2009-05-19 22:01       ` 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=326847810905190848j25d7da76of78729d6d3b19fa4@mail.gmail.com \
    --to=software.list.1es9s@gmail.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).