Hi Sergey,
I've attached another round trip test... Most of the differrences I think I understand.
However, there seems to be a cdata statement missing for the field
The CDATA statement is important to ensure that none of the characters in the notes field are interpreted as accidental XML.
I've attached the results of the round trip test.
Regards, Bruce
Hi Bruce,
We need some time to examine the issue. Will be back soon.
Hi Bruce,
Aspose.Tasks will check Notes string data during export to XML and wrap it in CDATA term if it has not been wrapped in it yet. It will suppress XML parser to interpret the Notes data as part of XML structure.
The issue “Wrap Notes data in CDATA term” with id=13784 has been created and linked to this forum thread.
Also, pay attention, that Aspose.Tasks reads the Notes data from mpp files in RTF format (not as a plain text).
Hi Bruce,
We have here again the case when different MSP versions are working by different ways…
MSP 2003 wraps Notes in CDATA term ONLY if the note contains invalid for XML symbols while MSP 2007/2010 are not using CDATA at all but replace the symbols by their codes. So Aspose.Tasks is working now by the same way as MSP 2007/2010…
As I understand MSP 2002 wrapes all Notes into CDATA term, doesn’t it?
Any suggestions are highly appreciated.
Hi Sergey,
It sounds like you have done a very detailed evaluation of the problem. My concern was that the notes Element does not cause the xml to break. I'm looking forward to testing the new version.
Will you handle this conversion automatically for all versions?
FYI.. or are also a problematic area. I do some checking on these tags too.
Regards, Bruce
Hi Bruce,
The new version is on staging now.
Aspose.Tasks has to convert symbols like ‘<’, ‘>’, ‘&’ into their codes ‘<’, ‘>’, ‘&’ for all xml elements like MSP 2007 and 2010 do. It prevents XML parser errors.
The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.