From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Seems `\definedescription' do not work
Date: Sun, 29 Apr 2012 09:14:57 +0200 [thread overview]
Message-ID: <6EF44E9A-EDD7-41A5-9C50-6892EF23B4BF@googlemail.com> (raw)
In-Reply-To: <20120429064845.GF1360@smoon>
Am 29.04.2012 um 08:48 schrieb Vladimir Lomov:
> Hello,
>
> I borrow this example from wiki:
> <example file="ex2.tex">
> %\setupbodyfont[computer-modern-unicode,12pt]
>
> \definedescription
> [Desc]
> [location=top,hang=20,
> headstyle={\bf\color[blue]},
> command=\hskip-1cm,margin=1cm]
>
> \starttext
> \startDesc{Tufte}
> \input tufte
> \stopDesc
> \stoptext
> </example>
The problem is \color which expects a argument for the text to be colored (e.g. \color[blue]{…}) which is never the case when you put it in a style key but you can use the color key to set the value.
\definedescription
[description]
[alternative=top,
headstyle=bold,
headcolor=blue,
headcommand={\offset[x=-1cm]},
margin=1cm]
\starttext
\input tufte
\startdescription{Tufte}
\input tufte
\stopdescription
\stoptext
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-04-29 7:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-29 6:48 Vladimir Lomov
2012-04-29 7:14 ` Wolfgang Schuster [this message]
2012-04-29 12:27 ` Vladimir Lomov
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=6EF44E9A-EDD7-41A5-9C50-6892EF23B4BF@googlemail.com \
--to=schuster.wolfgang@googlemail.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).