https://bugs.documentfoundation.org/show_bug.cgi?id=147316
Mike Kaganski <mikekagan...@hotmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #4 from Mike Kaganski <mikekagan...@hotmail.com> ---
(In reply to m.a.riosv from comment #3)
> In any case, IMO VALUE() looks a better function for that, as it is already
> interpreting dates, only needs support for decimal separator.
> Even best if VALUE() tries first the separator of the language in use, and
> if error result with the other.
No. Trying different separators one after another is error-prone. E.g., some
locales have comma and dot pair; other locales (e.g. ru-RU) have comma and
space... and trying several variants would just increase likelihood of false
detection.
Note that NUMBERVALUE is *specifically* created for locale-independent
conversion; and this is exactly the context of this enhancement - when user
wants to convert the input from specific representation, without taking current
locale into account. Extending VALUE to accept fractions of a second is
separate issue, and should only use current locale.
However, it would also be OK to introduce a dedicated VALUE_* variant for
locale-independent conversion, or to add optional arguments to override the
separators ... no idea what would be better, but it would work, too.
> For me excel NUMBERVALUE() doesn't work in that way for dates. Only works
> for dates without time and without parameters.
Yes, that is what I mentioned :-)
--
You are receiving this mail because:
You are the assignee for the bug.
