ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Pontus Lurcock <pont@talvi.net>
To: ntg-context@ntg.nl
Subject: Re: Marking a textfragment for later reference
Date: Tue, 7 Aug 2012 09:03:38 +0100	[thread overview]
Message-ID: <20120807080338.GU9970@rae.vm.bytemark.co.uk> (raw)
In-Reply-To: <89CA97EF-D04B-48D8-8BDC-AF2363B9FF64@gmail.com>

On Tue 07 Aug 2012, Robert Blackstone wrote:

> Here follows my minimal example. I reasoned that the identifier [topica] might act as a label, or an anchor, or whatever the correct ConTeXt name is, for a reference.
> ---------------------------------------------------------------------------
> 
> \definedelimitedtext[topica]
> \setupdelimitedtext[topica][left=,right=] %maybe superfluous? I do not need a layout different from the rest of the text.
> \starttext
> 
>  Some text.
> 
> \starttopica
> Some text to explain a certain topic, called topica.
> \stoptopica
> 
> Some more text about topica. (See discussion on \at{page}[topica])
> 
> \stoptext
> 
> ---------------------------------------------------------------------------
> To avoid any misunderstanding: this is no longer a problem since I have been given excellent advice. But it intrigues me. Why can some identifiers, for example of figures, be used for internal references and others not?

In this case, I'd say it's because you're defining a delimited text
style which can be used in multiple places. Your document could have
five hundred \starttopica...\stoptopica blocks on different pages.
A figure identifier, on the other hand, is meant to be unique.

Pont
___________________________________________________________________________________
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-08-07  8:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.10.1344285220.14247.ntg-context@ntg.nl>
2012-08-07  7:42 ` Robert Blackstone
2012-08-07  8:03   ` Pontus Lurcock [this message]
2012-08-07 15:42   ` Wolfgang Schuster
     [not found] <mailman.35.1344350527.14247.ntg-context@ntg.nl>
2012-08-08  7:48 ` Robert Blackstone
     [not found] <mailman.24.1344331200.14247.ntg-context@ntg.nl>
2012-08-07  9:44 ` Robert Blackstone
2012-08-07 10:47   ` Sietse Brouwer
     [not found] <mailman.7.1344276418.14247.ntg-context@ntg.nl>
2012-08-06 20:07 ` Robert Blackstone
     [not found] <mailman.12.1344199608.17520.ntg-context@ntg.nl>
2012-08-06  7:41 ` Robert Blackstone
2012-08-06 12:16   ` Wolfgang Schuster
     [not found] <mailman.1.1344177459.17520.ntg-context@ntg.nl>
2012-08-05 15:59 ` Robert Blackstone
2012-08-05 14:05 Robert Blackstone
2012-08-05 14:37 ` Wolfgang Schuster
2012-08-05 14:38 ` 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=20120807080338.GU9970@rae.vm.bytemark.co.uk \
    --to=pont@talvi.net \
    --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).