From: Steffen Wolfrum <context@st.estfiles.de>
Subject: Re: register fine tuning
Date: Thu, 26 Oct 2006 10:07:26 +0200 [thread overview]
Message-ID: <E5701066-6253-42AD-830E-553A2E19D94B@st.estfiles.de> (raw)
In-Reply-To: <453FCCE0.3000103@wxs.nl>
Sorry, same problem here as with your other posting:
How should I use this hack?
Given that I have a source TEX document (providing the \index{Keyword
and the \placeregister{index}} and those TUI and TOU files.
Where should I store the line below in order to manipulate (filter?)
the TUO?
Do I have to start a new file with a kind of \input command?
Steffen
Am 25.10.2006 um 22:45 schrieb Hans Hagen:
> Steffen Wolfrum wrote:
>> Hi,
>>
>> I am not sure how a ConTeXt index register is generated and what role
>> the tui and tuo files play.
>> But could it be possible to manually "fine tune" the generated
>> register?
>>
>> Something like from ...
>>
>> Keywords
>> -- secret 35
>> -- popular 25, 26, 27, 88, 89
>>
>> .... to ...
>>
>> Keywords see also Commands
>> -- secret 35
>> -- popular 25-27, 88-89
>>
>>
>> .... just by typing the changes in one of those helper files?
>>
>>
> it should not be to hard to filter the entries from a tuo into
> another file and use that one: dirty hack:
>
> \bgroup\def\jobname{copyof}\placeregister\egroup
>
> if needed i can provide a \setupregister[file=copyof] feature ;
>
> in mkiv there will be more control because we may move index
> handling in mem
>
> Hans
>
> -----------------------------------------------------------------
> 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
> -----------------------------------------------------------------
>
> _______________________________________________
> ntg-context mailing list
> ntg-context@ntg.nl
> http://www.ntg.nl/mailman/listinfo/ntg-context
>
next prev parent reply other threads:[~2006-10-26 8:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 9:34 Steffen Wolfrum
2006-10-25 20:45 ` Hans Hagen
2006-10-25 22:35 ` Vit Zyka
2006-10-26 8:07 ` Steffen Wolfrum [this message]
2006-10-26 8:32 ` Hans Hagen
2006-10-26 9:17 ` Steffen Wolfrum
2007-02-14 16:12 ` TOC (was: register) " Steffen Wolfrum
2007-02-15 16:06 ` TOC Hans Hagen
2006-10-26 8:42 ` register fine tuning Thomas A. Schmitz
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=E5701066-6253-42AD-830E-553A2E19D94B@st.estfiles.de \
--to=context@st.estfiles.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).