https://bugs.documentfoundation.org/show_bug.cgi?id=163842

            Bug ID: 163842
           Summary: XLS, XLSX Certain roundtripped spreadsheets not
                    opening in Excel due to regression
           Product: LibreOffice
           Version: 7.0.0.3 release
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: bibisected, bisected, regression
          Severity: normal
          Priority: medium
         Component: filters and storage
          Assignee: [email protected]
          Reporter: [email protected]
            Blocks: 104839

Created attachment 197535
  --> https://bugs.documentfoundation.org/attachment.cgi?id=197535&action=edit
forum-es-7576.xlsx

The attached files can all be opened in Excel in their current state.
Open them in LO, save them as XLSX, and try opening them in Excel.

=> Excel is unable to open the files, and shows error message.

Here's a list of some files from LO's bugzilla/forum files that are affected (a
few of those are attached):
forum-mso-de-63075.xls
forum-mso-en4-114468.xls
forum-mso-en4-268566.xls
forum-mso-en4-280967.xls
forum-mso-en4-52733.xls
forum-mso-en4-56244.xls
forum-mso-en4-67264.xls
forum-es-7576.xlsx

Not sure if the cause is the same, most have macros and form controls, where
some content used to get lost in the past, and it's still lost, but at least in
the past the roundtripped files could be opened in Excel.
All in the list regressed from the following commit, bibisected using
bibisect-win64-7.0:

https://cgit.freedesktop.org/libreoffice/core/commit/?id=fd238380ae7820f12ac1f7c52d0f7180a93f3ba3
author          Serge Krot <[email protected]>  2020-05-13 22:52:52 +0200
committer       Thorsten Behrens <[email protected]>      2020-05-26
00:20:54 +0200

tdf#106181 XLSX export: output form controls


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=104839
[Bug 104839] [META] Saved XLSX files that MS Excel can't open
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to