From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: bug with headcommand=type in definedescription?
Date: Sun, 29 Jan 2012 19:09:59 +0100 [thread overview]
Message-ID: <2EA0ECE5-07AA-46AF-9663-BDAA4BAD689C@googlemail.com> (raw)
In-Reply-To: <4F258506.2080601@web.de>
Am 29.01.2012 um 18:42 schrieb Pablo Rodríguez:
> On 01/29/2012 06:24 PM, Wolfgang Schuster wrote:
>>
>> [...]
>>
>> I tested it now myself and what you want doesn’t work in this way. As you can see
>> in the example below “headcommand=\tex” does work when you also use
>> “location=command” but only with some limitations, e.g. the font is wrong and
>> you loose also the option the change the location of the title.
>
> Thanks for your reply, Wolfgang.
>
> The font can be fixed using headstyle, but the location of the title is
> important for the document.
You can use a two step mechanism where the commands you use in the document
pass the content to a internal description environment.
\usemodule[annotation]
\definedescription[abcdescription]
\define[2]\AbcCommand
{\startabcdescription{\tex{\placeannotationtitle}}%
\placeannotationcontent
\stopabcdescription}
\defineannotation[abc][alternative=command,command=\AbcCommand]
\starttext
%\abc{starttext}{This is a description for \tex{starttext}}
\abc[title=starttext]{This is a description for \tex{starttext}}
\startabc[title=starttext]This is a description for \tex{starttext}\stopabc
\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-01-29 18:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 11:39 Pablo Rodríguez
2012-01-29 12:05 ` Wolfgang Schuster
2012-01-29 15:17 ` Pablo Rodríguez
2012-01-29 16:49 ` Aditya Mahajan
2012-01-29 17:08 ` Pablo Rodríguez
2012-01-29 17:24 ` Wolfgang Schuster
2012-01-29 17:42 ` Pablo Rodríguez
2012-01-29 18:09 ` Wolfgang Schuster [this message]
2012-01-29 18:19 ` Pablo Rodríguez
2012-01-29 18:38 ` Aditya Mahajan
2012-01-29 18:53 ` Wolfgang Schuster
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=2EA0ECE5-07AA-46AF-9663-BDAA4BAD689C@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).