ISO 8601 date format error in Synchronize directories
Moderators: Hacker, petermad, Stefan2, white
ISO 8601 date format error in Synchronize directories
I use ISO 8601 date format (yyyy-mm-dd) e.g. 2010-02-28 in Windows. This works well everywhere in Total Commander except in Synchronize directories where the date is display with just 6 digits like 10-02-28.
The error is not new it has been there for several versions and is still present in 7.55 beat 2.
I admit this is a smaller cosmetic error, but I would like to see it fixed some time soon.
Thanks for years of excellent program, well worth its price, from a happy customer.
Doei RIF
The error is not new it has been there for several versions and is still present in 7.55 beat 2.
I admit this is a smaller cosmetic error, but I would like to see it fixed some time soon.
Thanks for years of excellent program, well worth its price, from a happy customer.
Doei RIF
- ghisler(Author)
- Site Admin
- Posts: 50386
- Joined: 2003-02-04, 09:46 UTC
- Location: Switzerland
- Contact:
Sorry, this is intentional to save valuable screen space in synchronize dirs. Unfortunately it's currently not possible to configure it differently.
Author of Total Commander
https://www.ghisler.com
https://www.ghisler.com
Let us take an example, in sycronize directory I have a file:Horst.Epp wrote:I don't see the benefit of displaying 4 digits for the year. Today there are no file date which can be interpreted wrong with a 2 digit year.
abc.txt 1,024 10-04-09 15:00:00
Was this file created:
10. April 2009 (typical European date format)
4. October 2009 (US date format)
9. April 2010 (ISO 8601 format)
Without knowing the exact setup of Windows and interpretation by the program you can not be sure to tell the date from a 6 digit format. However if we display 8 digits and using ISO 8601 date format (2010-04-09) there is no confusion.
Is this problem going away? No, I have files that was created yesterday, last week, last month, last year, 10 years ago and also >20 years ago. They will allways have this problem.
Yes just using 4 digits screen space would provide clarity. Certainly a good use of that tiny space. Total Commander should just follow Windows date format, then you can set Windows to save the space.Horst.Epp wrote:It also would waste just 4 digits screen space in the snchronize dirs window without any additional info.
Last edited by rif on 2010-04-11, 17:07 UTC, edited 1 time in total.
In the normal file browsing panes the dates are displayed with 8 digits. If there is space there I cannot see why there would not be space on the Syncronize dirs window. It is practically the same information length.ghisler(Author) wrote:Sorry, this is intentional to save valuable screen space in synchronize dirs. Unfortunately it's currently not possible to configure it differently.
I recommend that Total Commander just follow the setup of Windows date format, then user can select if date format is 6 or 8 digit long.
I do not expect to see this fixed in 7.55, but it would be nice if it was fixed by version 7.60

- Samuel
- Power Member
- Posts: 1930
- Joined: 2003-08-29, 15:44 UTC
- Location: Germany, Brandenburg an der Havel
- Contact:
I totally agree to rif. Sometimes I am also confused by something ambiguous like 12.11.10.
Good point.rif wrote:In the normal file browsing panes the dates are displayed with 8 digits. If there is space there I cannot see why there would not be space on the Syncronize dirs window. It is practically the same information length
I always know what date / time setup my windows has, so its never a question how to read the date. And TC just shortens the year and doesn't change the date format in any other way. I'm working for a multi-national company and never had any problems with this.rif wrote:Let us take an example, in sycronize directory I have a file:Horst.Epp wrote:I don't see the benefit of displaying 4 digits for the year. Today there are no file date which can be interpreted wrong with a 2 digit year.
abc.txt 1,024 10-04-09 15:00:00
Was this file created:
10. April 2009 (typical European date format)
4. October 2009 (US date format)
9. April 2010 (ISO 8601 format)
Without knowing the exact setup of Windows and interpretation by the program you can not be sure to tell the date from a 6 digit format. However if we display 8 digits and using ISO 8601 date format (2010-04-09) there is no confusion.
...
But I would not argue against an option to control that display.
And as the date and time of a file is stored in binary UTC format it will be no problem to understand it in 10 or 20 years.
Support++ for 4 digits in the year in the Sync tool - just as there is in the Multi-rename tool.
BTW - shouldn't this be moved to Suggestions?
BTW - shouldn't this be moved to Suggestions?
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
[mod]Thread moved to TC7.55 Suggestions
Clo, moderator.[/mod]
Clo, moderator.[/mod]
#31505 Traducteur Français de T•C French translator Aide en Français Tutoriels Français English Tutorials
Re: ISO 8601 date format error in Synchronize directories
We now have TC 9.51 and this is still not fixed. There hasn't been an update in a long time.
I find the truncation of the first two digits of the year in ISO format confusing, as it no longer resembles ISO format and as others have commented here is therefore no longer unambiguous.
IMHO, the date format shown in the synchronize screen should be the same as that shown in the normal two-pane display.
Is there any hope of this happening?
Is there a thread for 9.52 suggestions?
I find the truncation of the first two digits of the year in ISO format confusing, as it no longer resembles ISO format and as others have commented here is therefore no longer unambiguous.
IMHO, the date format shown in the synchronize screen should be the same as that shown in the normal two-pane display.
Is there any hope of this happening?
Is there a thread for 9.52 suggestions?
Windows 10 Pro x64 20H2
TC 11.03 x64 / x86
TC 11.03 x64 / x86
Re: ISO 8601 date format error in Synchronize directories
You should have noticed that we are in the beta phase of TC 10.rsbrux wrote: 2021-04-12, 08:21 UTC We now have TC 9.51 and this is still not fixed. There hasn't been an update in a long time.
I find the truncation of the first two digits of the year in ISO format confusing, as it no longer resembles ISO format and as others have commented here is therefore no longer unambiguous.
IMHO, the date format shown in the synchronize screen should be the same as that shown in the normal two-pane display.
Is there any hope of this happening?
Is there a thread for 9.52 suggestions?
Windows 11 Home, Version 24H2 (OS Build 26100.3915)
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
TC 11.51 x64 / x86
Everything 1.5.0.1391a (x64), Everything Toolbar 1.5.2.0, Listary Pro 6.3.2.88
QAP 11.6.4.2.1 x64
Re: ISO 8601 date format error in Synchronize directories
Sorry, my bad!
Windows 10 Pro x64 20H2
TC 11.03 x64 / x86
TC 11.03 x64 / x86
Re: ISO 8601 date format error in Synchronize directories
Still support++
License #524 (1994)
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
Danish Total Commander Translator
TC 11.51 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1391a
TC 3.60b4 on Android 6, 13, 14
TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar