Rich text libre office corrupt (NO back up) help

Hello everyone.
I have an important document that was updated and saved as per my norm as a rich text file .rtf.

I sadly and stupidly have not got a back up facility to restore it! Which I fully appreciate is a major priority for me to sort, and despite combing the internet and seeking advice from help forums am now reaching my wits end!

If anyone out there can advise, I would be so grateful. The error states one column and line is an issue.

Thank you for any tips of how to remedy.
Best TorG

Open the file with a text editor and look at the pointed out column and line. Share this point neighborhood.

thank you @LeroyG , for your prompt support.
I followed your guidance, IE opened it as a text document, and tried to delete that line and also that specific error 1221, 7. Saved the document as any file and as text, but reopening it just gives me a text file so unreadable.

When you say share this point neighbourhood, sorry but what do you mean, how do i do it?
The row that the error is related to is this,
065aff18a9c642a9de3486d2f5faf8a7dbdffef60f79c843ee7ffffbffceeffcce77bffbdd6f7ce31b7001f7a9af8d960667f00a96c13bb3c7ddca23dfea8ce3
and it was identified in column 7, so the first 1.
Thank you for continuing your support. Best TorG

065aff18a9c642a9de3486d2f5faf8a7dbdffef60f79c843ee7ffffbffceeffcce77bffbdd6f7ce31b7001f7a9af8d960667f00a96c13bb3c7ddca23dfea8ce3

That looks like part of an encapsulated graphic. The RTF code for graphics starts with {\pict\ and ends with an }. I played with that in a small test document, with an inserted picture, then deleted that code and saved, Writer had to recover the apparently damaged document but got back the complete text, but I probably deleted one } too many. Another test gave back a clean document. However, I’m not sure that you got the position of the error right. Make sure that when the file is open in a text editor, line wrap is turned off.

1 Like

Thank you so much Floris for your support.
I’m not too sure what that means or exactly what I can do with the information. I guess I could look for the error in the text doc with your suggestions above. Cutting at the points you suggest.
The error code gave only one row and one column (1221, 7), so I was not too sure If I just had to remove that digit or the whole line. will see if I can check line wrap off
I am currently opening Libre office in note pad, is that suitable? I located the first {\pict\ and then selected down to just after error location, saved with code/text format eg.UTF8 and then reopened it with WORD PAD and seem to have got most back.
Thank you for tricks and no how… You are a life saver x

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.

@TorG - The error code gave only one row and one column (1221, 7), so I was not too sure If I just had to remove that digit or the whole line.

You have to delete the entire graphic, so everything in the code {\pict\ … }, including that code.