I noticed the levels in TBE have different formats for the date metadata field. Sometimes a slash is used as seperator, sometimes the month is written in full, etc.
This is bad and chaotic.
It also looks like TBE saves the date depending on the system's locale, which is probably why we have the mess in the first place.
For your information: My system's date format is “DD.MM.YY”.
I suggest to change TBE in a way that it always uses the ISO 8601 date format “YYYY-MM-DD” for storing the date internally, so consistency between systems is ensured.
Note that this suggestion does not require to change the way how dates are displayed to the user. Ideally, TBE converts from ISO to the system's locale to display the date to the user, and vice-versa for saving the date into a file.
I noticed the levels in TBE have different formats for the date metadata field. Sometimes a slash is used as seperator, sometimes the month is written in full, etc. This is bad and chaotic.
It also looks like TBE saves the date depending on the system's locale, which is probably why we have the mess in the first place.
For your information: My system's date format is “DD.MM.YY”.
I suggest to change TBE in a way that it always uses the ISO 8601 date format “YYYY-MM-DD” for storing the date internally, so consistency between systems is ensured. Note that this suggestion does not require to change the way how dates are displayed to the user. Ideally, TBE converts from ISO to the system's locale to display the date to the user, and vice-versa for saving the date into a file.