Thanks, Uwe. That's fixed now. ... View more

It is a PDF. You can't have read it in any other way. ... View more

As Eugene mentioned, if you want the footnotes at the foot of the page, you'll have to have all the text in a single text frame. That seems possible when you incorporate the text that's now in separate frames into the main text, and set it (what used to be in separate frames) in two columns (Type > Paragraph > Span columns > select Split columns).   Text anchors, also mentioned by Eugene, are an option but they dob't split across pages. ... View more

In addition to what Willi mentioned: - Your justification settings are fine (though purists will frown at glyph scaling) - Allow hyphenation, making sure to set the spacing/hyphen slider to the left (better spacing, but more hyphens). If the author then starts moaning about the hyphens, set the slider at the middle.   Best would be to prepare a few samples with different settings and ask the author to pick what they like best.   ... View more

If I were you I'd convert those GREP styles to local styles. In documents with long stories, GREP styles usually cause delays. You can use a script to do that:  https://creativepro.com/files/kahrel/indesign/grep-styles-to-local-styles.html Saving your documents using Save As reduces their size lot (by deleting the document's undo history), which tends to make things smoother. And disable preflight, hide all panels -- the accumulation of all these things make a difference. ... View more

It's not possible. The Index panel shows only the cross- and page references in open documents. To do consistency checks you'll have to generate the index from time to time.   But 1,000+ pages in 18 documents isn't that outrageous, InDesign easily handles that in my experience. Are the illustrations you mention embedded? Do you use (a lot of) GREP styles? Anything else that slows down InDesign and/or makes it crash?   P. ... View more

You can use Add All in the New Page Reference window: But there's no shortcut key for that.   ... View more

Start a new document, then File > Place. Enable the 'Show Import Options' box, then select the Word file. ... View more

A simple fix that often (not always!) works: if your Word file is .doc, save it in Word as .docx. Conversely, if it is a .docx file, save it as .doc. ... View more

First question: do you want to add index markers in the InDesign document, or do you want to produce an index straight away, bypassing InDesign's index feature?   If the second, i.e. to create an independent index, you can try Indiscripts :: IndexMatic³ or https://creativepro.com/files/kahrel/indesign/index_independent.html   If you want to mark up the InDesign document with index markers, use https://creativepro.com/files/kahrel/indesign/index_from_wordlist.html   Since you're indexing bible books and chapters it may be better to add index markers so that you have more control over how the index is sorted.   ... View more

Very useful, thanks, Mark. ... View more

Merging Electrocardiogram and Electrocardiograms is simple: just change the topic name in the Index panel. The same for ECG and ECGs. Then regenerate the index (all this assuming that you use InDesign's index). But then merging ECG and Electrocardiogram is another matter, that's not trivial and requires a script.   If there aren't too many of these you can the following. In the generated index, starting from this:   ECG 1, 3, 5 Electrocardiogram 2, 4   change that to   ECG see Electrocardiogram Electrocardiogram 1, 3, 5 Electrocardiogram 2, 4   The us this script: https://creativepro.com/files/kahrel/indesign/index_update.html to merge the two. You can ru the script against the whole index.   It's pssible to do a script that does this this in one go, but as I said, that's not trivial.     ... View more

Strange behaviour. Is it just with language codes or also other codes that do (or should) not interfere with kerning? Discretionary hyphen, discretionary line break, text anchor, index marker, etc?   Which font editor is that, by the way? And what do you mean by xD?   ... View more

What do you mean by 'merge'? Sorted together? In that case use the sort-order field in the New Topic window. ... View more

Maybe ask the developers of your font editor what has changed. ... View more

Ugh. Ugly.   Yet another thing you could try, though I don't know if it's at all feasible with your big document. Page references live in the text, they're markers in stories. Cross-references aren't, they are part of the document but are not in the text. So what you can do is copy all the text into a new document. That works only if you don't have too many floats (independent text frames with secondary text and tables, and image frames). ... View more

@lance_7340 -- You could try to fix it in the IDML file. Not just a simple roundtrip, but a fix. It's more straightforward than it looks.   1. Export the document to IDML. 2. An IDML file is in fact a ZIP file. Unpack the file. If necessary change the IDML file type to ZIP. You'll see six folders and two files:     3. Open designmap.xml and look for the <Index> section. The section looks as follows (this sample document contains just two topics, Azerty and Qwerty; Azerty has a cross-reference to Qwerty): <Index Self="uff"> <Topic Self="uffTopicnAzerty" SortOrder="" Name="Azerty"> <CrossReference Self="u11d" ReferencedTopic="uffTopicnQwerty" CrossReferenceType="See" CustomTypeString="" /> </Topic> <Topic Self="uffTopicnQwerty" SortOrder="" Name="Qwerty" /> </Index>   Now, I don't know what that section in your file looks like but you should be able to identify the topics with missing cross-references.  How you proceed now depends on how many cross-references there are and how many of them are faulty. If there are only a handful of ill-formed items, delete them and redo them in InDesign. If that turns out not to work, delete all the lines that start with <CrossReference .   4. When you're done, save designmap.xml and zip up the files in the folder. Change the ZIP file type to IMDL and open the IDML file in InDesign. Check the state of the Index panel.   Hope this helps. I can't reproduce the problem so I've no idea whether the above works. As I mentioned earlier, if you can post your file somewhere (or the exported IDML, which will be much smaller than the 340 Mb file) I'll happily take a look.     ... View more

Hi @Anubhav M . This is a serious and continuing problem. There have been many reports in this forum, UserVoice, and non-Adobe forums. Maybe you could nudge someone to do something about it. The index feature has been neglected after it was introduced many years ago. Adobe should at least fix this crashing bug. ... View more

@Thomas_Calvin -- Show us your script, maybe you overlooked something. ... View more

A web search ("InDesign index crash") shows many reports of InDesign crashes when editing index entries, going back to CS3. No clear solutions were suggested in the few posts I checked, but it may be worth your while to checks those posts. ... View more

This problem was reported in the past in this forum, but I can't find it now and I can't remember if there was a solution.   Anyway, further to what was outlined in the links that Anubhav gave, you can try exporting the document to IDML, then open the IDML again in InDesign (which will take a while with long documents). IDML-roundtripping often fixes problems. And if you use ID 2024, make sure you update it to the latest version.   As for posting big files, you can use Dropbox or file-transfer services such as WeTransfer. I'd be interested to see your document. ... View more

UXP is still work in progress, and unfortunately the documentation, such as it is, isn't being updated as UXP develops. The first link you gave, to the OMV, is for ID 18.0. It's mentioned there that as of InDesign 18.0 the ESTK no longer reliably connects to InDesign. In my experience that's not the case, in ID 2025 it still connects fine (on Windows) and its object-model viewer works as it always did (i.e. warts an all). On MacOS you have the ESTK extension for VS Code, which since recently sports a well-working OMV. The second link, the UXP overview, was last updated in 2023, like other pages I saw last week. All out of date.   It's true that ExtendScript is based on an old JavaScript version, but that doesn't mean that you can't use it. In fact, it is very much usable.   As for deprecation, how long ExtendScript and CEP will be supported is not clear, probably even Adobe don't know how long they'll be with us. UXP (both scripting and plug-ins) is by no means finished and won't be for a while, so ES and CEP can't be cut off. Another reason for continued support is the zillions of ExtendScript scripts out in the world which Adobe wouldn't want to disable. ... View more

Do you see the same problem in ExtendScript? ... View more