using tolocaledatestring with 2-digi year returns wrong century

Question

I'm manipulating some data coming from an external XML that I cannot change. This XML has dates in this format:

01-APR-39

and I want the date to become in this format:

01/04/1939

but using:

new Date('01-APR-39').toLocaleDateString('en-GB')

is returning wrong century:

01/04/2039

how can I fix this?

How is the parser supposed to know which century you want? See [*Why does Date.parse give incorrect results?*](https://stackoverflow.com/questions/2587345/why-does-date-parse-give-incorrect-results) — RobG, Aug 19 '20 at 08:27

mplungjan · Accepted Answer · 2020-08-19T08:31:35.063

0

Like this.

You need to decide the year cutoff

const cutOff = 29; // or have a range
const getDateFromYY = dStr => {
  let [dd, mmm, yy] = dStr.split("-");
  const yyyy = +yy > cutOff ? "19" + yy : "20" + yy;
  return new Date(dd + "-" + mmm + "-" + yyyy).toLocaleDateString('en-GB')
};

console.log(getDateFromYY('01-APR-39'))

console.log(getDateFromYY('01-APR-19'))

edited Aug 19 '20 at 08:31

answered Aug 19 '20 at 08:15

mplungjan

169,008
28
173
236

Can you explain what the number `75` is? Why in case of `01-APR-76` the answer should be `01/04/2076`? – Nikita Madeev Aug 19 '20 at 08:18
I updated to have a cutoff at 29 - so numbers > 29 will be 1900 – mplungjan Aug 19 '20 at 08:24
Ok, I hope OP understands the idea of manual selection `cutOff`, otherwise in case `01-APR-19` he will receive `01/04/2019` :) – Nikita Madeev Aug 19 '20 at 08:30

using tolocaledatestring with 2-digi year returns wrong century

1 Answers1