Bug 88634 - FILEOPEN: Incompatibly with Excel cells that contain ALT+ENTER
Summary: FILEOPEN: Incompatibly with Excel cells that contain ALT+ENTER
Status: RESOLVED DUPLICATE of bug 56036
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.5.2 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-20 17:35 UTC by Ed
Modified: 2015-01-20 23:24 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example of Excel 2010 ALT+ENTER problem (90.39 KB, application/vnd.ms-excel)
2015-01-20 17:35 UTC, Ed
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ed 2015-01-20 17:35:17 UTC
Created attachment 112559 [details]
Example of Excel 2010 ALT+ENTER problem

Impossible to successfully open Excel sheets.

Any Excel sheet's cells which contain ALT+ENTER are truncated.  All formula information after the ALT+ENTER is lost.  Any such cells are/can be flagged with an "Err:501"

ALT+ENTER is used to make formulas, especially nested IFs, more readable.  CTRL+ENTER is the LibreOffice equivalent.

At a minimum the ALT+ENTER should not cause the formula to be truncated.  You may lose the readability and put the formula as one long character string, but the formula data must be preserved.  (The preferred solution is to maintain the readability and convert the ALT+ENTER to CTRL+ENTER)

From the attached Excel 2010 sheet, cell BQ8, where <ALT-ENT> represents ALT+ENTER:

=IF(AR8=0,0,<ALT-ENT>
IF(AR8>82,2,<ALT-ENT>
(IF(AR8<51,-1,VLOOKUP(AR8,AdjTbl,3,FALSE)))))

When opened by LibreOffice the cell contains the following single line, which in this case results in an Err:501

=IF(AR8=0,0,)
Comment 1 raal 2015-01-20 21:48:36 UTC
I can confirm with Version: 4.5.0.0.alpha0+

The same request for ODF format in bug 76310
Comment 2 m_a_riosv 2015-01-20 23:24:22 UTC
It think this is a duplicate, please if you are not agree reopen it.

*** This bug has been marked as a duplicate of bug 56036 ***