errors reading rtf

[feat]

> There were problems reading this document.

• as a matter of fact, while typing that document, I had noticed frequent interruptions, sometimes with the assorted spinning ball
• what I didn't know is that saving and opening the document again would cause a read errors
• and that the automatically saved back-up document would behave just the same

> Please review the document before saving to see if anything has been lost.

• thanks, but how am I supposed to detect which of the 55,500 words could possibly have been lost
• or which of the 350,000 characters has been dropped?

> If you are willing to send this file to Nisus Software, we will do all we can to fix this problem for a future release.

• sent, but still no response
• now, what should I do?

[martin]

> Please review the document before saving to see if anything has been lost.

• thanks, but how am I supposed to detect which of the 55,500 words could possibly have been lost
• or which of the 350,000 characters has been dropped?

Sorry the dialog is so unspecific- it's a general catch all message that appears when something unexpected occurs when reading your file. It's something that we could improve upon.

> If you are willing to send this file to Nisus Software, we will do all we can to fix this problem for a future release.

• sent, but still no response
• now, what should I do?

I've looked at the file and the problem is just a minor shift in indexing. The index as "type de donne:int" that you've applied inside your table after "dans /usr/include/ctype.h" has moved from inside the table cell to the newline just preceding the start of the table. I've filed it as a bug for us to look at, sorry for the trouble.

[feat]

thanks for looking at my problem in details: I've also noticed that shift since now it looks like I've indexed two linefeeds, which just doesn't make sense…

but even though I've selected the whole document and suppressed all indexing, this still appear in the index list: as if it were impossible to suppress it because of the corruption.

is there a way I can tweak the underlaying RTF code directly to get rid of the corrupted data?

I've also noticed displaced foot-notes, now as a cluster at the very beginning of a paragraph, far away from their original location; also margin sizes have been altered in a number of sections beginning, at chapter 8

now the problem is each time I open that file again and save it in RTFD format, the corruption creeps in again: what can I do to cure this?

[martin]

thanks for looking at my problem in details: I've also noticed that shift since now it looks like I've indexed two linefeeds, which just doesn't make sense…

When the shift occurred NWP became confused as to where the indexing was applied and chose whatever text was nearby.

but even though I've selected the whole document and suppressed all indexing, this still appear in the index list: as if it were impossible to suppress it because of the corruption.

is there a way I can tweak the underlaying RTF code directly to get rid of the corrupted data?

It's possible the indexing was applied to some internal document content that you can't augment. You could search the raw RTF for this kind of sequence:

Code: Select all

{\xe \pard \plain \xef68 \nisusxeident1 {\v blerg}}

You just want to delete the whole thing, though all digits and the actual text are variable, eg: "\nisusxeident282".

now the problem is each time I open that file again and save it in RTFD format, the corruption creeps in again: what can I do to cure this?

Any use of "Index As" inside a table cell will introduce the problem. You'll have to stick with using the regular "Index" command, or apply the "Index As" somewhere nearby.

I've also noticed displaced foot-notes, now as a cluster at the very beginning of a paragraph, far away from their original location; also margin sizes have been altered in a number of sections beginning, at chapter 8

This would be a totally separate problem. I'm afraid I didn't notice it when I received your file, which I've already destroyed. If you observe problems unrelated to indexing again, please let me know.