Created attachment 46374 [details] File with comment Related to bug 33463, but that applies to .docx and this to RTF. I had an RTF file that I was redlining. I opened the file, made some comments (and changes), and saved it in .rtf (there was no warning about losing formatting). When I reopened, the changes were there but there were no comments visible. I ran some tests; the comments are, in fact, saved in .rtf format (when looking at the raw file, the /annotation keyword is present with my name and the text of the comment(s)), but when the file is reopened in Writer, the comments are not displayed. Then when the file is edited and re-saved, the comments are gone. Two files attached: an RTF file with a comment, and the same file (copied and saved with a new name) opened in Writer, edited and saved. Neither show any comments in Writer; the first has a comment in Word and the /annotation keyword in Notepad++.
Created attachment 46375 [details] File edited & saved, no comment
Miklos could you have a look please ( please reassign back to the list if not )
Noel, this is an import bug. I just verified that: 1) Creating a new doc with a comment in Word2007 -> save as rtf -> import in LO results in no comment, but 2) The other way around works fine. I have no idea right now how to fix it, but in case it's not urgent, I'm willing to fix it within the GSoC timeframe. If it's more urgent, then let's assign it back to the list. Thanks.
I modified Status to Assigned due to facts.
This is fixed in my GSoC repo: http://cgit.freedesktop.org/~vmiklos/lo-filters/commit/?id=2660469d1b63fdbd96e3971d066530cc4711a2eb Note that only comment text is imported, the underlying dmapper does not support author names and timestamps yet, but it's on my TODO. I'll merge that repo to master before 2011-08-15 and you'll have this feature if you enable experimental features. (Later hopefully it'll be the default, but there is no decision about that yet.)
Author names / dates are now also supported in the above mentioned repo.
*** Bug 41274 has been marked as a duplicate of this bug. ***
Fix confirmed in LO 3.5.1. Comments are visible in first attachment. Closing. Thank you.