Hello,
When converting an RTF file that contains comments to Word (.docx) format, any comments that do not have a date ({*\atndate …}) associated with them end up being assigned a date of 1/1/1901 when opened in Word.
To see what I mean, try opening the attached RTF file (text-with-comment.rtf) in Word (I tested in Word for Mac 2011). The comment in the RTF has no \atndate associated with it, so Word does not show a date for it, which is as it should be.
Next, convert the attached RTF file to .docx format using Aspose.Words, then open the resulting .docx file in Word. Now you will see that the comment does have a date next to it, of 1/1/1901.
Expected behaviour: if a comment does not have a date associated with it in the RTF, it should have no date associated with it in the .docx file and Word should show no comment. (If this is not possible, today’s date should be used. I can implement that workaround in our own RTF generator, but it would be better if no date is created if there isn’t one associated with the comment - our app doesn’t have dates associated with comments, for instance.)
Thanks!
All the best,
Keith
Hi Keith,
Thanks for your inquiry. I have tested the scenario and have managed to reproduce the same issue at my side. For the sake of correction, I have logged this problem in our issue tracking system as WORDSNET-11380. I have linked this forum thread to the same issue and you will be notified via this forum thread once this issue is resolved.
We apologize for your inconvenience.
The issues you have found earlier (filed as WORDSNET-11380) have been fixed in this .NET update and this Java update.
This message was posted using Notification2Forum from Downloads module by aspose.notifier.