Issue 101798 - ISO 8601 timestamps with time zone not interpreted correctly
Summary: ISO 8601 timestamps with time zone not interpreted correctly
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: OOO310m9
Hardware: Mac Mac OS X, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-05-12 08:53 UTC by wdonne
Modified: 2013-01-29 21:39 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

A generated spreadsheet file (21.55 KB, application/vnd.oasis.opendocument.spreadsheet)
2009-05-12 08:54 UTC, wdonne
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description wdonne 2009-05-12 08:53:21 UTC
The office:date-value attribute of table:table-cell should comply to
xmlschema-2-20010502/#dateTime. When such a timestamp contains a time zone indicator it is not 
interpreted correctly when the document is opened. All those timestamps are set to 12/30/1899 
00:00:00. This is an example:

<table:table-cell office:date-value="2009-05-04T11:39:45Z" office

This also happens when the TZD has the form +/-hh:mm.
Comment 1 wdonne 2009-05-12 08:54:34 UTC
Created attachment 62183 [details]
A generated spreadsheet file
Comment 2 wdonne 2010-09-13 17:11:16 UTC
When such a value is used in tracked-changes for a deleted cell the annotation shows the old value as a 
floating number.