Skip to main content
25 events
when toggle format what by license comment
Feb 12, 2022 at 3:00 history tweeted twitter.com/StackSoftEng/status/1492332641139494918
S Feb 10, 2022 at 15:56 history edited lennon310 CC BY-SA 4.0
corrected spelling
S Feb 10, 2022 at 15:56 history suggested xehpuk CC BY-SA 4.0
corrected spelling
Feb 10, 2022 at 15:45 review Suggested edits
S Feb 10, 2022 at 15:56
Feb 10, 2022 at 13:38 history protected gnat
Feb 10, 2022 at 13:29 answer added Joe Johnson timeline score: -3
Feb 9, 2022 at 22:11 comment added Neil The front end will have to translate non-API data (titles, text, tables etc), so it might as well localise the data too. Then the back end will not have to store (or be told) the current user's locale.
S Feb 9, 2022 at 16:17 history suggested chrylis -cautiouslyoptimistic- CC BY-SA 4.0
Change "culture" to "locale" as suggested in a comment but unaddressed by OP.
Feb 9, 2022 at 15:22 review Suggested edits
S Feb 9, 2022 at 16:17
Feb 9, 2022 at 12:49 answer added Lie Ryan timeline score: 0
Feb 8, 2022 at 19:24 answer added Josh Part timeline score: 1
Feb 8, 2022 at 15:49 comment added Voo @Jonathan Oh nice example (now that I think about it Outlook does mention the original locale and then the converted local time, possibly for such an issue, fascinating(. Yeah dates and times are complicated.
Feb 8, 2022 at 15:31 comment added Jonathan @voo: You're right, I considered just machine-generated timestamps. For an extreme example, consider an Exchange/Outlook recurring meeting with participants in different time zones - the meeting must be bound to one timezone, and shit with it, some times to the detriment of the other participants (I've personally experienced this).
Feb 8, 2022 at 15:04 comment added Voo @Jonathan That advice comes up quite often, but it definitely isn't a silver bullet and can be a horrible choice (I should know, I did exactly this once and ran into a similar problem that Jon describes). Jon Skeet has a nice blog post about why you have to consider the semantics to choose the right format. (Another classic counter example is that of an alarm clock - you probably want to store the next alarm in local time)
Feb 8, 2022 at 12:15 comment added Jonathan All the below answers are usually good for timezone calculations as well. Dat ashould be stored and transmitted in a set timezone (almost always UTC), and the fronetend display should convert to the user's timezone (or provide a choice of timezone - some log viewers do this).
Feb 8, 2022 at 10:52 answer added James_pic timeline score: 4
Feb 8, 2022 at 7:11 comment added Dario @njzk2 I mean the BCP 47 codes mentioned on docs.microsoft.com/en-us/openspecs/office_standards/ms-oe376/… e.g. en-US for US-English
Feb 7, 2022 at 22:39 answer added Helena timeline score: 11
Feb 7, 2022 at 22:08 comment added njzk2 by "culture" do you mean "locale"?
Feb 7, 2022 at 18:18 history became hot network question
Feb 7, 2022 at 10:52 answer added pjc50 timeline score: 78
Feb 7, 2022 at 10:42 review Close votes
Feb 12, 2022 at 3:04
Feb 7, 2022 at 10:17 comment added gnat Sharing your research helps everyone. Tell us what you've tried and why it didn't meet your needs. This demonstrates that you've taken the time to try to help yourself, it saves us from reiterating obvious answers, and most of all it helps you get a more specific and relevant answer. Also see How to Ask
S Feb 7, 2022 at 10:15 review First questions
Feb 7, 2022 at 11:16
S Feb 7, 2022 at 10:15 history asked Dario CC BY-SA 4.0