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

            Bug ID: 160310
           Summary: FILEOPEN: Minor error reported when moving between
                    calc and excel
           Product: LibreOffice
           Version: 24.2.1.2 release
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: minor
          Priority: medium
         Component: Calc
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: pthompson2...@gmail.com

Description:
If I edit a spreadsheet in Calc, save it and then edit it in MS Excel, Excel
reports "We found a problem with some content in '<File Name>'. Do you want us
to try to recover as much as we can?"

The error occurs because I use Calc and send spreadsheets to others who use MS
Excel.

Steps to Reproduce:
1. Edit a file in Calc and save it
2. Open the file in MS Excel
3.

Actual Results:
The above error is displayed in MS Excel. The error is then corrected by MS
Excel and Excel reports "Repaired records. Drawing from
/xl/drawings/drawing1.xml pare (Drawing shape)"

Expected Results:
MS Excel should be able to open the file without error.


Reproducible: Always


User Profile Reset: No

Additional Info:
XML Error file
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<recoveryLog
xmlns="http://schemas.openxmlformats.org/spreadsheetml/2006/main";><logFileName>error047120_01.xml</logFileName><summary>Errors
were detected in file
'https://d.docs.live.net/3eec8a413510c938/Documents/Apartments -
Sydney/2023-2024/Rent Income -
Test.xlsx'</summary><repairedRecords><repairedRecord>Repaired Records: Drawing
from /xl/drawings/drawing1.xml part (Drawing
shape)</repairedRecord><repairedRecord>Repaired Records: Drawing from
/xl/drawings/drawing2.xml part (Drawing
shape)</repairedRecord><repairedRecord>Repaired Records: Drawing from
/xl/drawings/drawing3.xml part (Drawing
shape)</repairedRecord></repairedRecords></recoveryLog>

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to