From: Wolfgang Schuster <wolfgang.schuster@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Place an annotation before it is defined
Date: Mon, 7 Jan 2013 22:34:07 +0100 [thread overview]
Message-ID: <ECD47FC6-6D24-4318-B94E-51630CB991B9@gmail.com> (raw)
In-Reply-To: <20130107212015.GV11551@homerow>
Am 07.01.2013 um 22:20 schrieb Marco Patzer <homerow@lavabit.com>:
> Hi,
>
> what is the best solution to place the content of annotations before
> they are defined in the text? What comes to mind is writing the
> content into an external file and read it in the next run. But maybe
> I overcomplicate things (usually I do) and there's a simpler
> solution. Here's an example:
>
> \usemodule
> [annotation]
>
> \defineannotation
> [myannotation]
>
> \setupannotation
> [myannotation]
> [alternative=myalternative]
>
> \defineannotationalternative
> [myalternative]
> [renderingsetup=annotation:myalternative]
>
> \startsetups [annotation:myalternative]
> Content: \placeannotationcontent
> \stopsetups
>
> \starttext
>
> %% The annotation content should be placed here.
>
> \input ward \blank
>
> %% Although it is defined later
> \startmyannotation
> \input knuth
> \stopmyannotation
>
> \stoptext
That’s not possible because the content is stored only in memory and is therefore only available after you put the environment in your document.
What you can do is to set the content of the environment at the begin of the document and refer to it at a later position like you can do with buffers.
\usemodule[annotation]
\defineannotation[test][method=buffer,text=Test]
\starttest[one]
\input knuth
\stoptest
\starttest[two]
\input ward
\stoptest
\starttext
\gettest[two][title=Ward]
\gettest[one][title=Knuth]
\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:[~2013-01-07 21:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 21:20 Marco Patzer
2013-01-07 21:25 ` Hans Hagen
2013-01-07 21:49 ` Marco Patzer
2013-01-07 21:57 ` Wolfgang Schuster
2013-01-07 22:20 ` Jaroslav Hajtmar
2013-01-07 22:25 ` Wolfgang Schuster
2013-01-07 22:28 ` Marco Patzer
2013-01-07 21:59 ` Hans Hagen
2013-01-07 21:34 ` Wolfgang Schuster [this message]
2013-01-07 21:56 ` Marco Patzer
2013-01-07 22:01 ` Wolfgang Schuster
2013-01-07 22:20 ` Marco Patzer
2013-01-10 21:21 ` Wolfgang Schuster
2013-01-11 8:45 ` Marco Patzer
2013-01-11 16:08 ` Wolfgang Schuster
2013-01-11 17:06 ` Marco Patzer
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=ECD47FC6-6D24-4318-B94E-51630CB991B9@gmail.com \
--to=wolfgang.schuster@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).