https://bugs.documentfoundation.org/show_bug.cgi?id=166914

--- Comment #21 from Eike Rathke <[email protected]> ---
(In reply to Fabbian from comment #19)
> (In reply to Eike Rathke from comment #15)
> > (In reply to Fabbian from comment #12)
> > > Note particularly the egregious error which interprets 6-11-25 as 
> > > 11/25/2006.
> > That's not an error, 6-11-25 is interpreted as ISO date notation,
> > year-month-day, with two-or-less-digits year 6.
> 
> What does ISO 8601 say about two-digit years?
Depends on which version. "allowed in the (now superseded) 2000 version:
YY-MM-DD", see https://en.wikipedia.org/wiki/ISO_8601

You are not trying to argue that we should stop supporting the short-hand
notation now, or restrict it to only 2 digits?


> > (In reply to Fabbian from comment #13)
> > > I believe the OpenOffice output is correct.
> > It's not, it does not recognize 25-06-11 that would be a two-digits year ISO
> > date but interprets 6-11-2025 and 6-11-25 as 2025-06-11, for which there is
> > no justification in an en-US locale that does not use '-' hyphen minus date
> > separator and the string is not parse-able as ISO date either.
> 
> Any north American reader would recognize 6/11/25 and 6-11-25 as equivalent.
Maybe US readers, Canadians probably not.

> Dates are written both ways here.  I can't speak for other parts of the
> world.  OpenOffice (and presumably Excel) follow the conventions that are
> familiar to human readers.
OpenOffice accepts every nonsense it encounters because Excel did.

> Perhaps it wasn't clear that the PDF files show the output of the VALUE
> function in the first column and the input in the second column.  I hope
> that didn't cause any confusion.  Sorry I didn't think to label them.
That was clear, as otherwise there wouldn't be Err:502 in the first column.

> I don't intend to engage in an extended debate on this issue but I believe
> Eike Rathke was mistaken about ISO date formats.
Thanks. It's only that I was after it for 20 years and implemented all this
shit.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to