another case of leading zeros omitted for no reason, they even had the audacity to put "MM" and "DD" implying they were present
I wonder what the metadata saves as. I reckon they'll save with leading zeros, but have the zeros not shown in this menu as a way to reduce visual noise. Something probably aligned to one of their UX objectives. But this is all assumptions. OP can you confirm?
I suspect the data is saved as an epoch value, ie a 32 bit unsigned int. Or, if the makes are very future aware, a 64 bit int of arbitrary signedness
To be fair, the two additional year digits that aren’t present in the format mask had to come from somewhere, I guess… 🥴
Please tell me you can set the time to 24h format.
Half assed implementation... Their heart's just not in it.
I wonder what the metadata saves as. I reckon they'll save with leading zeros, but have the zeros not shown in this menu as a way to reduce visual noise. Something probably aligned to one of their UX objectives.
But this is all assumptions. OP can you confirm?
I suspect the data is saved as an epoch value, ie a 32 bit unsigned int. Or, if the makes are very future aware, a 64 bit int of arbitrary signedness
Hey now, people 292 billion years from now are going to care very much whether it's signed
aka signed int :)
On the plus side, they at least allow you to set it to the proper ISO8601 order
And they even left space for a leading zero in the boxes :(
November and December: do you see us?
What about October?
"YY"
Looks inside.
YYYY
To be fair its not even close to being compliant, ISO8601 does NOT allow
2026.01.01nor12.00.00Especially not "AM"
Also wrong delimiters.
To be fair, the two additional year digits that aren’t present in the format mask had to come from somewhere, I guess… 🥴
Fujifilm camera?