ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <pragma@wxs.nl>
Subject: Re: Is alternative=serried broken in enumerations?
Date: Wed, 22 Feb 2012 16:59:31 +0100	[thread overview]
Message-ID: <33F16D65-EBCF-49D7-BA16-3DCE9775CB1E@googlemail.com> (raw)
In-Reply-To: <20120222155140.6587.14996@localhost.localdomain>


Am 22.02.2012 um 16:51 schrieb Janne Junnila:

> Hi!
> 
> I'm using the current beta, and I get the following error when trying to use alternative=serried. (The minimal example is included in the error message.)
> 
> <error>
> system          > tex > error on line 6 in file test.tex: Undefined control sequence ...
> 
> 1     \defineenumeration[myenumeration][alternative=serried]
> 2     
> 3     \starttext
> 4     
> 5     \startmyenumeration
> 6 >>  This is a test.
> 7     \stopmyenumeration
> 8     
> 9     \stoptext
> 10     
> 
> 
> \12>:144>:serried ...onstructionlocationparameter 
>                                                  \c!width }\doifsetupselse ...
> \139>construction ...parameter \c!renderingsetup }
>                                                  \relax \dostoptagged \dost...
> \dodogotopar ...andler \v!construction \endcsname 
>                                                  \BeforePar \emptytoks 
> <to be read again> 
>                   T
> l.6 T
>     his is a test.
> </error>
> 
> Any ideas?

strc-con.mkvi

\startsetups[\??constructionrenderings:\v!serried]
-   \edef\p_width{\constructionlocationparameter\c!width}% CHECK ! ! ! wrong parameter namespace
+   \edef\p_width{\constructionparameter\c!width}% CHECK ! ! ! wrong parameter namespace
    \doifsetupselse{\??constructionrenderings:\v!serried:\p_width} {
        \directsetup{\??constructionrenderings:\v!serried:\p_width}
    } {
        \directsetup{\??constructionrenderings:\v!serried:\v!wide}
    }
\stopsetups

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


      reply	other threads:[~2012-02-22 15:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 15:51 Janne Junnila
2012-02-22 15:59 ` Wolfgang Schuster [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=33F16D65-EBCF-49D7-BA16-3DCE9775CB1E@googlemail.com \
    --to=schuster.wolfgang@googlemail.com \
    --cc=ntg-context@ntg.nl \
    --cc=pragma@wxs.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).