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 (additional question)
Date: Sun, 19 Apr 2015 20:30:35 +0200	[thread overview]
Message-ID: <2411D92B-10E1-4337-A601-6F3CB0A8BCD8@gmail.com> (raw)
In-Reply-To: <mailman.159.1429437332.8971.ntg-context@ntg.nl>


On 19 Apr 2015, at 11:55 , Hans Hagen <pragma@wxs.nl> wrote
> 
> On 4/19/2015 9:47 AM, Robert Blackstone wrote:
>> 
>> On 16 Apr 2015, at 15:38 , Hans Hagen <pragma@wxs.nl> gave me the following:
>> 
>>> \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
>> 
>> 
>> This code works beautifully in this way, with only a few index entries  at the top of the file, before \starttext.
>> But how can I deal with the thousand or more index items in my project, which I have collected in four separate dedicated files with indexentries, like the three shown in the example-code.
>> 
>> I have really no idea  what else should be in these files,  what sort of name they should have, in particular extension,  and how and where I can input them.
>> I use TeXShop as my texteditor but that is probably not relevant here.
>> 
>> Can you give me some guidance, please?
> 
> \startluacode
> 
>     document.indexentries = {
>         ["rule"]          = [[Rule(s)]],
>         ["ruleimperfect"] = [[+ \quote{imperfect to perfect, from}]],
>         ["galilei"]       = [[Galilei, Vincenzo]],
>     }
> 
>     function document.loadindexentries(filename)
>         local fullname = resolvers.findfile(filename)
>         if fullname ~= "" then
>             local data = io.loaddata(fullname)
>             for a, b  in string.gmatch(data,"%s*(%S+)%s+([^\n\r]+)") do
>                 document.indexentries[a] = b
>             end
>         end
>     end
> 
>     function document.getindexentry(n)
>         local ie = document.indexentries[n]
>         if not ie then
>             logs.report("index","missing entry %a",n)
>         end
>         context("\\index[%s]{%s}",n,ie or ("<" .. n .. ">"))
>     end
> 
> \stopluacode
> 
> \unexpanded\def\LoadInEn[#1]{\ctxlua{document.loadindexentries("#1")}}
> \unexpanded\def\InEn    [#1]{\ctxlua{document.getindexentry("#1")}}
> 
> \LoadInEn[whatever.txt]
> 
> \starttext
> That this rule
> \InEn[rule]
> \InEn[ruleimperfect] was not applied by everybody is for example shown 
> in {\em Fronimo}%
> \InEn[galilei]
> 
> \InEn[unknown]
> 
> etc etc
> 
> \InEn[GalileiFronimo]
> \InEn[Cadence]
> \InEn[CadenceP]
> \InEn[PlagalCad]
> \index[Fronimo]{{\em Fronimo} (Galilei)} (1584), Vincenzo Galileo's 
> treatise on lute playing and the intabulation%
> \index[Intabulation]{intabulation}  of vocal music.
> \page
> 
> whatever.txt:
> 
> GalileiFronimo +{\em Fronimo}
> Cadence        cadence(s)
> CadenceP       + plagal
> PlagalCad      plagal cadence
> 
Hi Hans,

Thank you for your reply.
It took me a while to make your code operational in the way I need it.
For the new example you gave is still an "integral file". My project, like most book-projects, I guess, is modular with a master file Project.tex, into which everything else, setups, .bbl's, front- and backmatter, the various chapters are input. Though strictly speaking it would not be impossible to add some 1000 lines of index entries before \startproject, it would not be especially handy, and I cannot believe that it would be the proper ConTeXt-way to do it.

I found that when I split your code, transferred the top part to a new file, which I named "IndexItems", and input that into the other half, the text proper, it works. But when I add another file with indexentries, for instance "indexitemsnames", then only one of them, the one at the top is used. 
So it seems that the whole collection of index items must be in one file.
Is that the only possibility or are there ways to enable the use of several collections of index items?

Best 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-19 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.159.1429437332.8971.ntg-context@ntg.nl>
2015-04-19 18:30 ` Robert Blackstone [this message]
     [not found] <mailman.128.1429191487.8971.ntg-context@ntg.nl>
2015-04-19  7:47 ` Robert Blackstone
2015-04-19  9:50   ` 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=2411D92B-10E1-4337-A601-6F3CB0A8BCD8@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).