In ODFF standard 6.3.5 Conversion to Number, If the expected type is Number, then if value is of type: ● Text: The specific conversion is implementation-defined; an evaluator may return 0, an Error value, or the results of its attempt to convert the Text value to a Number (and fall back to 0 or Error if it fails to do so). Evaluators may apply VALUE() or some other function to do this conversion, should they choose to do so. Conversion depends on the actual locale the application runs in, especially if group or decimal separators are involved.
It leave the implementation to decide whether to convert a text value to a number, in which extent to convert a text value to a number. AOO now only support convert string content to numeric, which is integer numbers including exponent, and ISO 8601 dates and times in their extended formats with separators. This cause issue 118942( https://issues.apache.org/ooo/show_bug.cgi?id=118942). In my point of view it is better to support more scenarioes to convert a text value to a number, such as decimal. Though different locale has different decimal separator, AOO can support decimal separator for current locale and standard decimal separator, ".". It will be more complicated for date format. What's your suggestion?
