Hi Mihovil,
On Friday, 2012-08-31 13:46:47 +0200, Mihovil Stanic wrote:
> >>Now, my suggestion for Croatian locale would be:
> >>D.M;D.M.;D.M.Y;D/M;D/M/;D/M/Y
> >Any reason why the Croatian locale should have D.M. or D/M/ with
> >trailing separator?
>
> Because I'm not sure which is correct.
> I
>(from the bug)
> A suggestion: I'd like to see the "old" behaviour as a default:
NO! Definitely not. The old behavior was such a pain and it's a
godsend that it's finally fixed. Don't even consider such a stupid
idea. I can't even count how many silent/hidden data losses this
caused (especially o
On 31.8.2012. 13:01, Eike Rathke wrote:
Now, my suggestion for Croatian locale would be:
D.M;D.M.;D.M.Y;D/M;D/M/;D/M/Y
Any reason why the Croatian locale should have D.M. or D/M/ with
trailing separator?
Eike
Because I'm not sure which is correct.
I searched online for date writing rules
On 31.8.2012. 13:01, Eike Rathke wrote:
Now, my suggestion for Croatian locale would be:
D.M;D.M.;D.M.Y;D/M;D/M/;D/M/Y
Any reason why the Croatian locale should have D.M. or D/M/ with
trailing separator?
Eike
Because I'm not sure which is correct.
I searched online for date writing rules
Hi Mihovil,
On Friday, 2012-08-31 11:03:41 +0200, Mihovil Stanic wrote:
> That means you could have entered 31.8 or 31/8 or 31-8 in a
> cell and LO would recognise it as 31.08.12
> LO 3.6.x removed that support and now you need to enter 31.08.2012
> for date to be recognised.
This is not true. I
