Issue 57704 - bad XLS number format should trigger: ""File error: Some number formats may have been lost."
Summary: bad XLS number format should trigger: ""File error: Some number formats may h...
Status: CONFIRMED
Alias: None
Product: Calc
Classification: Application
Component: open-import (show other issues)
Version: OOO 2.0 Beta2
Hardware: PC Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-10 19:01 UTC by markjugg
Modified: 2013-08-07 15:12 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
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 markjugg 2005-11-10 19:01:44 UTC 
When opening an Excel document with an ill-formatted number, OOo 2 silently 
discards the format, while Excel provides a warning: "File error: Some number 
formats may have been lost."  The warning is helpful is finding the bug.  
 
This compatibility is also important because I use OOo to test Excel files I 
generate with Perl. The file looks fine to me, but Excel users see an error.  
 
The invalid format I used was:  
$"#,##0.00 
 
(A leading quote was missing). This was generated with the 
Spreadsheet::WriteExcel perl module. Perhaps it's not even possible for files 
that originate in Excel.  
 
Once I corrected the format by adding the leading quote, both Excel and 
OpenOffice behaved the same in this regard.  
 
Mac Excel v.X gave this error. I believe my collaborator was using Windows 
Excel 2003 when she got the error.
Comment 1 frank 2006-02-17 11:25:17 UTC 
Hi,

not a defect but an enhancement. Requirements have to decide how to proceed.

Frank