OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Commented: (OFFICE-2343) 3.3.3 Date andDateTime - 1900 as leap year

    [ http://tools.oasis-open.org/issues/browse/OFFICE-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17674#action_17674 ] 

Andreas Guelzow  commented on OFFICE-2343:

"Evaluators may accept expressions that treat 1900 as a leap year." What is that supposed to mean? How can an evaluator know whether an expression "treats 1900 as a leap year"?

"The number of days from a date is called an epoch. Epochs that shall be supported by evaluators are from 1904-01-01 through 9999-12-31. "  If the number of days froma date is called an epoch, then epaochs must be number of days not dates. SO this does not make sense.

"Use of the epoch date 1899-12-30 may compensate for expressions that depend upon the use of a 1900-02-29 date. " Why would one want to compensate for the use of a non-existing date? I suspect the intention is to falsify serial numbers prior to 1900-03-01 to hide a skip in the serial numbers (epoch?) between 1900-02-28 and 1900-03-01.

> 3.3.3 Date and DateTime - 1900 as leap year 
> --------------------------------------------
>                 Key: OFFICE-2343
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2343
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2 Part 2 CD 1
>            Reporter: Patrick Durusau
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 Part 2 CD 2
> Currently we say:
> ***
> Many applications cannot handle Date values before January 1, 1900. Some applications can handle dates for the years 1900 and on, but include a known defect: they incorrectly presume that 1900 was a leap year (1900 was not a leap year). Applications may reproduce the 1900-as-leap-year bug for compatibility purposes, but should not. 
> ***
> Rob Weir suggests that we should not make editorial comments about bugs, compatibility, etc. I think that is a good point. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]