From: Hans Hagen <pragma@wxs.nl>
To: snelting@collectifs.net,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: one entry, multiple registers
Date: Thu, 19 Feb 2009 14:58:55 +0100 [thread overview]
Message-ID: <499D659F.2070200@wxs.nl> (raw)
In-Reply-To: <499D5CD2.7050207@collectifs.net>
Femke Snelting wrote:
> Dear list,
>
> I'm part of a design group Open Source Publishing, and since a few
> months we are using various TeX related packages. After many trials and
> errors we were more than happy to come accross ConTeXt and it starts to
> grow on us :-)
>
> For the lay-out of a multi-lingual art publication we would like to
> include four registers. I've searched mailinglist, manuals and wiki but
> can't find how to add the same entry to *multiple* registers. How should
> I mark up 'carrots' to make it appear in Orange AND in Vegetable? Or is
> \Vegetable{carrots}\Orange{carrots}{carrots} really the best way?
there is no such sharing built in (for context mkiv i will probably
provide a merge registers features)
\def\VegetableAndOrange#1%
{\Vegetable{#1}\Orange{#1}#1}
\VegetableAndOrange{carrot}
is pretty safe
>
> Femke
>
> http://www.ospublish.constantvzw.org
>
> -----------------------
>
> \defineregister[Orange][Orange]
> \defineregister[Vegetable][Vegetables]
>
> \starttext
>
> In a large pot combine broth, water, wine, apples,
> \Vegetable{carrots}\Orange{carrots}{carrots}, \Vegetable{onion}{onion},
> \Vegetable{fennel}{fennel}, bay leaf, thyme and peppercorns; heat to
> boiling. Reduce heat to simmer, cover, and cook 20 minutes.
>
> \completeOrange
> \completeVegetable
>
> \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 : https://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
>
--
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-02-19 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 13:21 Femke Snelting
2009-02-19 13:58 ` Hans Hagen [this message]
2009-02-20 8:15 ` Femke Snelting
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=499D659F.2070200@wxs.nl \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.nl \
--cc=snelting@collectifs.net \
/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).