The Aspose getters and setters that use Java Date all do this, and ruin timestamps instead of leaving them alOne.
java.util.Date is not intended To be used as a timestamp with timezOne. From the JavaDoc:
Allocates a D…...Someone tried to ‘fix’ it at one point (so, when you read back...realize that sometimes it is “one-way” in the sense of e.g. exporting...