-
1. Re: Unable to open InCopy file I closed yesterday: unclosed token error.
Bart Van de Wiele Jan 28, 2013 7:51 AM (in response to IowaBoy9)Hi, were you able to find what caused this? I have a client who has the same issue
Thank you
-
2. Re: Unable to open InCopy file I closed yesterday: unclosed token error.
IowaBoy9 Jan 28, 2013 8:01 AM (in response to Bart Van de Wiele)Nope. I have heard nothing. I suspect that I may have interrupted a backup procedure of some kind, rendering the file unreadable. But that is just a guess. I have since upgraded to CS6 and have not (yet) experienced this problem or the frequent crashes. My guess: CS5 was not ready for prime time.
-
3. Re: Unable to open InCopy file I closed yesterday: unclosed token error.
IowaBoy9 Feb 26, 2013 7:28 AM (in response to IowaBoy9)Anyone out there is Adobeland tracking the unclosed token error? I now have two InCopy files I cannot open in InCopy or import into InDesign. Again, the error message is "unclosed token."
This post is the first entry of the google search "fix unclosed token in InCopy file". Not promising. Do I just kiss those files goodbye?
-
4. Re: Unable to open InCopy file I closed yesterday: unclosed token error.
IowaBoy9 Feb 26, 2013 8:22 AM (in response to IowaBoy9)I am going to answer my own question. The error "unclosed token" seems like an xml error. I decided to take a chance and open the InCopy file with a text editor (BBedit). Surprise, InCopy files are xml documents. I found that the save process must have been interrupted somehow and the document was cut off with several unclosed tags, including <table>, <story> and <document> elements. BBedit has a "close current tag." I commented out the incomplete <table> because there are complex table definitions that might throw an error. I then closed the remaining open tags and saved the document. Now it opens and imports into InDesign.


