Here we talk about 100% real free offline ocr software only, they are full-featured.
John McGhie, Microsoft MVP (Mac Word), Consultant Technical Writer.
If you can read XML and you know how to operate the command-line Zip application in Mac OS X, come back and we can explain how to find the error and fix it by hand (note: it's a lot of work, but if you can't read XML, it's not possible). If it can, TextEdit will ignore the error and you may get the text back.ģ) Open in Preview: Preview will often give you a read-only copy of the document.Ĥ) Open in Pages: Pages can sometimes read what Word can't (and vice-versa). Open the file in PC Word, then Save As to a new file to clean out the file.Ģ) Open in TextEdit: TextEdit can sometimes read simple Word documents.
Often, this error is caused by PC Word writing content into the file that Mac Word can't read, sometimes because the copy of PC Word has not had the update that fixed this condition. Reported in "Location 2" or "Line 2", that is Word saying "Sorry, I can't read this".ġ) Open in PC Word: If you have access to PC Word, this is the best approach. Until Word can read the file, it can't tell where the lines of text are, they are ALL in "line 2". When Word first starts trying to read the file, all the code is in one very long line (millions of bytes long, sometimes) on "line 2". It needs to do this, because some of the most important information in a Word document is stored at the far end of the file. When Word attempts to open a document, it first checks to ensure it can read all of it. The second condition is the one you hope you do not have, because it usually means the file is lost.Īny references to "Location 2" means "The code of the document". The other guys have spoken about the first condition. This error message results from one of TWO conditions:ġ) There are illegal character(s) somewhere in the HDD name or the path or file name of the file.Ģ) There is corruption within the XML code in the document.