1, TOC entries don't have to have a page number. Just click the Show More Options button in the TOC dialog, and set the number dropdown to no page number.
2, If I understand this, you should define a style for the TOC entries, not use the exiting style of the paragraph in the text.
Thanks Peter, finally "cracked the code" in this regard.
Next issue is the ordering of TOC entries.
About 7 .d ago I noticed that TOC displayed description entries ahead of captions, rather than vice versa. Fixed this by moving some descriptions lower in the page, below the captions. That worked at the time. I only moved a few of those at the time, just a a proof of concept. Noted that the revised TOC correctly reflected this change.
Then I began contending with page-number location, which is now resolved.
Now returning to the sequencing, I no longer seem to have any control of that, whatsoever. Have tried reversing the order of styles in the TOC style form, as well as locations of descriptions on pages. Nothing affects the sequencing of TOC entries.
Any ideas appreciated.
TOC picks up paragraphs according to how they are located, starting in the upper left corner and scanning down before moving right. Mis-ordering is usually the result of the heading being further to the right than the things that should fall below it.
Perfect Peter. One last issue for completion of the desired table:
I need to remove CR-LF between (pg nr) + spc + genus-species, and note immediately following, which always begins with the period and a space. I recall some earlier instructions on searching for certain characters in order to remove (line-feed + char return) in all instances where (as I have arranged it in this table) the next line begins with [Pd + Spc].
I'm guessing this might involve searching source code for all instances of the character combination described above, and combining all pairs of source lines that include them. Manual solution is last resort, but would prefer a script if that can be done.
With thanks in advance.
You lost me. CR-LF to my mind is a paragraph break, or hard return, which implies two paragraphs. Since TOC works on paragraphs, it makes a listing item for each paragraph. Perhaps you are using a "soft return" (it's been about 20 years since I wrote code that used CR-LF), but in either case, you would need to either use Find/Change on the TOC itself to remove the unwanted characters, or find another way to force the line break in the text that does not require the insertion of a break character. I don't write scripts, but I don't see any reason why the find/change could not be scripted if you can isolate the case where it needs to be applied.
Sorry if some of my terminology is a bit dated.
What I'm trying to describe is a collection of indexed items into my custom table of contents. Captions are followed by image descriptions. CR-LF comes from typewriter days, but there were/are ascii characters for this. Not sure I can correctly recall the ascii symbols for those? #32#10 is just a guess.
From your comments, I’m taking it that CR-LF is not used in modern (i.e., inDesign) documents.
Need to find all instances of trailing cr-lf-like characters/tags in para. style ImageID or the corresponding, leading characters/tags in para. style imgDescTOCentry.
Idea is, by deleting those, that text will flow smoothly from ImageID to imgDescTOCentry (which begins with “. “).
Thanks for your help, Peter.
If you are trying to work with code, you need to talk to coders. The SDK forum, or the scripting forum are the places you'll find them.