Bug 99234 - XLSX: New lines (CTRL+ENTER) in cell not saved correctly
Summary: XLSX: New lines (CTRL+ENTER) in cell not saved correctly
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.1.2.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-12 05:33 UTC by Lyuben Blagoev
Modified: 2016-04-14 13:40 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
XLSX file in which the new line is missing in Excel (4.75 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2016-04-12 05:33 UTC, Lyuben Blagoev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Lyuben Blagoev 2016-04-12 05:33:45 UTC
Created attachment 124266 [details]
XLSX file in which the new line is missing in Excel

The issue is still here in 5.1.2.2.

I saved two files (one in .xls and one in .xlsx format). Both looks good when opened in LibreOffice Calc, but when I open them in Excel (Excel 2010) the .xls file looks good, but the new line is not saved correctly in the .xlsx file.

The text is put in the cell is the following: 
Header
- Another line that must wrap

The word 'Header' is bolded. The missing new line is after the word 'Header' before the dash.

Related to https://bugs.documentfoundation.org/show_bug.cgi?id=89254
Comment 1 raal 2016-04-12 08:48:04 UTC
Hello, tested with Version: 5.2.0.0.alpha0+; win7 and seems to be fixed with dev version. Please could you test it with dev version?  You can download it here: http://dev-builds.libreoffice.org/daily/master/
Thank you
Comment 2 Lyuben Blagoev 2016-04-12 16:41:20 UTC
I've tested with the daily build of master. Seems it is fixed.
Any idea when it will be released?
Comment 3 raal 2016-04-12 18:32:16 UTC
Thanks for testing.

Release Plan 5.2
https://wiki.documentfoundation.org/ReleasePlan/5.2

but most of the fixes is backported to 5.1
https://wiki.documentfoundation.org/ReleasePlan/5.1
Comment 4 Lyuben Blagoev 2016-04-13 04:14:45 UTC
Thank you. What I meant was is there any plans to backport to 5.1.x and in which release? I think the fix for the original bug I posted (see the link in my first comment) was targeted to 5.1.
Comment 5 raal 2016-04-13 06:58:48 UTC
(In reply to Lyuben Blagoev from comment #4)
> Thank you. What I meant was is there any plans to backport to 5.1.x and in
> which release? I think the fix for the original bug I posted (see the link
> in my first comment) was targeted to 5.1.

It's hard to say, because we don't know the commit which fixed the bug. You can try to search in bugzilla for fixed bugs.
https://bugs.documentfoundation.org/query.cgi
Comment 6 Lyuben Blagoev 2016-04-14 12:33:19 UTC
(In reply to raal from comment #5)
> (In reply to Lyuben Blagoev from comment #4)
> > Thank you. What I meant was is there any plans to backport to 5.1.x and in
> > which release? I think the fix for the original bug I posted (see the link
> > in my first comment) was targeted to 5.1.
> 
> It's hard to say, because we don't know the commit which fixed the bug. You
> can try to search in bugzilla for fixed bugs.
> https://bugs.documentfoundation.org/query.cgi

This is the first bug that I submitted a while ago: https://bugs.documentfoundation.org/show_bug.cgi?id=89254

Another more recent bug that seems related is this one: https://bugs.documentfoundation.org/show_bug.cgi?id=96912
Comment 7 raal 2016-04-14 13:40:22 UTC
(In reply to Lyuben Blagoev from comment #6)

> 
> This is the first bug that I submitted a while ago:
> https://bugs.documentfoundation.org/show_bug.cgi?id=89254

 target:5.1.0 => the fix is in version 5.1.0
> 
> Another more recent bug that seems related is this one:
> https://bugs.documentfoundation.org/show_bug.cgi?id=96912

target:5.2.0 backportRequest:5.1 => the fix is in version 5.2. BackportRequest means the fix is not in 5.1 and we're waiting if some developer backport this fix into 5.1