I have at one point already reported this as a bug but I've returned to the issue in hopes of offering some more information to the developers to work with. I'm going to offer as best an explanation for this problem here in the hopes that others can contribute as I am sure this issue has been experienced by many InCopy users. (It is a recurring - and rather irritating - problem for many of our users which causes a great deal of lost work since many of their documents contain a large number of tables. This is the ONE bug that I really wish would be fixed more than anything else.)
Also note that this issue occurs in InDesign (with less frequency) if a user tries to export out an ICML file with the following bug in it, InDesign will freeze up and need to be forced to quit.
Description:
Pasting a table into an InCopy story (when Track Changes is activated) that has an even number of cells will result in a crash when saving if text above it is deleted and a line break is added after it.
Result:
InCopy will freeze up during the saving process and the result will be an empty ICML file and loss of any work done in the document.
Steps to recreate this particular issue:
This is to simulate normal working conditions when usersmake amends to a document with a number of tables.
- Activate Track Changes in a new InCopy document.
- Add a line of text.
- Add a table with an even number of cells.
- Copy the table and then delete it from the document.
- Accept all of the changes.
- Paste the table in directly under the line of text.
- Add a line break after the table.
- Remove one or more characters from the end of the line of text.
- Attempt to save the document. (In the "Background Tasks" panel you'll see that it freezes at 50% and you'll need to force quit the application.)
What this looks like:
![Screen Shot 2016-02-24 at 13.31.50.png]()
In "Layout view" this looks like the above. In "Galley view" it looks like the image below.
![Screen Shot 2016-02-24 at 13.31.43.png]()
The ICML file:
I've managed, with some effort, to create an ICML file that replicates this error. If you open it in InCopy - this was created with CC2015 - and make any change you will be unable to save the file.
This file can be downloaded here. (Hosted on Google Drive.)
Current solutions:
The only way we've managed to resolve this particular issue is by accepting either all of the changes or the particular change that is related to the pasting in of the table.
Difference in code:
The following snippet shows what the code looks like for the end of the table when you paste in a table with an even number of cells and add a carriage return:
<ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/$ID/NormalParagraphStyle"> <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]"> <Content>above</Content> </CharacterStyleRange> </ParagraphStyleRange> </Cell> </Table> <Br /> </Change>
This shows what it looks like with an odd number of cells (note that the break tag is added as a separate change, this document does not crash InCopy):
<ParagraphStyleRange AppliedParagraphStyle="ParagraphStyle/$ID/NormalParagraphStyle"> <CharacterStyleRange AppliedCharacterStyle="CharacterStyle/$ID/[No character style]" /> </ParagraphStyleRange> </Cell> </Table> </Change> <Change Date="2016-02-24T13:05:36" ChangeType="InsertedText" UserName="InCopy User" AppliedDocumentUser="dDocumentUser0"> <Br /> </Change>
This to me says that there is a different sort of handling going on with the inserted table related to the number of cells. If you remove the <Br /> seen in the first snippet on line 8 and open the document it will behave normally. However if you exchange lines 7-9 in snippet 2 with line 8 in snippet 1 - taking in account to move the </change> tag - the document will still crash InCopy. There seems to be a correlation between the deleted text found above the table, the pasted table with the even number of cells and the line break.
I know this sounds like a rather uncommon bug, and one that requires a series of steps to create, but it only needs to occur once for a user to lose their ability to rely on the software. We work with hundreds of InCopy users (and can see this a few times a day) and it's always distressing to inform them that their work is lost and cannot be recovered simply because they inadvertently caused this bug - and then tried to save their work.
I'd be happy to hear from anyone with any input regarding this. Or even anyone who has also experienced it and whether or not they have also reported the issue to Adobe. One major drawback from this bug is that the option to submit a crash report to Adobe is not offered and so there is probably a minimal amount of feedback.
Thanks!