Hi all,
I apologise for delay.
Yes. you are right about proposed patterns.
Since nobody in Croatia uses Croatian standard of date writing
(-mm-dd), almost everybody use proposed patterns.
With regards,
Robert
On 2.9.2012 20:47, Mihovil Stanić wrote:
Dana 31.8.2012. 14:46, Eike Rathke je
Dana 31.8.2012. 14:46, Eike Rathke je napisao:
I'd say it should be D.M.Y;D.M;D.M.Y.;D/M/Y;D/M or maybe
D.M.Y;D.M;D.M.Y.;D.M.;D/M/Y;D/M The '/' patterns are only for numeric
keypad input, aren't they? I doubt anyone wants to key in an extra
character if not needed.. Eike
Yes, you are right.
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. It
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
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
(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 on
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 searched
