Menu
The list of timezones is rather long, lots of duplication, and not very friendly to programmers let alone end-users.
Is there a way to to shorten the list to something friendlier and sufficient for 80%+ of users? But then how shall one decide which are the popular Tz?
The list in Windows seems pretty good, but I'm not sure if that's a good list to model after. It is interesting because DST is optional, is that why the list can be that short? Someone worked out the tz equivalents here.
I'm in Pacific Daylight Time (PDT). JS's getTimezoneOffset() returns 420 ==> offset -7. If I use the timezones list above, how would one tell it's US/Pacific (-8)?
Furthermore, what are the popular names for timezones? US/Pacific or Canada/Pacific sure sounds friendlier then America/Los_Angeles or America/Vancouver.
Lastly, how are the 2 timezones above different? Can they be safely grouped together and just use America/Los_Angeles in the app? How shall one group timezones together?
Thank you!
527
The user time zone is a client-specific time zone that can be defined for the user time and user date of each individual user in the user master record. It is contained in the system field sy-zonlo.
Friendly TZ names are subjective - one likes one name while someone else gets offended by it. Instead of trying to figure out how to shorten the tz list, why don't you implement geolocation and pre-select users' timezone for them?
It is not 100% accurate, and for travelling folk is just wrong, but that's better than make your users scroll through an endless list, I think.
131
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
