Bug 61261

Summary: FILEOPEN: carriage returns in XLSX causes truncated formulas
Product: LibreOffice Reporter: Jason <jasonp_austin>
Component: CalcAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: jasonp_austin
Priority: medium    
Version: 4.0.0.3 release   
Hardware: x86 (IA32)   
OS: macOS (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: file that has described issue

Description Jason 2013-02-22 04:52:19 UTC
Created attachment 75288 [details]
file that has described issue

When imnporting an XLSX spreadsheet any carriage returns in formulas are dropped and the rest of the formula is truncated.  The CR can either be preserved or removed but the formula should not be mangled.

AOO 3.3.0 has the same issue.  AOO 3.4.1 fixes the issue but has a text replication bug so it isn't usable either.

I've attached the spreadsheet.  Issue can be seen in Sheet "Line 44" cell Z34 (must unprotect sheet to see formula).


Thanks!
Comment 1 Jorendc 2013-02-23 23:16:09 UTC
hi Jason

Is it possible to attach a screenshot which compares LibreOffice with MS Office? 
I think I can't reproduce this using Mac OSX 10.8.2, LibreOffice 4.0.0.3.

Thanks in advance,
Joren
Comment 2 Jorendc 2013-02-23 23:17:53 UTC
(ps: what's the password for that file?) If this is personal, please edit the password and add that file again as attachment.

Kind regards,
Joren
Comment 3 Jason 2013-02-24 03:13:49 UTC
Shouldn't need a password, at least I didn't to unprotect certain sheets.
Comment 4 Jason 2013-02-24 03:20:11 UTC
Hi Joren. Are you saying that you see the entire formula in cell Z34 of Sheet "line 44"?  The entire formula is this:

=IF(T30<=SectB_a3,ROUND((T30*(SectB_b3/100)-SectB_d3),0),
IF(T30<=SectB_a4,ROUND((T30*(SectB_b4/100)-SectB_d4),0),
IF(T30<=SectB_a5,ROUND((T30*(SectB_b5/100)-SectB_d5),0),
ROUND((T30*(SectB_b6/100)-SectB_d6),0))))

but instead I get this:

=IF(T30<=SectB_a3,ROUND((T30*(SectB_b3/100)-SectB_d3),0),0)

I don't have access to MS Office at home (thus why I'm trying to use LO or AOO).  I'll open up the spreadsheet at work and grab a screenshot.

-Jason


(In reply to comment #1)
> hi Jason
> 
> Is it possible to attach a screenshot which compares LibreOffice with MS
> Office? 
> I think I can't reproduce this using Mac OSX 10.8.2, LibreOffice 4.0.0.3.
> 
> Thanks in advance,
> Joren
Comment 5 QA Administrators 2013-09-24 01:59:06 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 6 QA Administrators 2013-10-25 15:16:54 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO