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

ady <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]
             Status|NEEDINFO                    |NEW

--- Comment #9 from ady <[email protected]> ---
In a hunch, I am CC'ing Mike Kaganski. Maybe he happens to know what's going
on, but even if he doesn't, maybe he will be able to point to someone who
might.


(In reply to pedja from comment #8)
> I uploaded example, but I think it is not the same as after i updated Date
> acceptance pattern, I amunable to set it back as it was.
> 
> It was D.M.Y;D.M but that is not accepted. I entered D.M.Y;D.M. to make
> example.


This is what seems to be wrong. For example, when the Locale is English (USA),
the default Date acceptance pattern is "M/D/Y;M/D". I am not seeing the reason
for Calc to flag "D.M.Y;D.M." as wrong with a red color except maybe the very
last dot after the last "M". But even if that's the problem, why now and not
before?


> 
> The first row is entered as MM/DD/YYYY 
> The second row is entered as DD.MM.YYYY


In attachment 186121 from comment 7, cell A1 (that was supposed to be
MM/DD/YYYY according to your comment 8) is not really a date but text – tricky,
I know. This seems to match the Date acceptance pattern of "D.M.Y;D.M." (with
or without the latest dot/period/stop) which doesn't include MM/DD/YYYY (for
this example, according to your comment 8).

Using my settings, I see that cell A1 starts with an apostrophe. I'm not sure
that you are seeing it under your Locale settings, or that you introduced it
intentionally; probably not.

This reminds me of another very tricky and unclear bug report involving dates
and apostrophe (not seen by the original reporter) and Date acceptance pattern
too: https://bugs.documentfoundation.org/show_bug.cgi?id=148747#c39 – just in
case anyone is interested, I would suggest only reading after c#35 and not
before it, because it could be more confusing than anything else.

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

Reply via email to