Excellent stuff floris_v.
Just tested this myself and it works like a dream. I deliberately corrupted an .rtf file with an image in it by deleting the first ‘}’ character that occurred immediately following the image data and Writer then wouldn’t open the file, and I got a line and column error of the type the TorG reports. Then I opened the file again in Programmer’s Notepad and put the } I had deleted back in place – the result then was that Writer opened the file no problem (and the image and text was restored in full). Then I deleted all the image data, starting from {\pict\ and ending on and including the first } character at the end of the image data. Writer was then able to open the .rtf though minus the image, of course, but I did get all the text back.
Used Programmer’s Notepad (portable) to do this in – quite a bit easier than using Windows Notepad.
Does that mean that ‘just a text file’ is of no use to you?
Have to say that when I corrupted the file the character I deleted was at, according to Programmer’s Notepad, 287:93 (line:column). However, when I tried to open the corrupted file in Writer it reported the error as occurring at 69:7 (row, col). From that I would take that Writer can’t be relied on to report the position in an accurate way. However, when I loaded the corrupted file back into Programmer’s Notepad and went the row,col that Writer reported that row,col was well inside the image-data-block – so maybe from that you might be able to conclude that at least Writer might be pointing you to the particular image-data-block that is causing the problem.