https://issues.apache.org/ooo/show_bug.cgi?id=97669
--- Comment #9 from Andreas Säger <[email protected]> --- This has been a major source of error and confusion since many years. The NullDate is a property that is saved in an ODF document. However, a ususal ODF document has no NullDate. It assumes to be interpreted with day zero 1899-12-30. A fresh profile does not include any NullDate in registrymodifications.xcu. Once this entry has been added to registrymodificatoins.xcu, it overrides the NullDate for all imported csv files at least. The imported dates are displayed correctly but their underlying values are wrong. When you copy data from the imported csv into a "normal" spreadsheet, the imported dates are off by 4 years and 2 days. Any new ODF file and the existing ones without explicitly set NullDate behave normally. IMHO, there is no need to import plain text with any NullDate other than the default one. When this happened to me I was absolutely sure that I did not handle any files other than my daily ODF stuff and some imported csv. I have no idea why 1904-01-01 had been registered in my user profile. And I do not understand how such a registry change could make any sense. a) We open ODF or MSOffice formats where it is explicitly saved in the file or defaulting to 1899-12-30 b) We import text data or dBase where the date value is "hard coded" and switching the default value gives only disadvantages. c) We open some other file format with well known day numbers assuming a different NullDate (Apple Works? historic spreadsheets? don't know). Then we import the file into the speadsheet model and set the right NullDate for this particular model. In the end it is a per-document setting. Why should we modify the registry in this special case? -- You are receiving this mail because: You are on the CC list for the issue. You are the assignee for the issue. You are watching all issue changes.
