https://bugs.documentfoundation.org/show_bug.cgi?id=167201
--- Comment #2 from Warren <[email protected]> --- Was able to reproduce in the following environment: Version: 25.2.4.3 (X86_64) Build: 33e196637044ead23f5c3226c Environment: CPU Threads: 8 OS Windows 7 Service Pack 1 X86_64 (6.1 build 7601) User Interface: UI render: Skia/Raster; VCL:win Locale: en-US (en_US); UI: en-US Misc: Calc:threaded I also tired different input values to determine boundary condition where it changes from a Date - Time to a Text format and found the following: 15-1-1:30 is displayed as 2015-01-01 01:30:00 but 15-1-0:30 is displayed as text 15-1-0:30 It appears that if the third number (HH) is 01 to 31 it is interpreted as hours and converted to # of days plus # of hours and the # of days is added to the Omitted day which is assumed to be 1. If the third number (HH) is not in this range then the whole input is treated as text. The value in the month field (MM) does not change the behavior as 15-12-31:30 is displayed as Date : Time 2015-12-02 07:30:00 but 15-12-32:30 is displayed as text 15-12-32:30 As the Date:Time format only applies for a limited range of input values of this format IMHO displaying as text makes more sense for all cases to ensure consistency. -- You are receiving this mail because: You are the assignee for the bug.
