ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Robert Blackstone <blackstone.robert@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Index items
Date: Thu, 16 Apr 2015 20:08:36 +0200	[thread overview]
Message-ID: <6F24D05E-571F-4BA3-812E-A474A8710ED6@gmail.com> (raw)
In-Reply-To: <mailman.128.1429191487.8971.ntg-context@ntg.nl>


On 16 Apr 2015, at 15:38 , Hans Hagen <pragma@wxs.nl> wrote
> To: mailing list for ConTeXt users <ntg-context@ntg.nl>
> Subject: Re: [NTG-context] Index items
> Message-ID: <552FBB35.9050707@wxs.nl>
> Content-Type: text/plain; charset=utf-8; format=flowed
> 
> On 4/15/2015 11:41 PM, Robert Blackstone wrote:
>> 
>> On 15 Apr 2015, at 19:51 ,  Alan BRASLAU <alan.braslau@cea.fr> wrote
>>> Hans Hagen <pragma@wxs.nl> wrote:
>>> 
>>>> On 4/14/2015 1:48 PM, Robert Blackstone wrote:
>>>>> Dear all,
>>>>> 
>>>>> The book I am typesetting contains a very extensive and detailed
>>>>> index. The number of index items is probably around 1200, 16 pages.
>>>>> A fair number of them occur in more than one chapter.
>>>>> Like bibliography items, and for the sake of consistency, I have
>>>>> stored them in some auxiliary files and it is a matter of copy and
>>>>> paste to get them into the text in the proper place and way. (With
>>>>> always a risk of accidentally deleting or adding a spurious brace
>>>>> or bracket, with nasty results.)
>>>>> 
>>>>> I wonder therefore whether it would be possible to handle them like
>>>>> bibliography items, by means of a key, and leave their expansion to
>>>>> ConTeXt.
>>>>> 
>>>>> Would it be possible?
>>>>> And if it is not (yet) possible, how could I perhaps tackle it?
>>>> 
>>>> so you want to remap given index entries to new ones? at what moment?
>>> 
>>> We index pretty heavily now in the new bibliography dataset subsystem,
>>> that is one can create an index of authors, an index of keywords, an
>>> index of titles, etc. as well as index the pages on which a reference
>>> is cited. All of the information is there.
>>> 
>>> So say that you want to create a database of anything: words, images,
>>> phrases. You can put these into the database structure and then insert
>>> them or any associated information wherever you want in your text,
>>> later producing lists and indexes.
>>> 
>>> Can you give an example of what type of information you extensively
>>> index with detail?
>>> 
>>> Alan
>> Hi Alan,
>>  I realize that I have not yet reacted to Hans’ reply. So let me do that first (it was written but not yet sent).
>> 
>>  Hi Hans,
>> Do I want to remap given index entries? Assuming I understand your reply correctly the answer is: Yes, in principle. I would want to be able to change them if there are errors, or if some publisher has different views about the presentation of titles of items that are in the index (titles of songs, for instance). And also when (parts of) the text has (have) to be reused for other purposes. Change them in one operation, that is, not by digging up all occurrences in the book of the item that has to be changed.
>> 
>> In answer to Alan’s question: names, theoretical treatises and manuscripts, musical works, musical terms. Nearly all examples in the book have several features that have to be indexed: composer’s name, title of the published work (an opera for instance), title of the particular aria of which the example shows a fragment, and the special features that are shown in the example, parallel 7ths, for example.
>> The not-so-minimal example below (best processed iwth mkiv) gives an impression, also of the optical clumsiness that makes the unprocessed text practically unreadable. That is another reason why I would like to be able to call an index entry by means of some sort of key, like in bibliographic items for footnotes.
> 
> \startluacode
> 
>     document.indexentries = {
>         ["rule"]          = [[Rule(s)]],
>         ["ruleimperfect"] = [[+ \quote{imperfect to perfect, from}]],
>         ["galilei"]       = [[Galilei, Vincenzo]],
>     }
> 
>     function document.getindexentry(n)
>         context("\\index[%s]{%s}",n,document.indexentries[n] or ("<" .. 
> n .. ">"))
>     end
> 
> \stopluacode
> 
> \unexpanded\def\InEn[#1]%
>   {\ctxlua{document.getindexentry("#1")}}
> 
> \starttext
> That this rule
> \InEn[rule]
> \InEn[ruleimperfect] was not applied by everybody is for example shown 
> in {\em Fronimo}%
> \InEn[galilei]
> 
> etc etc

Wow, this is super! Great improvement, also for the readability of the text.
Thank you very much, Hans.

Kind regards,
Robert

___________________________________________________________________________________
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
___________________________________________________________________________________

       reply	other threads:[~2015-04-16 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.128.1429191487.8971.ntg-context@ntg.nl>
2015-04-16 18:08 ` Robert Blackstone [this message]
2015-04-19  7:47 ` Index items (additional question) Robert Blackstone
2015-04-19  9:50   ` Hans Hagen
2015-04-16  7:50 Index items Robert Blackstone
2015-04-16 10:48 ` Alan BRASLAU
     [not found] <mailman.120.1429120262.8971.ntg-context@ntg.nl>
2015-04-15 21:41 ` Robert Blackstone
2015-04-16 13:37   ` Hans Hagen
  -- strict thread matches above, loose matches on Subject: below --
2015-04-14 11:48 Robert Blackstone
2015-04-14 16:50 ` Hans Hagen
2015-04-15 16:58   ` Alan BRASLAU

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=6F24D05E-571F-4BA3-812E-A474A8710ED6@gmail.com \
    --to=blackstone.robert@gmail.com \
    --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).