Dreaded Endnotes (CS6)

Learn / Forums / General InDesign Topics / Dreaded Endnotes (CS6)

Viewing 6 reply threads
  • Author
    Posts
    • #70634
      Hyppe Knowl
      Member

      Hi,

      I’m not going to rant about InDesign developers’ neglectful attitude towards endnotes for, like, the last 12 years. I’m sure there are some great work-arounds out there…

      I’ve got a Word doc with multiple chapters and the endnotes begin again at 1 at the beginning of each chapter. The chapters are separated by Section Breaks.

      When I place/import the doc into InDesign the numbers just run on sequentially throughout the whole book.

      I thought Section Breaks were the way to go here but InDesign doesn’t seem to recognise them. Is there anything else I can do in Word to prepare the document so that the endnotes begin again at 1?

      Or do I need to save each chapter as a separate Word document and place them individually?

      Thanks for your help!

    • #70642
      Gert Verrept
      Member

      As long as the thread between chapters isn’t needed (don’t link the frames), the footnotes will start again at 1 in the same doc. Keep in mind that the reflow can be a problem afterwards. If the thread is needed, you can keep separate files, make a pdf of each of them and make one pdf with acrobat.

    • #70645
      Hyppe Knowl
      Member

      Thanks Gert, but I already tried that :( I placed the whole document then used the BreakFrame.applescript to separate the text frames, but the notes didn’t renumber.

      Once you place a Word doc into InD the notes are no longer dynamic, right? So one the text is in InD I have no more opportunities to renumber the notes in any automated way (I’m talking about the superscript numbers throughout the chapters, not the list of notes at the end, which is a regular numbered list).

      So surely there is something I have to do in Word to ensure the numbering works…

    • #70648
      Gert Verrept
      Member

      Try this link. It’s for CC2014 but I think it works in older versions too.

      https://forums.adobe.com/thread/1565562?start=0&tstart=0

    • #70660

      That’s why I (the company I work for) have the word files tagged, macros run, and then save the word file as a tagged text file. Then we flow that in and all is well with the world.

    • #70661

      Dwayne, without giving away the actual macros you use can you give an idea of what you check? I had the worst experiences with word files created from PDFs. They are good candidates to crash Indesign!

      • #70673

        Well, we never use word files created from PDFs. We’d rather get it double-keyed. If we have it keyed, then we mark it up with the paragraph styles, and the keyboarders key in the italic, bold, small caps, etc., as well as the paragraph styles.

        If we get a word file from the author/copy editor to use, we run a macro that captures the italic, bold, etc., as well as em and en dashes. We strip out double spaces, double returns, etc. Sometimes they use basic tagging for paragraph styles that we can search and replace on.

        Then we save it as a regular text file.

        The final macro puts spaces between the periods in the ellipses, proper space between single and double quotes, adds space between quotes and superior figures, etc. We resave it as a .txt file and then flow into InDesign with xTags.

        Note: We use QuarkXpress tagging as we use xTags, and it’s easier to mark up a job with that coding than with InDesign’s coding. xTags saves us a lot of keystrokes and mistakes in keying.

    • #70745
      Ann Farr
      Member

      It’s honestly much easier (even if it takes a bit of time) to start with making separate Word documents of each chapter (I daresay there’s something more intelligent, but I just copy and paste each chapter into a new Word doc). Then set up your book as separate chapters to set up as a book when you’ve finished. This way you can keep those endnotes numbered as they are in the Word documents.

Viewing 6 reply threads
  • You must be logged in to reply to this topic.
>