You can go ahead and skip Post 1
Exporting IDML doesn't give the option of page range to export.
Try Peters or the link to Dovs post to see if that can help with your issues.
While exporting to .idml is all or nothing, you might be able to narrow down where the problem is by exporting to PDF in pieces. If you can isolate a page and frame, I'd replace the entire frame, then delete the text in it if threaded and retype that part.
I tried exporting to PDF as you suggested and here's the thing… it exported without a hitch!
So PDF is ok but IDML freezes. Given this, do you still think it's a problematic bit of text or maybe something else?
That's definitely one I haven't seen before.
Try moving the pages to a new file and see if that will export to .idml.
By the way, why are you doing .idml?
The file is being collaboratively edited in CC but I need to edit the file in CS6 to use Automatication's Multi-Find Change plugin in order to cleanup the new content I paste in from Word.
Multi-Find Change is not yet compatible with CC which is why I have to keep my feet in two boats at the moment. :-)
Copy-pasting to a new file seems promising. Is there a way to do it so I don't have to setup all the master pages, grids, etc. again?
Before doing a copy paste, just use the Move Pages command in the Pages Panel. Set up a new file the same size, and reanme the master page to something unused in the original file, like zzzz, then select all the pages in the panel inthe first file and Move Pages... Choose BEFORE page 1 in the new file so you son't swap sides, and delete the last page which should be the old blank page 1.
Thanks, Peter. That definitely seemed to help.
Beyond the page size, is there a checklist of things that don't carry over to a new document? Giving a quick glance to the file, I see I need to fix the baseline grid and footnote numbering scheme.
Once I get it looking exactly like the original, I'll try re-exporting and let you know if I have any issues.
If you re-defined Basic Paragrpaph in the original file, you'll need to fix that, too. Styles and swatch definitions use the destination defintions, if they already exist, and I guess Layers might be have the same.
I'm not sure what you are running inside the Automatication plugin -- only glanced at it briefly, but it looks likea way to organize and chain find/change queries. If I have that right, you may find you can also use Peter Kahrel's Query Manager (http://www.kahrel.plus.com/indesign/chain_queries.html) or one of the many "fix-up" scripts to correct Word formatting. I'm fond of Jongware's PrepText script (http://indesignsecrets.com/perfectpreptext-a-smart-way-to-style-local-formatting.php). Because these are both scripts rather than plugins they should work in CC if you put them in a Scripts panel subfolder for earlier version scripts if they don't run natively. Sub foler names would be like Version 7.0 Scripts or Version 6.0 Scripts to make ID interpret as CS5/5.5 or CS4, respectively. The folder name is case sensitive.
Thanks, Peter. Moving the pages over and re-doing the settings seemed to be a good workaround for the issue.
Is there a way I could provide the Adobe InDesign programmers with the troublesome file for their own testing? It would be great if they could replicate the issue and fix it for the next release.
Thanks for sending over the links to the scripts as well. I looked into them but the Multi-Find Change plugin has some advanced features that I need. Nevertheless, I'll keep those scripts in mind if I work on something less ambitious and I'm stuck in CC.