search

qwerin / fusion-tables

Automatically exported from code.google.com/p/fusion-tables
0 stars 1 forks source link

international - fusiontables use of date&time-format should per default iso8601 and support it fully #1445

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
For better international use the fusiontables date&time-format should support 
iso8601 ( https://en.wikipedia.org/wiki/ISO_8601 ) as default.

A string like 20150106T155823Z is even better human readable (the seconds since 
1970 might also be readable for some, but most ppl would connect that with 
nothing) AND a ISO_8601-formated string is also script-able much more easy 
(there don't need to be dashes, colon spaces or time-zones).
Furthermore a list with strings like 20150106T155823Z sorts by default correct.

UTC default - to avoid other TS-failures.
With setting all to UTC also the string gets more easy. No handling of 
TimeZones hassles anymore.

With this we would avoid international questions on dates&times. If indeed a 
fraction is really needed a 'comma' must be the separator(even if ISO_8601 only 
prefer it).

Specially due we could reduce the use of wicked Comma&Dot&otherDashes&andSuch 
incorrect interpretation and developer times get reduced.

We could go back to what we intended to do, instead of talking about the 'when'.
All gets more easy and fun. :)

Original issue reported on code.google.com by dilspi...@googlemail.com on 6 Jan 2015 at 3:44