I found the problem during my research for "Bug 56988 - FILESAVE of particular .ods adds rows in sheet with comments" Steps how to reproduce with parallel installation of Master "LOdev 3.7.0.0.alpha0+ - ENGLISH UI / German Locale [Build ID: 70ec82)]" {tinderbox: @16, pull time 2012-11-09 00:53:19} on German WIN7 Home Premium (64bit) with separate User Profile for Master Branch: 0. download Sample document of Bug 56988 "Attachment 69904 [details]" 1. Open document from LibO start Center Expected: Sheet "REPORT" shoud show dates in column B Actual: integer numbers Strange: no problem with second sample of Bug 56988 Not reproducible with my own sample documents. Not reproducible with other versions I tested for Bug 56988 @sandrve7: Any ideas?
Confirmed as a regression. Works fine in 3.6.3.2 but problem shows up in 4.1.0.0.alpha0 Marking as NEW and adding regression to whiteboard status
Also changing platform to ALL as I verified this on Linux
Taking this
@moggi: This might be your construction site with conditional formats. The cells are assigned an automatic style style:name='ce3' style:data-style-name='N38' where N38 is the long date format. Additionally this style has <style:map style:condition='is-true-formula(OR(WEEKDAY([.A1])=7;WEEKDAY([.A1])=1))' style:base-cell-address='test.A1' style:apply-style-name='SabatoDomenicaScritteRosseGrassetto' /> to color weekends in red. Now that SabatoDomenicaScritteRosseGrassetto inherits from Default and other than bold and red does not set anything else and as such doesn't define it's own number format so that is General, this may be related or not. Somehow the cells' number format hard attribution is default General and the style's date format is not applied. Maybe you know ad hoc where to look at? If this is not related to your changes assign it back to me.
Looks like another problem being fixed by http://cgit.freedesktop.org/libreoffice/core/commit/?id=8a028afd55decfd269268d0d1e6adcfbdc9d85d0
Indeed, that change applied fixes this, so actually a duplicate. *** This bug has been marked as a duplicate of bug 58338 ***