From c81765b3ea684108637a5a2e657e1c7dfa76c679 Mon Sep 17 00:00:00 2001 From: Olivier Lacan Date: Tue, 18 Jul 2017 12:54:17 +0200 Subject: [PATCH] Address issues with Confusing Dates section This section was by far the weakest since it focused too heavily on issues with the U.S.-based date formats and not enough on justifying the recommendation. Addresses #191 #178 --- source/en/1.0.0/index.html.haml | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/source/en/1.0.0/index.html.haml b/source/en/1.0.0/index.html.haml index 32c7291..3632429 100644 --- a/source/en/1.0.0/index.html.haml +++ b/source/en/1.0.0/index.html.haml @@ -167,13 +167,16 @@ version: 1.0.0 Confusing Dates %p - In the U.S., people put the month first (06-02-2012 for - June 2nd, 2012), while many people in the rest of the world write a - robotic-looking 2 June 2012, yet pronounce it - differently. 2012-06-02 works logically from largest to - smallest, doesn't overlap in ambiguous ways with other date formats, - and is an #{link_to "ISO standard", iso}. Thus, it is the - recommended date format for changelogs. + Regional date formats vary throughout the world and it's often + difficult to find a human-friendly date format that feels intuitive + to everyone. The advantage of dates formatted like + 2017-07-17 is that they follow the order of largest to + smallest units: year, month, and day. This format also doesn't + overlap in ambiguous ways with other date formats, unlike some + regional formats that switch the position of month and day numbers. + These reasons, and the fact this date format is an + #{link_to "ISO standard", iso} are why it is the recommended date + format for changelog entries. %aside There’s more. Help me collect these antipatterns by