desjarlais / wordcorruptdocchecker

I created this tool to fix corrupt Word documents (non-binary, just open xml files). Mainly this applies to the .docx format. It basically just checks through a list of known corruptions and then applies a fix if it comes across one of those scenarios in the file.

wordcorruptdocchecker's Issues

Open in Word fails to open with error

When using the open in Word after a repair, the wrong file path is used, need to fix this.

Word Corrupt Doc Checker Reports Fixing a File That Won't Open in Word 2016

Word Corrupt Doc Checker reports fixing a file I will privately share with the author. It reports:
Invalid Tag: </w:txbxContent></w:pict></mc:Fallback></mc:AlternateContent> Replaced With: </w:txbxContent></v:textbox></v:shape></w:pict></mc:Fallback></mc:AlternateContent>

The fixed file won't open in Word 2016, but will open if the </v:shape> tag is replaced with a </v:rect> one.

Program does not show buttons when Windows text is magnified to 175%

Great program Brandon! I have been recommending it in this Microsoft Community thread regarding Microsoft Word errors: "Unspecified Error, word/document.xml, Line:2, Column: 0".

I have a big monitor and my eyes are having "senior" problems so in the "Customize your display" section of System settings of PC settings, I set "Change the size of text, apps and other items: 175%."

When I do this, wordcorruptdocchecker in the new Github releases, v1.2.0.4 and v.1.2.0.5 don't magnify proportionally for me. Instead the right side of the software Window with the buttons, is cut off. I do not have this problem with the Codeplex version and when I change the magnification to 100%, the problem goes away.

Here's what I see with the Codeplex version even at 175%:

Suggestion: Add a Info-Zip Zip Pretreament for Repairing the Zip Structure of the DOCX

Suggestion: Add a pretreatment step for repairing the zip structure of the DOCX with InfoZip's Zip command line app. I have found that among the free command line zip program, it is the best at repairing corrupt zip structure.

When Word Corrupt Doc Checker Finds the Document Does Not Contain Invalid XML...

When Word Corrupt Doc Checker finds that a document does not contain invalid XML, it also marks the target document as being inaccessible because it being in use, leading to a possibly false hope that releasing the file from another program might allow it to be fixed.

For example here is a recent error message from a file that the program says doesn't have invalid:

This document does not contain invalid xml.
ERROR: The process cannot access the file 'D:\Paul D Pruitt\Desktop\corrupt_docx_files\Unspecified error\math_tags\Japanese_characters_file(Fixed).docx' because it is being used by another process.

If the Program Claims to Have Repaired Bad XML and the File Still Won't Open Offer to Remove Fallback Tags

If the Word Corrupt Doc Checker is able to fix bad XML and the program is unsuccessful at opening the file in a new instance of Word, show a pop up Windows which both explains what Fallback tags are and offers to remove them.

Suggestion: Once a File is Fixed Have Microsoft Word Open It

If Word Corrupt Doc Checker is successful in repairing a bad tag file, programatically have the software open Microsoft Word or its default DOCX file handler and load the fixed file.

Suggestion: If No Invalid XML is Found, Try Opening the Non-Opening DOCX in WordPad

After zip repair and if Word Corrupt Doc Checker does not find any invalid XML, to attempt to open the file in WordPad. I have found that surprisingly once the zip structure is fixed, many if not most repairable DOCX files will open in WordPad without any further repair. I know this is not a prestigious solution, but sometimes simple is best.

Corrupt Document is Only Partially Fixed by Program

A corrupt document I recently was asked to fix, is partially repaired by the program. The problems seem to revolve around the same usual suspect tags.

I'm not sure which tags are not being properly addressed. The lack of complete result occurred even when the check box for removing all Fallback check marks was checked. I also ran the files through the program in succession more than one cycle and this didn't seem to help either.

I will send the file to the author separately.

Change the Name of the Project to the More Grammatically Correct "Corrupt Word DOCX Checker"

Word Corrupt DOC Checker sounds clumsy. This is probably because adjectives need to follow a certain order, see: http://www.gingersoftware.com/content/grammar-rules/adjectives/order-of-adjectives/[http://www.gingersoftware.com/content/grammar-rules/adjectives/order-of-adjectives/](url). Here "Corrupt" is a quality (#2 on the list), which should be in front of "Word" which is a proper adjective (#7) which properly precedes I think "DOC" which I think is a purpose or qualifier (#8 in the list order).

If the program can only work with DOCX files, the program should replace DOC with DOCX. If it works with other variants like the macro enable DOCM files, perhaps the long form, "Document" should be reintroduced, but this may be a matter of taste.

Finally Microsoft has grammar guidelines which say that when referring to Word, see: https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/publications.aspx[https://www.microsoft.com/en-us/legal/intellectualproperty/trademarks/usage/publications.aspx](url). This sentence "You may not:
use the Marks as the leading word or most prominent element in your publication, seminar, or conference title;" may be applicable to "Word Corrupt DOC Checker" which starts with "Word" clearly referring to "Microsoft Word" as its leading word.