Am in state of confusion: images missing in DT RTF document after opening with ext editor, but present if copy paste

[rufus123]

in case of a Nisus - DT interaction disaster whereby the document is mangled and the info lost, does DT have any forum of document versioning ? If so how frequent are the automatic version backups ?
thank you

[pete31]

@rufus123

What I tried DT data from RTFD template → open in Nisus Writer Pro → use styles (headings, images etc) → save→ return to DT → edit extensively in DT (including adding images) → open again in Nisus Writer Pro → I could see the same doc as in DT including all previous Nisus Writer Pro styles and changes made in DT.

Over here the Nisus Writer TOC is destroyed after editing in DEVONthink.

[pete31]

From the thread I linked above

@BLUEFROG

No, DEVONthink does not support versioning beyond manual versioning via duplicate and rename functions.

[korm]

If Nisus behaves fragilely when working with RTFs, then maybe the best approach is to keep the documents external to DEVONthink, index them, and not attempt to edit them in DEVONthink.

That’s not a criticism of Nisus – it deserves its reputation for excellence. But it appears to be working in a non-standard way with a common file type, which is behavior one cannot expect DEVONthink to overcome.

[Greg_Jones]

@korm

That’s not a criticism of Nisus – it deserves its reputation for excellence. But it appears to be working in a non-standard way with a common file type, which is behavior one cannot expect DEVONthink to overcome.

I’ve not looked at Nisus in many years now, but back in the day when I did it had a reputation for a non-standard version of RTF(D).

[rufus123]

OK. thank you for the testing. So I can get a surprise anytime with style related and other features

[rufus123]

yes, and a good example is the lack of quick look as described by @chrillek above

[rufus123]

@korm

If Nisus behaves fragilely when working with RTFs, then maybe the best approach is to keep the documents external to DEVONthink, index them, and not attempt to edit them in DEVONthink.

It would seem like a perfect solution. I am new to DT, and have not yet learned to do that (replicants ?)
I would imagine that if I use that method, I would lose the ability to see the document in DT, which is not acceptable in terms of my workflow, but I have no idea what I am talking about.

[korm]

Like anything else, try it in your own database.

Indexed documents can be seen, read, and edited in DEVONthink. The manual explains it all.