[Bug 122473] New: Spontanious switch to NullDate 1904-01-01

[bu...@apache.org]

https://issues.apache.org/ooo/show_bug.cgi?id=122473

            Bug ID: 122473
        Issue Type: DEFECT
           Summary: Spontanious switch to NullDate 1904-01-01
           Product: Calc
           Version: AOO 3.4.1
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: configuration
          Assignee: issues@openoffice.apache.org
          Reporter: villeroy@t-online.de
                CC: issues@openoffice.apache.org

The problem of spontanious moving base dates (1899-12-30 --> 1904-01-01) comes
up every now and then:
http://forum.openoffice.org/en/forum/viewtopic.php?f=9&t=56521
Some day I found that my brand new documents (not from my default template) are
based on 1904-01-01. CSV always gets imported into brand new documents and when
you copy data from a "sick" document to a regular ODF document my imported and
copied dates are off by minus 4 years and 2 days:
http://forum.openoffice.org/en/forum/viewtopic.php?f=9&t=56521&p=270485#p270483

<snip registrymodifications.xcu>

<item oor:path="/org.openoffice.Office.Calc/Calculate/Other/Date">
  <prop oor:name="DD" oor:op="fuse"><value>1</value></prop>
</item>
<item oor:path="/org.openoffice.Office.Calc/Calculate/Other/Date">
  <prop oor:name="MM" oor:op="fuse"><value>1</value></prop>
</item>
<item oor:path="/org.openoffice.Office.Calc/Calculate/Other/Date">
  <prop oor:name="YY" oor:op="fuse"><value>1904</value></prop>
</item>

</snip>

I have no idea what may have caused this change.
I can not imagine any situation where this automatic change to a global default
setting would make any sense. But something in this software must have written
the offending xml into that file.

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

[Bug 122473] Spontanious switch to NullDate 1904-01-01

[bu...@apache.org]

https://issues.apache.org/ooo/show_bug.cgi?id=122473

Edwin Sharp <el...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |elish@apache.org
         Resolution|---                         |IRREPRODUCIBLE

--- Comment #1 from Edwin Sharp <el...@apache.org> ---
No problem with 20130415.csv.

AOO410m1(Build:9750)  -  Rev. 1548193
2013-12-07_04:10:48 - Rev. 1548790
Debian

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.

[Bug 122473] Spontanious switch to NullDate 1904-01-01

[bu...@apache.org]

https://issues.apache.org/ooo/show_bug.cgi?id=122473

--- Comment #2 from Andreas Säger <vi...@t-online.de> ---
Indeed, the csv file does not trigger that problem. The problem occurs
spontaniously and it happened to be that file when the problem hit me after
reading many times about the spontanious switch from 1899-12-30 to 1904-01-01.
Normally the NullDate setting is an optional part of an ODF document. A csv
file does not have any settings. The NullDate defaults to 1899-12-30. When the
mysterious switch occured on my system I found the above mentioned entry in
registry_modifications.xcu which seems to override the default so the
spreadsheet model of the csv file uses 1904-01-01 as NullDate.
Something in the application writes this modified default into
registry_modifications.xcu, and being a very experienced Calc user I can not
think of any occasion where this would make any sense.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
You are watching all bug changes.