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: Thu, 10 Jan 2013 22:21:31 +0100 [thread overview]
Message-ID: <8DDDF6ED-F6F1-408A-BA29-7878686CC6F1@gmail.com> (raw)
In-Reply-To: <20130107222047.GA11551@homerow>
Am 07.01.2013 um 23:20 schrieb Marco Patzer <homerow@lavabit.com>:
> On 2013–01–07 Wolfgang Schuster wrote:
>
>>> Blocks, in contrast to buffers, seem to be able to place content
>>> before it is defined. I did not check how they work, but since I
>>> didn't see any temporary files, the only possibility is to write the
>>> data to the tuc file, I assume. It is by any chance possible to
>>> provide a “method=block”?
>>
>> Yes, blocks are stored in the tux-file while buffers are only stored in memory.
>>
>> I played for a while with \setdataset to store the content but dropped it because
>> it required multiple runs and especially in the first run the output would be always
>> wrong
>
> That's no problem IMO. Two-pass data is always wrong the first run.
> In the worst case, it needs an additional run if text moves around
> too much. But since it's just another method, which is optional,
> this only applies if it's activated and then the user knows what
> he/she is doing and that it might be slower.
>
>> I can consider it as a optional method.
>
> I think it would be a nice feature. It enables placement of elements
> where they logically belong, instead of where they are supposed to
> be printed. It's nothing mission critical though, but you can keep
> it in mind for a rainy afternoon.
You can try the beta from my bitbucket site [0] which uses a two mechanism
for named buffers (\startannotation[<NAME>] … \stopannotation) which can
be accessed with \getannotation[<NAME>].
[0] https://bitbucket.org/wolfs/annotation/src
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-10 21:21 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
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 [this message]
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=8DDDF6ED-F6F1-408A-BA29-7878686CC6F1@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).