You can view in print layout mode by following the instructions above, written by FidelmaB, by switching to 'no markup' but then you cannot view any track changes/comments. If you scroll on that white screen, it will simply revert back to draft view. If you try to view in print layout view, a blank white screen will block the text images. It will only be viewable with redlines (but no comments) in draft view. The compare markup that you save (as either a doc or docx) will experience the issues listed by other users above. If one source document was created as a doc in a 1993-2007 compatible program and one wasĬreated as a docx, and vice versa, it WILL NOT work.

Them without their last paragraphs to try and alleviate the corruption in the resulting compared doc. You cannot even copy and paste the source documents into new docs to try and get rid of the corrupting formatting and compare those.

You cannot convert them both to docx and try it that way. You cannot convert both files to doc and then run yourĬompare to fix the problem. If you have a doc and docx as the two source documents, it simply will not work and no amount of fiddling will fix the issue. Will end up being corrupted (as people have outlined above). 2008-current), then the compare document that you save as a new markup document docx) or that were created using different Microsoft versions (1993-2007 vs. If you try to create a compare document from two source documents that are different types (doc vs. (skip to the bottom if you do not want to learn exactly what is causing the issue) If you have similar issues with a file, I would look around the footnotes, maybe clearing them up helps.Ĭhanging to showing “no markup” does work for viewing the markup changes as 'accepted' throughout the document in print layout view, but it does not fix the problem for those of us that want to view insertions, changes, and comments in print layout Since attribute value dependent structure cannot be prescribed using the xsd schema, this remains an implementation restriction of Word. Once every custom mark character was moved right next to the footnoteReference tag, our documents appeared correctly. The problem in our case was that the text containing the custom mark was in a separate text run, like this Where 8 is marker showing in superscript. There were footnotes in the file with custom footnote marks, and it seamed that they are not represented in the format, how Word likes them to.Ĭustom footnote reference characters are represented in the docx file usually as We had a similar issue with some files at our company and I found what was the problem for us.

How to go into edit mode word