Infuriated by the 3 page instructions of the Linux date
I decided to write my own.
The worst problem is that there is no canonical date format.
There are conventions:
— if you use dots as separator, the date should have DD.MM.YYYY format
— if slashes — the „American” format MM/DD/YYYY
— if dashes — the „international” format: YYYY-MM-DD
— if using Roman digits for the month, the date parts are separated
by spaces and no leading zero for days is used, like this: 9 X 2023
One problem may be with British format:: DD/MM/YYYY — they
also use slashes.
Infuriated by the 3 page instructions of the Linux date
I decided to write my own.
The worst problem is that there is no canonical date format.
Infuriated by the 3 page instructions of the Linux date
I decided to write my own.
The worst problem is that there is no canonical date format.
There are conventions:
— if you use dots as separator, the date should have DD.MM.YYYY format
— if slashes — the „American” format MM/DD/YYYY
— if dashes — the „international” format: YYYY-MM-DD
— if using Roman digits for the month, the date parts are separated
by spaces and no leading zero for days is used, like this: 9 X 2023
One problem may be with British format:: DD/MM/YYYY — they
also use slashes.
Infuriated by the 3 page instructions of the Linux dateWell, there is ISO 8601and RFC 1123. 4tH (will) support both. For my job I have to do with converting
I decided to write my own.
The worst problem is that there is no canonical date format.
Look at 'man co' option -d . There is a plethora of options
to format the date. It is a day's work to find out whether
they agree.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 475 |
Nodes: | 16 (2 / 14) |
Uptime: | 18:30:00 |
Calls: | 9,487 |
Calls today: | 6 |
Files: | 13,617 |
Messages: | 6,121,092 |