Timestamp in logs should be in standardised (ISO) format

Bug
,
#1

Please describe what you are doing to trigger the bug:
Running Duplicacy, then reading the log.

Please describe what you expect to happen (but doesn’t):
The first line of log shows the timestamp that the backup began. I expect that timestamp to be in the standard ISO8601 format (yyy-mm-dd.

Please describe what actually happens (the wrong behaviour):
The timestamps in the log is hardcoded to the mm-dd-yyyy format used in America, eg “Beginning backup on 08-09-2026” for 9 August 2026.
It also should not be in the currently-selected system format since that can change over time. Log timestamp formats should be unambiguous and consistent over time.

#2

Where is this “Beginning backup on 08-09-2026” log message coming from? I couldn’t locate it in either the CLI or the GUI.

#3

Apologies, it’s in the backup log, but I think that is generated by Duplicacy Util, not by Duplicacy itself.
I’ll follow up there.