<p dir="auto">Using the <code class="notranslate">Dates</code> modules, when formatting an existing date, if the "year" field is only two digits long, it parses out missing the centuries. For example:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="&gt; Date(&quot;01/01/19&quot;,&quot;mm/dd/yy&quot;)
0019-01-01"><pre class="notranslate"><code class="notranslate">&gt; Date("01/01/19","mm/dd/yy")
0019-01-01
</code></pre></div>
<p dir="auto">Currently, a <code class="notranslate">yy</code> in the <code class="notranslate">DateFormat</code> string parses a two digit year string like "08" as the year 8. In Python and Posix, they instead map values 69–99 to 1969–1999, and values 0–68 to 2000–2068. I'm not sure that is a great default either, but it certainly seems more useful in general than the current julia implementation.</p>
<p dir="auto">I'm opening this issue mainly to brainstorm ideas how we could make this use case better.</p>
<p dir="auto">Maybe one option could be to add some new options to the <code class="notranslate">DateFormat</code> string that would stand for "POSIX 2 digit year parsing", i.e. a way to explicitly opt into that behavior.</p>
<p dir="auto">Another idea might be to add some syntax to the <code class="notranslate">DateFormat</code> string that would even allow one specify the century offset as part of the format string...</p>