Skip to main content
Inspiring
July 30, 2018
Answered

InDesign crashing when exporting endnotes

  • July 30, 2018
  • 4 replies
  • 1340 views

I'm using the most current InDesign available on Creative Cloud and working on a Mac OS 10.13.2. I have a manuscript that was exporting to PDF fine until I reformatted the endnotes (just put a period after each number. So it went from 1 Endnote information (how it automatically formatted) to 1. Endnote information. That is the only difference I can identify. When the system kept crashing I tried cutting the endnotes and pasting them back in and then they exported without crashing InDesign, but all the formatting and the numbers were gone. Endnotes looked like this. <?> endnote information. I can print out the whole document up until the endnotes, but as soon as I try to print even one endnote page InDesign crashes completely. I've looked at the forum under Indexing and see that that also crashes the system. I don't know if it's a similar issue. I need to be able to export the manuscript to PDF so I'm hoping someone has a fix for this. Thanks!

This topic has been closed for replies.
Correct answer dovz34096061

Hi Dov,

I see no crashes with your sample documents.

Printing ok, exporting to PDF ok.

However, I did not work with the exact versions of your applied fonts.

( You did not provide the used ones.)

Maybe that's the point?

Regards,
Uwe


Interesting. I tried changing the font and it didn't crash. And I changed it back to the one I was using and it did crash. So, using periods in the footnotes with certain fonts crashes InDesign. (Glad at least have some more ideas about how to problem solve when there are crashes.) Thanks for looking into this!

Best,

Dov

4 replies

Participant
February 6, 2023

I had this problem--InDesign crashing every time I exported to PDF--and realized that I had accidentally included the endnote bracket in a hyperlink. I used story editor to identify which endnote had the issue and then resolved it. I hope this helps!

Inspiring
July 31, 2018

Well, I figured out that if take the period out between the end note number and the end note, InDesign doesn't crash. Hard to believe that adding a . after the end note number crashes the whole system, but it does.

Community Expert
July 31, 2018

dovz34096061  wrote

Well, I figured out that if take the period out between the end note number and the end note, InDesign doesn't crash. Hard to believe that adding a . after the end note number crashes the whole system, but it does.

Hi dovz34096061 ,

crashing because you added a period to the endnote number is not the norm.

Just tested this with my German InDesign CC 2018.1 version 13.1.0.76 on Windows 10.

Printing to e.g. PostScript was possible without crashing. Ok, you are on OS X 10.13.6. That could be a difference.

Do you have a sample document that you can share with Dropbox or a similar service? Just post the download link in your reply.

Thanks,
Uwe

Inspiring
July 31, 2018

Hi there,

I created a sample excerpt (two version) of the document that crashes with the period after the number in the endnotes (all it takes is one). It works fine when I delete it. I've fixed the full document by taking out all the periods. Curious to hear if you have any ideas why this happened.

Dropbox - endnote_glitch_tester4_ch1.indd

Dropbox - endnote_glitch_tester4_ch1fix.indd

Best,

Dov

Inspiring
July 31, 2018

Thanks. That's what it said to do for the similar issue with indexing. But I tried that and it's still crashing.

BobLevine
Community Expert
Community Expert
July 30, 2018

First things first. Update to 10.13.5

Inspiring
July 31, 2018

Right. I think you mean 10.13.6. If you have ideas that might address my problem with exporting the InDesign document I'd be very happy to hear them.

BobLevine
Community Expert
Community Expert
July 31, 2018

Whatever is current. There were some very serious issues with earlier versions of High Sierra.

As for this document, if it's only this document...export to IDML, open that and see if you can work on it without crashing. It's possible there's a bit of corruption in there that IDML can clean out.