From: "Stefan Müller" <warrence.stm@gmx.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: references
Date: Mon, 28 Feb 2011 16:08:09 +0100 [thread overview]
Message-ID: <4D6BBA59.1050105@gmx.de> (raw)
In-Reply-To: <4D55719B.4040901@wxs.nl>
Hi,
I think it could be useful to be able to "reuse" the label text setups
elsewhere, too.
I have for example
\definereferenceformat[inexp][label=example]
\setuplabeltext[en][example=example~]
in one of my documents. Why not specify this label when defining an
enumeration "example":
\defineenumeration[example][label=example]
This way I could easily use several languages in parallel with one
setup. The first letter should probably be capitalized in the
enumeration label...
Stefan.
On 11.02.2011 18:27, Hans Hagen wrote:
> Hi,
>
> I uploaded a beta. New:
>
> - Improved \textxt behaviour (for Mojca's code).
> - Korean labels and index tagging (with help from Jeong Dalyoung).
> - Cleaned of referencing (formats).
>
> \setupinteraction[state=start]
>
> \startbuffer[definitions]
> \definereferenceformat [PageOne] [left=(,right=),text=sometext]
> \definereferenceformat [PageTwo] [label=page]
> \definereferenceformat [PageThree] [label=*]
> \definereferenceformat [PageFour] [label=both]
>
> \setuplabeltext[en][page=page~]
> \setuplabeltext[en][chapter=chapter~]
> \setuplabeltext[en][both={chapter~,~retpahc}]
> \stopbuffer
>
> \getbuffer[definitions]
>
> \starttext
>
> \chapter[one]{One}
>
> \typebuffer[definitions]
>
> \startbuffer
> \PageOne[two]
> \PageTwo[two]
> \PageThree[two]
> \PageFour[two]
> \at{(}{)}[two]
> \at{!}[two]
> \at{page}[two]
> <<\at[two]>>
> \stopbuffer
>
> \typebuffer \startlines \getbuffer \stoplines
>
> \chapter[two]{Two}
>
> \typebuffer[definitions]
>
> \startbuffer
> \PageOne[one]
> \PageTwo[one]
> \PageThree[one]
> \PageFour[one]
> \at{(}{)}[one]
> \at{!}[one]
> \at{page}[one]
> <<\at[one]>>
> \stopbuffer
>
> \typebuffer \startlines \getbuffer \stoplines
>
> \stoptext
>
___________________________________________________________________________________
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:[~2011-02-28 15:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-11 17:27 references Hans Hagen
2011-02-11 19:23 ` references Florian Wobbe
2011-02-11 19:28 ` references Hans Hagen
[not found] ` <0C82F986-4A00-4587-BE0A-56D01BB52A88@awi.de>
[not found] ` <4D5869F6.3080801@wxs.nl>
[not found] ` <84FDA7BF-F81F-4975-A8EF-DE6AB857C2E9@awi.de>
2011-02-14 22:33 ` references Hans Hagen
2011-02-15 11:00 ` references Florian Wobbe
2011-02-15 19:09 ` references Hans Hagen
2011-02-28 15:08 ` Stefan Müller [this message]
2011-02-28 16:38 ` references Stefan Müller
2011-02-28 16:58 ` references Wolfgang Schuster
2011-03-01 9:27 ` references Stefan Müller
2011-03-01 10:08 ` references Vedran Miletić
-- strict thread matches above, loose matches on Subject: below --
2002-06-05 6:44 References Martin Kolarik
2002-06-05 12:57 ` References 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=4D6BBA59.1050105@gmx.de \
--to=warrence.stm@gmx.de \
--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).