https://bugs.documentfoundation.org/show_bug.cgi?id=170806
ady <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |bibisectRequest --- Comment #5 from ady <[email protected]> --- (In reply to Regina Henschel from comment #3) > A cell does not have a locale. Please forgive my non-strict wording about that. At a minimum, the text in the cell has a language-country setting ([CTRL]+[1] > Font tab), and you can see the language-country of each cell on the status bar. You can set one cell > font to be en-us, while an adjacent cell could be en-uk (or whichever). In this report, I don't want to get into the possibilities of mixing text of different language-country settings within the same cell. The main point is that Calc's functions (or the way they can parse their arguments) should not be limited / constrained by the "Date Acceptance Pattern", which is supposed to be aimed at how Calc interprets datetime-like values at the moment the values are introduced (or imported). Once the value is in the cell, the "Date Acceptance Pattern" should be done with its job, and should have no incidence on what the functions do; in particular, when the argument for DATEVALUE() and VALUE() is not even DateTime, but Text (or General/Standard). What I called "the locale of the cell" goes with the file, whereas the "Date Acceptance Pattern" can vary from user to user. It would be almost impossible for users of different countries to share a workbook. Anyway, I gave enough examples. Hopefully these two functions can be recover their full potential. -- You are receiving this mail because: You are the assignee for the bug.
