Backsaving in InDesign 4
I have CS3 which obviously includes InDesign 3
Someone from another company has sent me a document created in InDesign 4. I'm not able to open it, so I asked if it could be backsaved to InDesign 3.
The person at the other end doesn't know how to do a backsave (if it can even be done), and I don't have ID4 so I'm not in a position to find out.
Can ID4 be backsaved to ID3? And if so, can someone tell me how, so that I can pass the messge on to an ID4 user who doesn't know
Thanks
First, lets get the versions straight. Indesign CS4 is version 6. InDesign CS3 is version 5. InDesign CS2 is version 4. InDesign CS is version 3. Very confusing, but also very important.
Exporting to .inx will work, as Eugene says, for going back ONE version, though you will lose any new-version specific features, and text will often flow differently when edited due to differences in the text engines of each version. The earlier, receiving version, should have the latest update patch applied, as well.
If they are trying to send you a CS4 file (v6) and you have CS3 (v5), rather than CS (v3) , or if they have CS2 (v4) and you vave CS, this should work for you, but if the gap is larger, it needs to be exported multiple times, cascading though the versions.
In any case, this is not a reliable workflow for collaboration if the file will be making a round-trip.
Peter
Similar Messages
-
Hello everyone. I've received some great advice so far on this problem, and wanted to outline what we're thinking of doing if anyone has any suggestions. First of all, we're a small printing company with multiple users of Indesign CS3. 80% of the time we're using it we're just opening an existing document, change a few address and name details, maybe a picture or two, exporting to PDF, then closing it. I may be wrong but I can't see too much advantage in CS5 for this very basic type of work?
So what I'm proposing to do is upgrade our main machine that most design work is done on to CS4 now, which will also get us CS5 as well (thanks for the tip!). Then I'll use Rorohikos Soxy plugin so that all our old CS3 files open in CS3 still, which will mean all our other machines will still be able to access them. We can use CS5 for new documents and take advantage of it's new features, we're small enough that it won't be a hassle to have to use that machine for the occasional job, it's not anyones personal computer. On repeat work, which is all basic stuff like business cards, we'll save back to CS3 and keep it in that version so everyone can use them.
Apart from the fact we'll be keeping all our other machines in a time warp can anyone see any major problems? I'd love to upgrade everyone to CS5 but we simply can't afford it.Sadly, I have lots and lots of experience with workflows involving multiple versions of ID (hooray, nonprofit management ).
Who works on that "main machine that most design work is done on?" Can that person be trusted to learn which tools and features don't backsave two versions well? Can that person be relied upon to pop open the double-backsave and review it in CS3 every single time? If the answer to either question is "no," it's a horrible idea.
Also, it's worth pointing out that there are very few people on the planet at the moment who really know how well the IDML backsave works. If you're not one of those people, I wouldn't want to base a workflow on it. It'll probably be fine, but I recall an error in an early InDesign manual that caused all kinds of furor on these forums when we discovered that it was an error, and that the INX export in InDesign CS really didn't offer a route to backsave to InDesign 2. So, if you're basing your future workflow on documentation or references to a particular feature in marketing materials, think twice.
But, barring that, I know that there are plenty of other people on the forums who will tell you that this workflow is a horrible idea, so if you can nail down (in a style guide!) exactly what CS5 users are and are not allowed to do, and can rely upon all CS5 users to obey those strict rules, then it'll probably kinda work without a huge amount of hair-pulling, assuming that IDML works as we expect it to. -
Hi all, I just wanted to as a question before I talk to my client.
I've been working on a 400 page product catalog for a couple months. We're now done and my client wants a final disk for their file. I know they have Indesign on the pc but I'm not sure what version. I did the file on the mac in CS5. From some of the other discussions, am I correct in telling them I really don't want to down save this document to a previous version because it could really mess up the layout? I'm not sure, at this point, if I'm going to be handling the printing or not so I'm very leery about releasing the file in the first place but more leery about downsaving it if the layout is going to be compromised. I'm very familiar with the file and someone else, just coming in, won't be as familiar with it. I'll definitely save a pdf for them but not sure about the indesign document.
Any thoughts would be helpful.
Sincerely,
AnnetteNo, this wasn't discussed before we started the project. I'm trying to be helpful to them and jump through their hoops but don't want to compromise my document.
Just so I have my ducks in a row, would I be correct in telling them that I can't save it down to another version because things might change in the file and the layout might be altered?
Annette -
Backsaving InDesign Creative Cloud files to idml files
Hi I have an ID CC doc that Im back saving to an idml file for someone to edit on, however when I do this and send it to them they are opening it and all the master pages are in the main doc over the top of my laid out work. IS there any reason for this do i need to tick something before saving as an idml file? By the way the idml file looks fine to me on my mac.
@Bruce – I think, there is nothing on your side you can do.
At least, I cannot tell, because I cannot see into the files (the IDML and the INDD as well).
And: I do not know what is the exact version of:
Your InDesign
Your OS
The recipient's InDesign
The recipient's OS
Uwe -
How to import an Quarkxpress 5 file into Indesign CS3
Hello,
I am in trouble when trying to open with Indesign CS3 for windows a file created with Quarkxpress 5 for Mac. Do you have any hint? (file attached)
thanks for supportThe Q2ID plugin is really nice as Bob suggested. If you go through there website they will convert your one document and post it for you to download, email you with the results and a discount code. Well worth the money and a very nice company to work with. I can't say enough nice things about their products.
If you have a newer version of Quark licensed I prefer use their Markztools plugin for Quark to backsave to 4. Seems to be a better conversion with InDesign's Quark import, though that could just be my impression. -
Cannot open .pdf created by InDesign CS6, can open all other .pdfs
I just got InDesign CS6 at work (I use CC at home, but my company could not afford the CC subscription). I'm on PC with the minimum specs for InDesign and Photoshop Elements (also just installed). I have never been able to print to .pdf from InDesign; the program hangs. I have been doing Export to .pdf, press quality with my printer's specs. This has been working fine, except that, on occasion, I have to export the .pdf a few times to get it to open; it will give me an "either not a supported file or damaged" error message. Up until today, I have been able to export 2-3 times and would always get a .pdf that would open.
As of today, I cannot open any .pdf at all; I get that same "not supported or damaged" error message. However, if I let my computer sit idle for about 30 minutes, it will open. In addition, after exporting, InDesign hangs on a background task of "Export " 5" and I have to close out of that task to do anything further in the program.
I have read the forums on these issues and done what I can: I have installed all updates, backsaved to earlier Acrobat versions, exported to .idml, etc. Nothing helps.
I will confess that I am not the most technically-savvy person by any means. My company is small and does not have an IT person, nor is there a budget for calling someone in, so it is up to me and my admittedly limited understanding of this software to fix this issue.
Help?You may have shown me part of the problem. I can't share one of the files I'm working on, as they're full of images and we have client protections that make sharing problematic, but I did try to recreate a new file with garbage text and graphics and that .pdf opened without any problem.
Could this be a file size issue? The files I'm working on are only 8,900 kb and 200 kb. That doesn't seem too large to me, but perhaps it's enough to cause a problem on my machine. -
Trouble printing Photoshop PDFs in InDesign
Hi, I'm using some Photoshop PDFs placed in InDesign. I can export to PDF just fine, but if I print to PDF the image drops out (just becomes a black square). Any ideas on this? I need to print to PDF to follow my printer's instructions (unfortunately). Though it's also black if I print to the Adobe PDF printer (rather than my printer's supplied virtual printer). I could switch the file to a TIF, but I hate to rasterize it. Should I try backsaving to an earlier version of Photoshop (if that's even possible)?
I'm using InDesign CS4 and Photoshop CS4. I think it's the first time I've tried PDFs from Photoshop CS4 (last magazine issue I had upgraded to InDesign CS4 but was still using Photoshop CS3).
I'm on Windows Vista.
Thanks, PhyllisNo, OPI is off, though that was a good guess!
Any other ideas?
I'm trying to find a way to downsave to Photoshop CS3 but don't see it. Do you happen to know if that's an option? (I realize this isn't a Photoshop forum but hate to split up the question.)
Thanks, Phyllis -
Data Merge Crashing with InDesign CC 9.2
Since I've updated to InDesign CC 9.2, ID crashes when attempting data merges. It's happened on both my Mac computer at work and my personal Mac laptop. I changed out my lists to make sure it wasn't something with my csv file and it still crashed.
I also opened a file that I had successfully merged before doing the update. It crashed when I attempted to create that merged document as well.
As a workaround to get my project done, I was able to make an IDML file from my CC file and open it in CS6 and successfully create my merged document from that.
Anybody else having this issue or know of any fixes or is it a wait for the next version and bug fixes thing?
Thanks in advance.Exact same issue here. InDesign CC crashes right after the merge every single time.
Backsaved file and opened in InDesign 6 – merged like a charm.
Adobe, please fix the bug in CC.
Thanks!
Process:
Adobe InDesign CC [956]
Path:
/Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/Adobe InDesign CC
Identifier:
com.adobe.InDesign
Version:
9.2.0.69 (9200)
Code Type:
X86-64 (Native)
Parent Process: launchd [131]
User ID:
502
Date/Time:
2014-01-29 11:39:53.838 -0600
OS Version:
Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:
91088 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 214878 sec
Per-App Crashes Since Last Report: 4
Anonymous UUID:
0B8A413F-AA3A-D340-5BE6-B511CB5CE317
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
*** CFRetain() called with NULL ***
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation
0x00007fff8e8c1acd CFRetain + 29
1 com.apple.CoreFoundation
0x00007fff8e8cdd57 __CFDictionaryStandardRetainValue + 71
2 com.apple.CoreFoundation
0x00007fff8e8cdb8a __CFBasicHashAddValue + 1226
3 com.apple.CoreFoundation
0x00007fff8e8d4268 CFBasicHashAddValue + 3176
4 com.apple.CoreFoundation
0x00007fff8e8d358d CFDictionaryAddValue + 189
5 com.adobe.InDesign.Document Framework
0x00000001107bb553 0x110697000 + 1197395
6 com.adobe.InDesign.Document Framework
0x00000001107bb117 0x110697000 + 1196311
7 com.adobe.InDesign.AppFramework
0x000000010ba87415 0x10ba60000 + 160789
8 com.adobe.InDesign.AppFramework
0x000000010ba868e3 0x10ba60000 + 157923
9 PublicLib.dylib
0x00000001011ae781 CSubject::Change(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*) + 81
10 com.adobe.InDesign.Document Framework
0x00000001107dab2f 0x110697000 + 1325871
11 com.adobe.InDesign.Document Framework
0x00000001107d8fd4 0x110697000 + 1318868
12 PublicLib.dylib
0x00000001010efd01 Command::DoImmediate(short) + 33
13 com.adobe.InDesign.Utilities
0x00000001087a541c 0x1087a3000 + 9244
14 com.adobe.InDesign.Utilities
0x00000001087a55a5 0x1087a3000 + 9637
15 com.adobe.InDesign.AppFramework
0x000000010ba6bb1f 0x10ba60000 + 47903
16 PublicLib.dylib
0x00000001010eefc0 CmdUtils::ProcessCommand(ICommand*) + 64
17 com.adobe.InDesign.Document Framework
0x00000001107d9c77 0x110697000 + 1322103
18 com.adobe.InDesign.DataMerge
0x000000011808c51d 0x11804d000 + 259357
19 com.adobe.InDesign.DataMerge
0x000000011808c3a1 0x11804d000 + 258977
20 com.adobe.InDesign.DataMerge
0x000000011808b1ab 0x11804d000 + 254379
21 com.adobe.InDesign.DataMergeUI
0x0000000118112fbb 0x11810e000 + 20411
22 com.adobe.InDesign.DataMergeUI
0x00000001181114e4 0x11810e000 + 13540
23 com.adobe.InDesign.Actions
0x0000000116d80189 0x116d69000 + 94601
24 com.adobe.InDesign.DataMergeUI
0x000000011812d866 0x11810e000 + 129126
25 com.adobe.InDesign.AppFramework
0x000000010ba87415 0x10ba60000 + 160789
26 com.adobe.InDesign.AppFramework
0x000000010ba868e3 0x10ba60000 + 157923
27 PublicLib.dylib
0x00000001011ae781 CSubject::Change(IDType<ClassID_tag>, IDType<PMIID_tag> const&, void*) + 81
28 com.adobe.InDesign.DV_Widgets
0x00000001166b1e8c 0x1166ab000 + 28300
29 com.adobe.InDesign.DV_Widgets
0x00000001166b29a3 0x1166ab000 + 31139
30 com.adobe.InDesign.DV_Widgets
0x00000001166b2a61 0x1166ab000 + 31329
31 DV_WidgetBinLib.dylib
0x000000010005c0cc DVIconSuiteButtonView::ChangeControls(short) + 92
32 DV_WidgetBinLib.dylib
0x000000010005d709 0x100037000 + 157449
33 com.adobe.dvaui.framework
0x00000001009dcebf dvaui::controls::UI_ControlView::SendControlMessages(dvacore::utility::SharedFunctions<bo ost::shared_ptr<boost::function<void (dvaui::ui::MessageT<dvaui::ui::UI_Node>*)> > > const&, dvaui::ui::MessageT<dvaui::ui::UI_Node>*) + 63
34 com.adobe.dvaui.framework
0x00000001009b986c dvaui::controls::UI_Button::SendButtonChangedMessage(dvacore::utility::Flags<unsigned char>) + 76
35 com.adobe.dvaui.framework
0x00000001009b89dc dvaui::controls::UI_Button::PerformAction(bool, dvacore::utility::Flags<unsigned char>, bool) + 108
36 com.adobe.dvaui.framework
0x00000001009b9412 dvaui::controls::ButtonInputCapture::End() + 146
37 com.adobe.dvaui.framework
0x0000000100bbc7c7 dvaui::ui::EventCapture::InvokeEnd(bool) + 135
38 com.adobe.dvaui.framework
0x0000000100bc5e75 dvaui::ui::UI_NodeManager::EndInputCapture(bool) + 101
39 com.adobe.dvaui.framework
0x00000001009b9609 dvaui::controls::ButtonInputCapture::DoMouseEvent(dvaui::ui::MouseEvent const&) + 281
40 com.adobe.dvaui.framework
0x0000000100bd018a dvaui::ui::UI_Node::UI_DispatchCapturedMouseEvent(dvaui::ui::MouseEvent const&) + 650
41 com.adobe.dvaui.framework
0x0000000100bcf5da dvaui::ui::UI_Node::UI_DispatchMouseEventToTarget(dvaui::ui::UI_Node*, dvaui::ui::MouseEvent const&, bool) + 1098
42 com.adobe.dvaui.framework
0x0000000100bcf155 dvaui::ui::UI_Node::UI_DispatchMouseEvent(dvaui::ui::MouseEvent const&, bool) + 69
43 com.adobe.dvaui.framework
0x0000000100c4919a dvaui::ui::OS_View::UI_DispatchPlatformMouseEvent(dvaui::ui::MouseEvent const&, bool) + 666
44 com.adobe.dvaui.framework
0x0000000100c48cfd dvaui::ui::OS_View::UI_DispatchPlatformMouseClickEvent(dvaui::ui::OS_Event const&) + 477
45 com.adobe.dvaui.framework
0x0000000100c475e8 dvaui::ui::OS_View::UI_DispatchEvent(dvaui::ui::OS_Event*) + 120
46 com.adobe.dvaui.framework
0x0000000100c47546 dvaui::ui::OS_View::UI_HandleOSEvent(dvaui::ui::OS_Event*) + 22
47 com.adobe.dvaui.framework
0x0000000100c487f9 dvaui::ui::OS_View::UI_HandlePlatformEvent(NSEvent*) + 57
48 com.adobe.dvacore.framework
0x0000000100679164 int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 68
49 com.adobe.InDesign.Application UI
0x000000010faf83a2 0x10f9ca000 + 1237922
50 com.adobe.dvacore.framework
0x00000001006791fc void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 140
51 com.adobe.dvacore.framework
0x000000010067ad6d void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 125
52 com.adobe.dvaui.framework
0x0000000100c538ba dvaui::ui::OS_NodeTimerData::RemoveTimer() + 28442
53 com.apple.AppKit
0x00007fff9051a5d6 -[NSWindow sendEvent:] + 7053
54 com.adobe.owl
0x0000000100481690 0x10044a000 + 226960
55 com.apple.AppKit
0x00007fff90516644 -[NSApplication sendEvent:] + 5761
56 com.adobe.dvaui.framework
0x0000000100c4cd8e dvaui::ui::OS_NodeTimerData::RemoveTimer() + 1006
57 com.adobe.exo.framework
0x00000001028d2420 exo::app::OS_AppBase::SetResetMenuShortcutsOnClose(bool) + 800
58 DV_WidgetBinLib.dylib
0x00000001000c1095 0x100037000 + 565397
59 com.adobe.InDesign.Application UI
0x000000010fafdbcc 0x10f9ca000 + 1260492
60 com.apple.AppKit
0x00007fff9042c21a -[NSApplication run] + 636
61 com.adobe.exo.framework
0x00000001028d1e58 exo::app::OS_AppBase::RunEventLoop() + 56
62 com.adobe.InDesign.AppFramework
0x000000010bb6f8d3 0x10ba60000 + 1112275
63 com.adobe.InDesign.AppFramework
0x000000010bb6e9b2 0x10ba60000 + 1108402
64 com.adobe.InDesign
0x0000000100001dbc main + 412
65 com.adobe.InDesign
0x0000000100001bb4 start + 52
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib
0x00007fff983cdd16 kevent + 10
1 libdispatch.dylib
0x00007fff983dbdea _dispatch_mgr_invoke + 883
2 libdispatch.dylib
0x00007fff983db9ee _dispatch_mgr_thread + 54
Thread 2:
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccaff3 _pthread_cond_wait + 927
2 com.apple.CoreServices.CarbonCore
0x00007fff95390406 TSWaitOnConditionTimedRelative + 163
3 com.apple.CoreServices.CarbonCore
0x00007fff952f2a98 MPWaitOnQueue + 252
4 PMRuntime.dylib
0x0000000101682be1 0x101681000 + 7137
5 com.apple.CoreServices.CarbonCore
0x00007fff953677e0 PrivateMPEntryPoint + 58
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 3:: com.apple.CFSocket.private
0 libsystem_kernel.dylib
0x00007fff983cd322 __select + 10
1 com.apple.CoreFoundation
0x00007fff8e933f46 __CFSocketManager + 1302
2 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
3 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 4:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 5:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 6:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 7:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 8:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 9:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 10:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 11:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.Font Manager
0x0000000115f26d1b 0x115e77000 + 720155
3 com.adobe.InDesign.Font Manager
0x0000000115f2510b 0x115e77000 + 712971
4 com.adobe.InDesign.Font Manager
0x0000000115f23624 0x115e77000 + 706084
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 12:: com.apple.NSURLConnectionLoader
0 libsystem_kernel.dylib
0x00007fff983cb686 mach_msg_trap + 10
1 libsystem_kernel.dylib
0x00007fff983cac42 mach_msg + 70
2 com.apple.CoreFoundation
0x00007fff8e8ef233 __CFRunLoopServiceMachPort + 195
3 com.apple.CoreFoundation
0x00007fff8e8f4916 __CFRunLoopRun + 1078
4 com.apple.CoreFoundation
0x00007fff8e8f40e2 CFRunLoopRunSpecific + 290
5 com.apple.Foundation
0x00007fff93962546 +[NSURLConnection(Loader) _resourceLoadLoop:] + 356
6 com.apple.Foundation
0x00007fff939c0562 __NSThread__main__ + 1345
7 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
8 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 13:
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3 com.adobe.InDesign.AppFramework
0x000000010bb59077 0x10ba60000 + 1020023
4 com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5 com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6 com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7 com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 14:
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3 com.adobe.InDesign.AppFramework
0x000000010bb59077 0x10ba60000 + 1020023
4 com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5 com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6 com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7 com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 15:
0 libsystem_kernel.dylib
0x00007fff983cd386 __semwait_signal + 10
1 libsystem_c.dylib
0x00007fff8dd507c8 nanosleep + 163
2 com.adobe.InDesign.Support for JavaScript
0x0000000113a517e8 0x1139fe000 + 341992
3 com.adobe.InDesign.Support for JavaScript
0x0000000113a38a0e 0x1139fe000 + 240142
4 com.adobe.InDesign.Support for JavaScript
0x0000000113a513a5 0x1139fe000 + 340901
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 16:
0 libsystem_kernel.dylib
0x00007fff983cd2aa __recvfrom + 10
1 ServiceManager-Launcher.dylib
0x000000011090d1a1 0x1108f5000 + 98721
2 ServiceManager-Launcher.dylib
0x000000011090c4bc 0x1108f5000 + 95420
3 ServiceManager-Launcher.dylib
0x000000011090b55e 0x1108f5000 + 91486
4 ServiceManager-Launcher.dylib
0x000000011090b5cc 0x1108f5000 + 91596
5 ServiceManager-Launcher.dylib
0x00000001109061c4 0x1108f5000 + 70084
6 ServiceManager-Launcher.dylib
0x0000000110906bde 0x1108f5000 + 72670
7 ServiceManager-Launcher.dylib
0x0000000110906aeb 0x1108f5000 + 72427
8 ServiceManager-Launcher.dylib
0x000000011090a24e 0x1108f5000 + 86606
9 ServiceManager-Launcher.dylib
0x000000011090a392 0x1108f5000 + 86930
10 ServiceManager-Launcher.dylib
0x000000011090a14d 0x1108f5000 + 86349
11 ServiceManager-Launcher.dylib
0x000000011090a0c6 0x1108f5000 + 86214
12 ServiceManager-Launcher.dylib
0x00000001108f87d6 0x1108f5000 + 14294
13 ServiceManager-Launcher.dylib
0x00000001108fc9c5 0x1108f5000 + 31173
14 ServiceManager-Launcher.dylib
0x000000011090ad2c 0x1108f5000 + 89388
15 ServiceManager-Launcher.dylib
0x000000011090ce63 0x1108f5000 + 97891
16 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
17 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 17:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 18:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 19:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 20:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 21:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 22:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 23:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 24:: UxTech Queue ThreadController
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.SettingsInCloud
0x000000010c5a363b 0x10c47d000 + 1205819
3 com.adobe.InDesign.SettingsInCloud
0x000000010c5a1abb 0x10c47d000 + 1198779
4 com.adobe.InDesign.SettingsInCloud
0x000000010c59ffd4 0x10c47d000 + 1191892
5 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
6 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
7 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 25:
0 libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1 com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2 com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3 com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4 com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 26:
0 libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1 com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2 com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3 com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4 com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 27:
0 libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1 com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2 com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3 com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4 com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 28:
0 libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1 com.adobe.PDFL
0x000000012a254356 0x129e45000 + 4256598
2 com.adobe.PDFL
0x000000012a254df2 0x129e45000 + 4259314
3 com.adobe.PDFL
0x000000012a255364 0x129e45000 + 4260708
4 com.adobe.PDFL
0x000000012a254b06 0x129e45000 + 4258566
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 29:
0 libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1 com.adobe.ACE
0x0000000101b263c7 ACEHasFeature + 533191
2 com.adobe.ACE
0x0000000101b25dc1 ACEHasFeature + 531649
3 com.adobe.ACE
0x0000000101b2567e ACEHasFeature + 529790
4 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
5 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 30:
0 libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1 com.adobe.ACE
0x0000000101b263c7 ACEHasFeature + 533191
2 com.adobe.ACE
0x0000000101b25dc1 ACEHasFeature + 531649
3 com.adobe.ACE
0x0000000101b2567e ACEHasFeature + 529790
4 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
5 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 31:
0 libsystem_kernel.dylib
0x00007fff983cb6c2 semaphore_wait_trap + 10
1 com.adobe.ACE
0x0000000101b263c7 ACEHasFeature + 533191
2 com.adobe.ACE
0x0000000101b25dc1 ACEHasFeature + 531649
3 com.adobe.ACE
0x0000000101b2567e ACEHasFeature + 529790
4 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
5 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 32:: MPSupport Worker
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 MultiProcessor Support
0x00000001327aafbb 0x132765000 + 286651
3 MultiProcessor Support
0x00000001327aae73 0x132765000 + 286323
4 MultiProcessor Support
0x00000001327caf04 0x132765000 + 417540
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 33:: MPSupport Worker
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 MultiProcessor Support
0x00000001327aafbb 0x132765000 + 286651
3 MultiProcessor Support
0x00000001327aae73 0x132765000 + 286323
4 MultiProcessor Support
0x00000001327caf04 0x132765000 + 417540
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 34:: MPSupport Worker
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 MultiProcessor Support
0x00000001327aafbb 0x132765000 + 286651
3 MultiProcessor Support
0x00000001327aae73 0x132765000 + 286323
4 MultiProcessor Support
0x00000001327caf04 0x132765000 + 417540
5 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
6 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 35:
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3 com.adobe.InDesign.AppFramework
0x000000010bb59128 0x10ba60000 + 1020200
4 com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5 com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6 com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7 com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 36:
0 libsystem_kernel.dylib
0x00007fff983cd0fa __psynch_cvwait + 10
1 libsystem_c.dylib
0x00007fff8dccafb9 _pthread_cond_wait + 869
2 com.adobe.InDesign.AppFramework
0x000000010bb59a82 0x10ba60000 + 1022594
3 com.adobe.InDesign.AppFramework
0x000000010bb59077 0x10ba60000 + 1020023
4 com.adobe.InDesign.AppFramework
0x000000010bb565f7 0x10ba60000 + 1009143
5 com.adobe.InDesign.AppFramework
0x000000010bb5a61d 0x10ba60000 + 1025565
6 com.adobe.InDesign.AppFramework
0x000000010bb5a5a3 0x10ba60000 + 1025443
7 com.adobe.InDesign.AppFramework
0x000000010bb5a562 0x10ba60000 + 1025378
8 com.adobe.boost_threads.framework
0x000000010108f6d4 boost::thread::start_thread() + 436
9 libsystem_c.dylib
0x00007fff8dcc6772 _pthread_start + 327
10 libsystem_c.dylib
0x00007fff8dcb31a1 thread_start + 13
Thread 37:
0 libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2 libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3 libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 38:
0 libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2 libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3 libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 39:
0 libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2 libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3 libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 40:
0 libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2 libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3 libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 41:
0 libsystem_kernel.dylib
0x00007fff983cd6d6 __workq_kernreturn + 10
1 libsystem_c.dylib
0x00007fff8dcc8f1c _pthread_workq_return + 25
2 libsystem_c.dylib
0x00007fff8dcc8ce3 _pthread_wqthread + 412
3 libsystem_c.dylib
0x00007fff8dcb3191 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00007fff8ea4d918 rbx: 0x0000000000000000 rcx: 0x00007fff8ea43920 rdx: 0x0000000000000000
rdi: 0x0000000000000000 rsi: 0x0000000000000000 rbp: 0x00007fff5fbfce60 rsp: 0x00007fff5fbfce50
r8: 0x0000000000000000 r9: 0x0000000110834d72 r10: 0x0000000110834d72 r11: 0x0000000110834d71
r12: 0x0000000131cd0000 r13: 0x0000000000000000 r14: 0x0000000131cd0000 r15: 0x0000000000000000
rip: 0x00007fff8e8c1acd rfl: 0x0000000000000246 cr2: 0x0000000127355000
Logical CPU: 1
Binary Images:
0x100000000 -
0x100005fff +com.adobe.InDesign (9.2.0.69 - 9200) <B7C09BD6-74AF-323E-8D22-D5E1F7965643> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/Adobe InDesign CC
0x10000c000 -
0x10000eff7 +com.adobe.InDesign.InDesignModelAndUI (9.0 - 0) <612870BE-869E-3165-9714-55F900A66BCC> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/InDesignModelAndUI.framework/Versions/A/InDesignModelAndUI
0x100014000 -
0x10001cfff +com.adobe.coretech.adobesplashkit (AdobeSplashKit Version 1.0 - 1.0) <65BFDA83-4121-3D12-9BBE-9F4FF1DB3D6A> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/Frameworks/AdobeSplashKit.framework/Versions/A/AdobeSplashKit
0x100025000 -
0x10002ffff +ASLSupportLib.dylib (1) <1039F962-C495-36E4-B868-3DA5C43E3EBF> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/ASLSupportLib.dylib
0x100037000 -
0x10013aff7 +DV_WidgetBinLib.dylib (1) <57491245-3B90-3D4B-B4B6-4441EE325E3C> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/DV_WidgetBinLib.dylib
0x1001d5000 -
0x10021aff7 +TextPanelLib.dylib (1) <4B30610F-C637-3910-A413-C40325795CAD> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/TextPanelLib.dylib
0x100237000 -
0x100398fff +WidgetBinLib.dylib (1) <50EE77D3-591B-306F-9D62-2026938837EE> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/MacOS/WidgetBinLib.dylib
0x10044a000 -
0x100616fff +com.adobe.owl (AdobeOwl version 5.0.24 - 5.0.24) <1C99AA07-E73F-370B-82FA-01C1C4AAF97D> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/Frameworks/AdobeOwl.framework/Versions/A/AdobeOwl
0x100659000 -
0x10089dfff +com.adobe.dvacore.framework (7.0.849324 - 7.0.849324.0) <08EB97C1-03E5-3C1B-B154-C886807BC6F1> /Applications/Adobe InDesign CC/Adobe InDesign CC.app/Contents/Frameworks/dvacore.framework/Versions/A/dvacore
0x100964000 -
0x100df1ff7 +com.ad -
Indesign CC export to .idml not reliable
I just sent a large financial document to print. Its 132 pages.
The printer (like every printer I work with) has not purchased CC yet and apparently refuses to.
No prob - Ill just save as an .idml so they can open it in CS6, right?
WRONG! DEAD WRONG!
Turns out that when I save as .idml and its opened in CS6, random acts of weirdness occur.
Namely, lines applied to Indesign Table Cells can disappear. That's right. In a 132 page FINANCIAL document, the client is looking at a proof and asking why the lines are not in some places. Im lucky it was caught (by the client) before going to print.
I had no idea what the problem was because my files were fine. But I exported as .idml and opened it up in CS6 and... Lo and Behold, the lines were missing again in the exact same areas.
In the past I have just exported to .idml and sent to print, but I cannot have any faith in that process anymore. I encourage any and all to export to .idml, then open it up in CS6 and review every last line, break, color, etc. THEN send the CS6 file to the printer.
Or better yet, maybe dont use CC at all, which is what Im contemplating.I must thank you Bobby. Friday is our donut and pastry morning and when I came in and saw your ridiculous post, I brought the entire team in to get a good laugh.
Im not sure if you use Indesign in a professional capacity, or even work with printers or not, (from your comments and assumptions I would say no), but ever since there has been a way to backsave, it is exactly what has been done when sending files to print. Printers are notorious late adopters of new versions (for good reason). For years and years EVERY SINGLE printer we work with - whether its hear in San Diego, printers in New York, the Mid-West or even in China - every time we get a new version of the software and send it to print we have been asked to backsave the file. Hell, some print shops are TWO versions back! This is standard procedure and has been for over a decade. Sorry if you dont know this, but that is reality.
Also, your assumptions show a lack of understanding of a modern design studio. See, when you have governmental agencies, multi-national energy company's, Casinos with over 240 locations world wide, Hospitals, biotech companies, etc etc as clients, it is 8 times out of 10 the CLIENT who choses the printer - like I mentioned above. Additionally, (since apparently you are not aware of this), the client often does not make their final decision on which printer to select until WELL AFTER the project is underway. In this particular case we found out 3 days before it was supposed to go to print what printer it was. So your naive "the first thing you do when working with a new printer is pick up the phone" comment is truly uneducated and is very telling about your experience in the field.
Futhermore, anytime I come across a printer that requests PDFs (its extremely rare - we usually work with professional high-end printers with actual pre-press departments, not Mickey Mouse outfits that want me to do their prepress for them) - The first thing I do is call my client and ask them "you got a good price on printing didnt you." Of course they did because their printer wants ME to prep their files for them - so I need to go back to the client and raise my rates. Heck, I can do pre-press, I used to use a stat camera creating chokes and traps back in the day - then did the same with Illustrator - but that is not the role of the modern design studio, its the PRINTES responsibility. All respectable professional print shop wants to have control of the files so they can make adjustments for their presses and even humidity - i.e. Native Files.
Now, I originally made this post so that other professionals would be aware of the flaw in backsaving - a flaw that DID NOT EXIST BEFORE. I know this from years of experience. You comment that you dont care if I have been doing this for 240 years... but im still wrong, is the height of arrogance. I mean, do you even hear yoursel?
I was under the impression that this was the place that real design professionals discussed Indesign. Apparently its the place for people to rack up 28 thousand comments posting uneducated drivel. -
Backsave in 6 (PC) mutates to a zip file
I need to backsave InDesign 6 (PC) file for use with 5, but the export to idml ends up as a zip file after being emailed. How can I prevent this?
.idml IS a zip archive, but with the .idml extension instead of .zip, but it's possible that your email program re-zipped it when you mailed it. Did they attempt to unzip at the other end? If they see a whole bunch of folders and a designmap.xml file they can just rename the zip file to .idml and it should be OK. Otherwise, they should see the original .idml that can be extracted and opened.
-
InDesign Content Manager 'Cannot open' error message
We are attempting to open InDesign version 2, 'indd' files, with version 3.0.1. We are getting the 'Cannot open xxxx.indd. Please upgrade your plugins to their latest versions, or upgrade to the latest version of Adobe InDesign'.
We are able to use a workaround found on the Adobe site by opening the file in version 2, exporting to an .inx file and then opening/saving using version 3.0.1. This is very cumbersome as we have many files in the older format.
Why can't we just open the file directly in version 3.0.1 as it seems like the program should be backwards compatible? Are there additional plug-ins or updates that need to be loaded?
Thanks very much for your help!It sounds like you're being misled by Adobe's misleading version numbering. InDesign CS is 3.0.something. InDesign CS2 is 4.0.something. If the files were actually from pre-CS Version 2, then they ought to open up in CS 3.0.1 without exporting. My exposure to InDesign 2 was pretty minimal, so there might be something here that I don't know about opening up InDesign 2 files in InDesign CS (3). So, if my suspicions are correct, then the workaround you're using is actually backsaving from a newer version (CS2 version 4.0.X) to an older version (CS version 3.0.X).
-
Will InDesign open my Quark files?
Q: Will InDesign open my Quark files?
A: InDesign can open Quark 3 and 4 files. Quark encrypted version 5 and 6 files just so InDesign can't open them. If you can back save these newer Quark files to version 4 they can be opened by InDesign.
If you don't have all versions of Quark to backsave to version 4, Markwarz Q2ID (QuarkXPress to Adobe InDesign) offers users a quick and easy way to convert QuarkXPress content into a new Adobe InDesign document.
http://www.markzware.com/q2id/
Dave, can this be made sticky?An EPS caution for imported XPress docs
InDesign 3 (CS1) has a bug that was never fixed which turns on the non-printing attribute for random EPS graphics in an imported XPress doc. You can spot these graphics in Overprint Preview mode and you can use the Attributes palette to fix them individually. Dave Saunders also wrote a nice script that will turn off the Non-Printing Attribute for every graphic in the document (ie, make *everything* print).
//DESCRIPTION: Uncheck ALL nonprinting attributes checkboxes
//Script Author: Dave Saunders
if (app.documents.length != 0) {
myGraphs = app.activeDocument.allGraphics;
myLim = myGraphs.length;
for (i = 0; myLim > i; i++) {
myGraphs[i].nonprinting = false
myPIs = app.activeDocument.allPageItems;
myLim = myPIs.length;
for (i = 0; myLim > i; i++) {
myPIs[i].nonprinting = false
Theoretically, this bug has been fixed in ID4. -
Hi mr. expert,
I am looking for at very specific feature /(script). I know a company has allready made it (here in Denmark) but it is very expensive and mayby there is something similar out there.
What I want is the following:
We have a lot of basic texts and it is quite difficult to keep track of them.
The text are basic texts and we use the same text in all our brochures, catalogues, flyers etc. SO if we have a small text edit (change a word) I have to open all my Indesign files (app. 20-25) and change the little specific word. (it is getting very difficult to remember where to edit)
Solution: a EXCEL/WORD or other document where we collect ALL our text - a master document and we ONLY have to made the corrections in here and it automatically transfer the correction to the indesign documents which uses the same text where there are corrections. It menas that the master document has to be linked up to indesign.
The danish company has done that, but is there a script out there, which can manage my request?Well, translation memory apps can be expensive, like SDL/Trados, although there are some free/open source ones like OmegaT that will work with InDesign. Either one is overkill unless you spend a measurable amount of your time on translations of documents. However, if you're spending any signficant time on handling translated documents, then the hours spent on setting this workflow up will pay for themselves absurdly quickly. (SDL/Trados costs so much that I wouldn't suggest it to you unless your job was more than 60% localization, or if there were more people like you updating translated documents in your organization. You may want to talk to them anyways, if I'm underestimating your translation workload.)
But, here's the way it works: Let's say that you have an English master document in ID. Just hypothetically, let's also assume that your translation provider is capable of delivering translations in some way that lets a single English sentence be matched to its translation. (There's lots of file formats and options here, which I will detail for you if you're interested. Also, if all you have is Word/Excel files of these translations, it's not hard to align them into a bilingual format that can be used here.)
Then, your superior tells you that there's a changed graphic on the English document. You then open up the English doc, note the new graphic, and export an INX file. These files were originally meant for backsaving to previous versions of ID, I think, but they're useful if you need another app to parse an InDesign file.
Then, you run that INX file through your translation memory app. It automatically finds matching sentences and pastes 'em in. If something isn't a perfect match - say, they changed a word or moved some punctuation, or if a sentence has been signifcantly revised - your TM app will point it out, and inform you of how much it's changed (a percentage usually based on a new character count).
So, you only have to make graphics updates to one file, and all the rest of the text for the translations flows straight in. Often, some adjustment of the size of text boxes is necessary, but if you set up your ID files well, a twenty-language update can be completed in forty minutes. (That's obviously a best-case scenario.) Does this make any more sense now?
My advice against using layers to manage translations is simply because a) people who do this usually rely on manual recordkeeping to manage their translated documents, which is okay for small projects but usually falls apart completely when you try to scale it up. If your organization plans on 0% growth in international markets, sticking with manual management of translated documents will work great for you. However, let's just say that all of a sudden your translation needs skyrocket (big EU contract?), and you need to move your old-fashioned I-keep-track-of-everything-in-spreadsheets workflow to a contemporary translation workflow with structured authoring, legally-mandated controlled language, et cetera. In that situation, trying to tease apart five-language files into one-language files is tedious but doable, if and only if you've exhibited perfect information hygiene.
As I work on big localization projects on a regular basis, I often inherit other people's manually-managed documents, and part of my reputation is built upon being able to figure out how to revamp a workflow like this. Basically, I do detective work to reconstruct other people's philosophies of how duct tape and Perl hold the world together. In the last decade, I've only seen one layers-and-spreadsheets workflow that wasn't pure hell to untangle.
However, the method you describe is actually okay; if it works the way you say it does, and you document your actions, and you disappeared without a trace, then when I was brought in to clean it up, your workflow might be the second such non-hellish workflow in my professional career. If your translation needs are minimal, and it's only a small part of what you need to do with ID, then I see no reason to try to talk you into spending a lot of money and time on a workflow revamp with translation memory tools. However, that's what you are asking for, really - a translation memory tool written in Javascript, sitting on top of a multilingual InDesign document. Doing this is currently barely within my scripting abilities, but since I know that I'd be needlessly duplicating a custom solution for which there are already a few mature commercial applications and some general industry standards, I'd be reluctant to agree to such a development project without a ludicrous hourly rate and a disclaimer signed by all parties "We understand that the custom workflow we're asking you to develop is a step back fifteen years in time, and will furthermore be difficult to integrate with commonly accepted standards should we ever elect to drag our workflow, kicking and screaming, into the 21st century."
Or, if you wanted to do it the cheap way, do you know that you could just check the box upon placing a Word or Excel file that treats it as a link, and lets you update it like any graphic link? After writing all of the above novel, I just realized that there is in fact a way for you to get what you want, without changing your workflow at all. -
I ran into a little backsaving snafu when dealing with a client's CS5.5 file the other day I figured I would share.
The document barked at me with the missing plugins in standard fashion. I requested the client backsave the file (a 96 page instruction manual with around 300 various placed vector graphics). The IDML came in and I got similar barking from InDesign in a slightly different shaped dialog box with the same (slightly different count) plugin request. This time the dialog box rather than accepting the Okay button to dismiss the error persisted seemingly regardless of how many times I hit Okay.
Turns out a couple of the placed links were also CS5.5 InDesign files that were scattered about the document. The presence of the linked files precluded opening of the document. Several force quits, the download of the trial version of CS5.5 to backsave the links, open the links, convert to INDD 5.0, and a couple cups of coffee got me back in business.
Possibly had I hit okay a few hundred times it would have continued with the full conversion and brought up a corresponding few hundred "Failed to Import File" errors, but the human in me figured that after the first 50 or so unsuccessful Okay's to the plugin error that I would have to force quit to get rid of the offending dialog box.
Backsaving once again is a blast. Can't wait for CS6 so I can merit actually blowing the $5000 on upgrades. CS5.5 still brings doesn't bring enough to the table for our print workflow to merit the upgrade.macinbytes wrote:
I ran into a little backsaving snafu when dealing with a client's CS5.5 file the other day I figured I would share.
The document barked at me with the missing plugins in standard fashion. I requested the client backsave the file (a 96 page instruction manual with around 300 various placed vector graphics). The IDML came in and I got similar barking from InDesign in a slightly different shaped dialog box with the same (slightly different count) plugin request. This time the dialog box rather than accepting the Okay button to dismiss the error persisted seemingly regardless of how many times I hit Okay.
Turns out a couple of the placed links were also CS5.5 InDesign files that were scattered about the document. The presence of the linked files precluded opening of the document. Several force quits, the download of the trial version of CS5.5 to backsave the links, open the links, convert to INDD 5.0, and a couple cups of coffee got me back in business.
Possibly had I hit okay a few hundred times it would have continued with the full conversion and brought up a corresponding few hundred "Failed to Import File" errors, but the human in me figured that after the first 50 or so unsuccessful Okay's to the plugin error that I would have to force quit to get rid of the offending dialog box.
Backsaving once again is a blast. Can't wait for CS6 so I can merit actually blowing the $5000 on upgrades. CS5.5 still brings doesn't bring enough to the table for our print workflow to merit the upgrade.
I suggest that you post a request for improving the error message here: wish It's likely since the incompatible version of the placed files is detected, it's possible to make the message accurately describe the problem.
HTH
Regards,
Peter
Peter Gold
KnowHow ProServices -
[Perm]Opening InDesign CS with InDesign 2.0.2
A client is saving InDesign CS back to 2.0 for me in prepress. However, I get a message upon opening concerning "InDesign Content Manager" Suggestion is to upgrade plug-ins and/or InDesign to newest upgrade. I have upgraded to 2.0.2, but have no idea if this component is a 3-rd party plug in, a component of Indesign that didn't get installed, or what. Please help!
>If you could backsave and your job was screwed up because ID2 could not handle the way ID3 did its job, I'm sure you and all the others that are whining about not being able to backsave would be whining that Adobe ruined your job and who is going to pay for it and why would they put the backsave function in an app if it did not save bakward with no errors.<<br />
Buko, I suspect you didn't really read Jill's comments very close. She's not talking about back saving a final to go to Kinkos or any other printer. She's just talking about sharing documents with other users (in an education environment).
I'm truly hoping Adobe will provide some kind of legacy file support at some point very soon because we can't really afford to upgrade until then. We share files with too many other offices that need to be editable on the other end. Venders can take PDFs and that is no problem--I don't quibble with that at all. But as soon as I start using my already installed version of ID CS, none of the other designers in my building or in our other international offices can work on a file that I produce. I'm itching to dig into and make use of ID CS's new features, but can't even convert a document for a quick edit because that document would then become unusable for everyone else. (Of course I can't start using ID CS for another unrelated reason--the Managing Editor hasn't released TruEdit for CS yet, and it would destroy our editing workflow to move to CS without InCopy.)
Just an overall observation:
I suspect that backsaving was not an issue on previous versions of ID because so many of the current users were not involved with previous versions. I was one of the few who used version 1, and I was also one of the few who truly incorporated 1.5 into their workflow, and I put up with the inconvenience of being totally incompatible with everyone else. I'm just not able to do it now, and I'm chomping at the bit, totally frustrated at not being able to reach that tantilizing carrot (the newest features in CS) because it's held out of reach by workflow issues.
What good is a user to user forum if people can't vent a little. It isn't a stupid request or an invalid frustration, and the continual harping on it is almost always started by someone I haven't noticed on the forum before (possibly new users), meaning to me that this is becoming a serious concern for the Adobe quest to gain market share in the page layout industry. I've read all of the topics on this issue and I'm a little annoyed at the continual harsh comments back to people who are simply airing a frustration. People have a right to be upset, and those of us who are long time users on this forum should at least welcome their point-of-view instead of snapping at them.
Maybe you are looking for
-
Hi! I am having a problem with a ASA 5505. The users on the inside cannot access internet for the most of the time. When i looked over the configuration and tried a few changes i got out to internet about 5 seconds every 30 minute or so. Very strange
-
Unable to Import the ID objects in PI 7.0
Hi, I have installed a new PI 7.0 server which is on local SLD. I also have old PI 7.0 in which all the scenarios are configured. I am trying to import the scenarios from the old PI 7.0 to new PI 7.0. Both the servers are on local SLD and on differen
-
Win7 Incompatible with Adobe Acrobat 6.0
Hello! I have a big question here. Currently I have Adobe Acrobat 6.0 Standard software that was normally apply with Windows XP Pro. However, when I upgraded my Windows XP Pro to Windows 7 – I found out Windows 7 has a known issue with Adobe Acrobat
-
Hi all, is it possible to photo stitch in iPhoto8?
-
Is it Possible to View Album info on my TV
I have all the necessary gear to view videos and photos on my TV (and can view) but can't seem to get the album art or song title etc. to come up on the TV monitor while playing music. Is there something i'm doing wrong or is it evan posible? If it's