Internationalization should not be done on time entry for stats

theimmc · July 2022

This was noticed on iOS with country set to Finland.

On the stats entry, the time separator is a period "." instead of a colon ":". For example:

ALL TIME theimmc Resistance 2022-07-04 00.47.54 16 ....

Date and time should be in ISO-8601 format. Stats shouldn't be internationalized - same reason why you don't use localized comma separators for the numbers, or translate "ALL TIME" to their local language. Even the header line of the stats say:

Time Span Agent Name Agent Faction Date (yyyy-mm-dd) Time (hh:mm:ss) Level

By the way, even when the date value is shown with the period separator, the header still shows colon separator.

Thank you.

fluffboll · July 2022

I would appreciate if local time zone (or at least offset from UTC) was part of the time stamp too. When collecting stats for agents from multiple time zones, no time zone makes the date/time stamp mean something like "the stats are from this time stamp, +/- 14 hours or so" and kind of pointless except for ordering that specific agents updates, since you can't be sure the devices local time even is the same time zone as other agents in the same area (mission days, anomalies, etc are common places where this could be an issue).

DhrMekmek · July 2022

It's not just on stats, sharing portal links also use some localisation where comma's are replaced by dots, which for some users end up with broken portal links.

DhrMekmek · July 2022

@NianticBrian We have talked about this earlier on stats processing tools (like my Ingress First Saturday bot) about having one standard for exports without any localisation applied.