https://bugs.freedesktop.org/show_bug.cgi?id=83116
--- Comment #2 from ariel cornejo <arie...@gmail.com> --- I agree about the likely cause but I do see it as a bug or needful improvement; an user could argue that if "12:23:34.9994" is a legitimate time, so is "12:23:34.9996". I think I can fix it; I'd either: - parse the whole "SS.0000" bit as a float respecting the regional settings, - add fractional_seconds/length(fractional_seconds) to the ongoing value, or - if the precision must be limited to 1 ms, allow 1 s to be carried over to the seconds part. Any hints on the relevant bit of code? I'll look into setting up a development environment. Also, is there a spec that says that decimal digits beyond the third must be truncated or rounded in conversion? I thought dates were floating-point numbers. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
