ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Simon Pepping <spepping@scaprea.hobby.nl>
Subject: Re: index term in term of a definition list
Date: Tue, 18 Mar 2003 22:06:49 +0100	[thread overview]
Message-ID: <20030318210649.GB1813@scaprea> (raw)
In-Reply-To: <5.1.0.14.1.20030318090704.03f0d258@server-1>

On Tue, Mar 18, 2003 at 09:08:33AM +0100, Hans Hagen wrote:
> At 08:27 PM 3/17/2003 +0100, you wrote:
> >In XML documents this may occur:
> >
> > <varlistentry>
> >   <term>sarge
> >     <indexterm significance="normal">
> >       <primary>sarge</primary>
> >     </indexterm>
> >   </term>
> >   <listitem>
> >     <para>De groene soldaat</para>
> >   </listitem>
> > </varlistentry>
> >
> >Is it a fundamental problem to enable this in Context? If so I must
> >find other solutions.
> 
> \defineXMLenvironmentsave[indexterm][significance=]
>   {\bgroup
>    \defineXMLsave[primary]}
>   {\expanded{\index{\XMLflush{primary}}}%
>    \egroup}

The term element is saved in \XMLDBterm, complete with embedded
indexterm, and then used as: \startvariable{\XMLDBterm}, so the above
\index command would still be in the term of the definitionlist.

I now save the indexterm element when \XMLDBterm is expanded, and
process it after \startvariable. However, \XMLDBterm may contain more
than one indexterm element (not likely, but it can), so I would need
to save a stack of them to cater for that possibility.

Of course I could also expand the term element and save the expanded
value in \XMLDBterm, but that has its own risks.

Regards, Simon

-- 
Simon Pepping
email: spepping@scaprea.hobby.nl

      reply	other threads:[~2003-03-18 21:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-17 19:27 Simon Pepping
2003-03-18  8:04 ` Hans Hagen
2003-03-18  8:08 ` Hans Hagen
2003-03-18 21:06   ` Simon Pepping [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=20030318210649.GB1813@scaprea \
    --to=spepping@scaprea.hobby.nl \
    --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).