From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Taco Hoekwater <taco@elvenkind.com>
Subject: Re: urgent reference problem (full path)
Date: Thu, 24 Apr 2008 19:38:11 +0200 [thread overview]
Message-ID: <4810C583.3080908@wxs.nl> (raw)
In-Reply-To: <98D0571D-4D69-44A6-BEB1-1E67DAB947F2@st.estfiles.de>
Steffen Wolfrum wrote:
> I don't know how the section number (with/without previous number) is
> build internally, but I hope there could be a hack, with ...
>
> setupsection[...][previousnumber=yes]% so that referencing gets the
> full path
>
> .... but a section-design like "previousnumber=no", made with ...
>
> \setuphead[...][command=\PreviousNumberNo]
>
>
> Could this be done?
the current mechanisms are a messy compromise of old tex, newer tex
(etex) and history ... lists, references and sectioning will be
rewritten (and more flexible) for mkiv
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| 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://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2008-04-24 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 8:51 Steffen Wolfrum
2008-04-24 12:55 ` Steffen Wolfrum
2008-04-24 14:32 ` Wolfgang Schuster
2008-04-24 17:38 ` Hans Hagen [this message]
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=4810C583.3080908@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).