Yes, so far.
And columns are cheap,
So are new sheets,
But also cheats.
In fact correct handling of data containing numeric values requires, imo, that the representation also contains sufficient and truthful information about the semantics. 1 = 1 V = 1 USD
isn’t even fun, but a collection of lies. This is extremely important concerning DateTime
values where not only the format is problematic, but also an arbitrary NullDate
is applied, and makes the conventional format absolutely inapt for the communication of durations. Moreover ToD
formats suppress an integer part. And so on …
Years ago I came to the conclusion that so-called numeric data must in most cases be exchanged as standardised texts. Pure numbers are a rare thing in the universe.
Modern processors, on the other hand, are fast enough for spreadsheet if textually represented data must be converted on the fly if calculations are to be performed. In addition an automatic check for the compatibility of operands would be needed.
I made a little example using some Basic code to get a kind of “proof of concept”. Now I derived an .ods
from it containing a sheet specialised to durations and their relation to DateTime values.
Now you will definitely want to see my examples. The magic lies in the strings I use as xFormat
- and in the related analysis, and …
xFormat_requiresREGEXfunction.ods (33.7 KB)
Don’t hesitate to ask if I failed to make the meanings/usage of xFormat strings clear enough.