Created attachment 59891 [details] date ranges that illustrate the 'bug' If you enter any date between 1/Jan/1830-15/Apr/1880 and Libreoffice Calc enters it as -1d. i.e. enter any date in the range 1/Jan/1831-15/Apr/1880 and calc will register the value as -1d from the date entered. E.g. enter 1/1/1880 press enter and the cell will get the value 31/12/1879 To overcome you need to enter dates as +1d. If you want to enter 18/1/1880 (d/m/yyyy) you should enter 19/1/1880 (d/m/yyyy) As a result it is also ***impossible*** to enter 14/4/1880 See attached for illustration fo the problem. Notes: Bug found/tested in: 1. LibreOffice 3.5.0rc3 Build ID: 7e68ba2-a744ebf-1f241b7-c506db1-7d53735 2.LibreOffice 3.5.2.2 Build ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f Cheers, N.
NOT reproducible with "LibreOffice 3.5.2.2 German UI/Locale [Build-ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f] on German WIN7 Home Premium (64bit). When I open reporters sample and type "1.1.1870" into cell A71 <enter> will lead to "01.01.1870" Related to or DUP of "Bug 44286 - [EDITING] Calc decreases one day of a date typed (Brazilian-portuguese locale and timezone)"? @Nikitas Thank you for your report – unfortunately important information is missing. May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? If you believe that that is really sophisticated please as for Help on a user mailing list Please: - Write a meaningful Summary describing exactly what the problem is - Contribute a step by step instruction containing every key press and every mouse click how to reproduce your problem (due to example in Bug 43431) like Tyoe "xyz" into cell ..., <enter>, expected ...., actual ... – if possible contribute an instruction how to create a sample document from the scratch - add information -- what EXACTLY is unexpected -- and WHY do you believe it's unexpected (cite Help or Documentation!) -- concerning your PC -- concerning your OS (Version, Distribution, Language) -- concerning your LibO version (with Build ID if it's not a public release) and localization (UI language, Locale setting) –- Libo settings that might be related to your problems (video hardware acceleration ...) -- how you launch LibO and how you opened the sample document -- everything else crossing your mind after you read linked texts Even if you can not provide all demanded information, every little new information might bring the breakthrough. May be you can test <https://www.libreoffice.org/get-help/bug/> for submitting bug reports?
@Rainer Thanks for the report/update. I forgot to mention I'm using the portable apps version (i.e. both isnatnces mentioned in my initial report). Perhaps this helps. The original report is on a WinXP (with latest updates) Vaio laptop (SZ2XP) usign the protable apps versions. However the problem persists with version LibreOffice Windows, version 3.5.2, Greek (as stated in download page) Or as stated in About: LibreOffice 3.5.2.2 Build ID: 281b639-6baa1d3-ef66a77-d866f25-f36d45f installed on a Win7x64 (with latest updates) I'll be pleased to provide more info - Can you please be more specific as to what information is missing/you require? The Wiki list doesn't help, I think I have it covered already. Hope this helps - Thanks N.
The bug doen't occur for me in neither LibreOffice 3.5.5.3 Build ID: 7122e39-92ed229-498d286-15e43b4-d70da21 on Windows 7 Home (64 bit) nor LibreOffice 3.5.4.2 Build ID: 350m1(Build:2) on Ubuntu 12.04 (64 bit)
Bug is visible at LibreOffice Calc Version 3.6.4.3 (Build ID: 2ef5aff) Windows 7 Home Premium (English, 64bit) Service Pack 1. Finnish keymapping and dates. Asus desktop PC with AMD A8-3820 CPU. Entering -7198 to Calc cell and changing that to date form gives 15.04.1880 Entering -7199 to Calc cell and changing that to date form gives 13.04.1880 It seems that it is impossible to enter 14.04.1880 since there is no integer value between -7198 and -7199.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.