Issue 125745 - cellType="d" not supported when reading MS Excel files
Summary: cellType="d" not supported when reading MS Excel files
Status: CLOSED DUPLICATE of issue 127034
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: 4.1.1
Hardware: All All
: P3 Normal (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: interop_OOXML
Depends on:
Blocks:
 
Reported: 2014-10-13 14:29 UTC by Charlie Clark
Modified: 2023-01-08 15:51 UTC (History)
2 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Charlie Clark 2014-10-13 14:29:50 UTC 
According to 18.18.11 ST_CellType (Cell Type) of the ECMA specification it is possible to set the type of the cell to "d" with a value formatted according to ISO 8601. 

"d (Date)
Cell contains a date in the ISO 8601 format."

Such cells will, however, be treated as empty cells by OpenOffice.org. This is a pity as it would allow us to ignore Excel's broken 1900-based calendar and simply pass ISO formats around.
Comment 1 oooforum (fr) 2014-10-23 08:41:25 UTC 
Don't understand that means cellType.
In Calc and MS-Excel, the function is CELL.
Both supports format codes as date.
Comment 2 Charlie Clark 2014-10-23 08:58:51 UTC 
The XSD for the "t" attribute of the cell.

<xsd:simpleType name="ST_CellType">
    <xsd:restriction base="xsd:string">
       <xsd:enumeration value="b"/>
       <xsd:enumeration value="d"/>
       <xsd:enumeration value="n"/>
       <xsd:enumeration value="e"/>
       <xsd:enumeration value="s"/>
       <xsd:enumeration value="str"/>
       <xsd:enumeration value="inlineStr"/>
    </xsd:restriction>
</xsd:simpleType>
Comment 3 damjan 2023-01-08 08:45:54 UTC 
This works now, it was just implemented as per bug 127034. Strictly speaking, that bug was filed after this one, and should be a duplicate of this one, but it was already closed so resolving this one as its duplicate.

*** This issue has been marked as a duplicate of issue 127034 ***