> You can add further topic arrays using “Additional Index As”. > If you index the text “Nisus Writer” once using ‘Index’ and once using ‘Index As’ with the topic “Document Processor”, the array of arrays will be ((), (“Document Processor”)) > If you use ‘Index As’ on the text “Nisus Writer” and use “Nisus Writer” as the topic, the array of arrays will be ((“Nisus Writer”)) > If you just straight index something, the array of arrays will be (()), that is an array containing an empty array. If this sounds complicated, it’s because it is -) > Basically Nisus treats (so it seems) indexing as a kind of attribute, except that the “attribute” is an _array of arrays of topics_. > Let me try to explain again how this works, although this is a bit presumptuous on my part, since I’m not really sure I know myself. This is because when I reply, I always forget to change the address field of the listserve. > Anyway, although the current implementation of indexing is well thought, it seems that there are many points which could be / should be improved. > So we have to check each occurrence using the Find box, but this is very time consuming. Prompt "Indexation Complete", "A Total of $count entries have been marked for inclusion in the index." $indexTopic = $wordList.cellAtRowAndColumn($row,1).text $indexItem = $wordList.cellAtRowAndColumn($row,0).text $wordListDoc = Document.open $wordListFile, Word list must include a table with exactly two columns # will be "generated automatically from text" not indexed with a blank string # - if the second column of the word list is blank, the index topic # - it allows the user to include Powerfind bubbles as part of the index # - it allows the user to tailor the find options # This macro provides a similar interface to the regular Nisus command
# Macro Index Using Word List (Powerfind) You only need to provide index topics if you want them to be different. So you don’t need to fill the whole table with repetitions of the first column. Unlike the built-in feature, this will index just as the plain “Index” command would. Finally I also tested it with a table where I leave the second column empty. So you could use “CharacterNotInSet(-)” to exclude things like “Yamato-takeru” from the “Yamato” search, etc. Also since it uses Powerfind you could use Powerfind bubbles in your word list. I have set the options to “-iw”, and this seems to work for your case. Since it uses Powerfind you can set your own search options. But the macro uses the list and runs a search for each item in the list and applies the index using the term in the second column. Here’s a macro that works almost the same as the built-in feature, and it should work with the same word list. But for a language like French this is a problem. It seems that the feature only indexes the term, if the item is “a word” in the text. This would seem to be a problem related to how the Index Using Word List feature defines word.
> I found another problem: when we run Index Using Word List, some occurrences of a word that is listed in the list file do not get indexed: one of the cases in which the word is not indexed is when it comes just after an apostrophe (for example, if you have "antiquité" in your word list, "the antiquité" would be indexed, but not "l'antiquité", etc.). > On 2015 Oct 27, at 11:53, Nobumi Iyanaga wrote: LISTSERV - NISUS Archives - Hello Nobumi,
0 kommentar(er)
