ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Rik Kabel <context@rik.users.panix.com>
Subject: Re: Labels and Enumerations
Date: Sun, 14 Jan 2018 15:46:11 +0100	[thread overview]
Message-ID: <fef5f18f-b09a-c77b-2352-3aea10b70604@wxs.nl> (raw)
In-Reply-To: <e075eba5-1101-a882-dfad-ce6bfb92a604@rik.users.panix.com>

On 1/13/2018 10:17 PM, Rik Kabel wrote:
> I would like to request the restoration of labels (\definelabel) to full 
> citizenship in MKIV. While enumerations are more flexible in many ways, 
> they cannot replace one particular use of labels if find necessary. 
> Enumerations are paragraph entities, while labels are not so restricted.
> 
> I use labels displayed as numbers in the margin to serially identify 
> quotations in a book about the development of quotation and 
> misquotation, at the same time generating reference information for 
> cross-referencing. While most quotations are blocks and can be handled 
> by enumerations, many are in-line quotations, and enumeration cannot be 
> used for these.
> 
> The wiki describes enumerations as the MKIV replacement for labels, and 
> the documentation as far as I can see omits \definelabel. Unless there 
> is something else supported in MKIV that can assume this function of 
> labels, can we please have full support for labels? I would not want to 
> see labels deprecated before the functionality is reproduced.
> 
> (Of course, if you can suggest how enumeration can be adapted to this 
> requirement, or suggest an alternative mechanism, this request can be 
> rejected.)

two options:

\defineconstructionalternative
   [mylabel]
   [renderingsetup=constructionrenderings:mylabel,
    width=]

\startsetups[constructionrenderings:mylabel]
     \dontleavehmode
     \flushconstructionheadbox
\stopsetups

\defineenumeration[two][alternative=mylabel,display=no,before=,after=]

\definelabel[foo][way=bychapter,prefix=chapter]

\starttext

     \startchapter[title=bar]

         here \starttwo\stoptwo \input tufte

         here \foo[xx] \input tufte

         whatever \in{foo}[xx]

     \stopchapter

\stoptext





-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2018-01-14 14:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-13 21:17 Rik Kabel
2018-01-13 22:14 ` Alan Braslau
2018-01-14 14:46 ` Hans Hagen [this message]
2018-01-14 20:37   ` Rik Kabel
2018-01-15  1:59     ` Rik Kabel
2018-01-15  8:09     ` Hans Hagen
2018-01-15 21:15       ` Rik Kabel
2018-01-16  8:21         ` Hans Hagen

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=fef5f18f-b09a-c77b-2352-3aea10b70604@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=context@rik.users.panix.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).