https://bugs.documentfoundation.org/show_bug.cgi?id=143508
Wolfgang Jäger <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #4 from Wolfgang Jäger <[email protected]> --- DATEVALUE() is dangerous basically. Making its working depend on a cells locale will probably complicate things. And: What if the function only is a subexpression, and the relevant result appears in a different cell... Surprises to be expected anyway. An opinion: The inconcistency concerning TEXT() isn't actually important. The relevant problem with DATEVALUE() is that it's result factually depends on parameters (settings) neither clear to the user nor explicated by the help nor reasonably disambiguated in any way. That's not only concerning the locale used for the conversion, but also - and mainly- concerning the default century. This default will shift with time, and results can change without warning, and unnoticed if two-digit-years are accepted. The only way to reasonably handle the date-format-troubles, is to abandon them. "And by opposing end them." One step on the way would require to not convert ambiguous date-strings at all. If users urgently need the functionality, the indispensably needed information must be added. Yes, this requires optional parameters: A first one for the used format, and - in case of acceptance for two-digit-year-dates - the first year of the default century as the second one. -- You are receiving this mail because: You are the assignee for the bug.
