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

[desjarlais]

Thanks for the report. The reason the default Fix fails is because the code I wrote is assuming the textbox (txbxContent) is a shape, not a rectangle. I'll see if I can adjust the logic to handle both shape and rectangle scenarios.

The option that should work (and likely works on almost all of these type of corrupt files) is the "Remove all fallback" tags option. If you check that box and attempt to fix the original file, it should work correctly.

The reason that works is because I'm taking a brute force approach of deleting all of the fallback tags since they are optional tags per the file format spec. It is only relevant for older clients who are going to read the file, so technically, it will resolve the problem, but could make down-level clients fail. That is unless you re-save the file in Word and let it re-populate the fallback tags correctly, which it should.

[socrtwo]

Thanks for working on this. Have you released a build with a checkbox to remove all "Remove all fallback" tags? Best Wishes, Paul D Pruitt [email protected] [phone] 9006 Friars Rd. Bethesda, MD 20817-3320 - Have a manuscript lying around gathering dust? Let me help you self-publish it <[email protected]>.

…

On Thu, Aug 10, 2017 at 1:58 AM, Brandon Desjarlais < ***@***.***> wrote: Thanks for the report. The reason the default Fix fails is because the code I wrote is assuming the textbox (txbxContent) is a shape, not a rectangle. I'll see if I can adjust the logic to handle both shape and rectangle scenarios. The option that should work (and likely works on almost all of these type of corrupt files) is the "Remove all fallback" tags option. If you check that box and attempt to fix the original file, it should work correctly. The reason that works is because I'm taking a brute force approach of deleting all of the fallback tags since they are optional tags per the file format spec. It is only relevant for older clients who are going to read the file, so technically, it will resolve the problem, but could make down-level clients fail. That is unless you re-save the file in Word and let it re-populate the fallback tags correctly, which it should. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2CpmbKPtldwaeWkz8qcuZuZnUZS4R5ks5sWpwbgaJpZM4OxmJI> .

[socrtwo]

I removed the *<mc:Fallback>* and *</mc:Fallback>* tags from the EXPO SISTEMAS.docx word\document.xml file and it didn't fix the rezipped version. Do you mean the whole line *</w:txbxContent></w:pict></mc:Fallback></mc:AlternateContent>*? Or do you mean *<mc:Fallback>* and *</mc:Fallback>* tags and everything between them? Or something else? Best Wishes, Paul D Pruitt [email protected] [phone] 9006 Friars Rd. Bethesda, MD 20817-3320 - Have a manuscript lying around gathering dust? Let me help you self-publish it <[email protected]>. On Thu, Aug 10, 2017 at 3:57 PM, Paul D Pruitt <[email protected]> wrote:

…

Thanks for working on this. Have you released a build with a checkbox to remove all "Remove all fallback" tags? Best Wishes, Paul D Pruitt ***@***.*** [phone] 9006 Friars Rd. Bethesda, MD 20817-3320 - Have a manuscript lying around gathering dust? Let me help you self-publish it ***@***.***>. On Thu, Aug 10, 2017 at 1:58 AM, Brandon Desjarlais < ***@***.***> wrote: > Thanks for the report. The reason the default Fix fails is because the > code I wrote is assuming the textbox (txbxContent) is a shape, not a > rectangle. I'll see if I can adjust the logic to handle both shape and > rectangle scenarios. > > The option that should work (and likely works on almost all of these type > of corrupt files) is the "Remove all fallback" tags option. If you check > that box and attempt to fix the original file, it should work correctly. > > The reason that works is because I'm taking a brute force approach of > deleting all of the fallback tags since they are optional tags per the file > format spec. It is only relevant for older clients who are going to read > the file, so technically, it will resolve the problem, but could make > down-level clients fail. That is unless you re-save the file in Word and > let it re-populate the fallback tags correctly, which it should. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AA2CpmbKPtldwaeWkz8qcuZuZnUZS4R5ks5sWpwbgaJpZM4OxmJI> > . >

[desjarlais]

I let the application do it, which you can do by checking the checkbox on the bottom left corner of the application window and then clicking Fix Document. Basically I'm removing the entire mc:Fallback...</mc:Fallback> block of tags. You leave the AC (AlternateContent) tag though.

[socrtwo]

Yeah, that worked. You can close the bug. Best Wishes, Paul D Pruitt [email protected] [phone] 9006 Friars Rd. Bethesda, MD 20817-3320 - Have a manuscript lying around gathering dust? Let me help you self-publish it <[email protected]>.

…

On Thu, Aug 10, 2017 at 7:52 PM, Brandon Desjarlais < ***@***.***> wrote: I let the application do it, which you can do by checking the checkbox on the bottom left corner of the application window and then clicking Fix Document. Basically I'm removing the entire mc:Fallback...</mc:Fallback> block of tags. You leave the AC (AlternateContent) tag though. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#2 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA2CpgrtWifpguJ9aEbokeQh651Eq3UFks5sW5fagaJpZM4OxmJI> .

[socrtwo]

I didn't see that checkbox before but you clearly had it in the current version as I see now. Best Wishes, Paul D Pruitt [email protected] [phone] 9006 Friars Rd. Bethesda, MD 20817-3320 - Have a manuscript lying around gathering dust? Let me help you self-publish it <[email protected]>. On Thu, Aug 10, 2017 at 10:11 PM, Paul D Pruitt <[email protected]> wrote:

…

Yeah, that worked. You can close the bug. Best Wishes, Paul D Pruitt ***@***.*** [phone] 9006 Friars Rd. Bethesda, MD 20817-3320 - Have a manuscript lying around gathering dust? Let me help you self-publish it ***@***.***>. On Thu, Aug 10, 2017 at 7:52 PM, Brandon Desjarlais < ***@***.***> wrote: > I let the application do it, which you can do by checking the checkbox on > the bottom left corner of the application window and then clicking Fix > Document. Basically I'm removing the entire mc:Fallback...</mc:Fallback> > block of tags. You leave the AC (AlternateContent) tag though. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#2 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AA2CpgrtWifpguJ9aEbokeQh651Eq3UFks5sW5fagaJpZM4OxmJI> > . >