Apache OpenOffice (AOO) Bugzilla – Issue 126768
odt files written by Libreoffice 4.2.8.2 will not open in OOWriter 4.1.2
Last modified: 2023-06-20 06:36:00 UTC
Created attachment 85237 [details] OpenOffice Document opened with LibreOffice Writer and saved as a LibreOffice odt file. Copied existing OO4.1.1 based file and opened in LibreOffice/4.2.8.2$Linux_x86 LibreOffice_project/420m0$Build-2. After saving OO4.1.2 would not open the file. Attempting to open odt files written or touched by LibreOffice produce the following message and will not open in Writer: Read-Error Error Reading file The odt file can be opened and read by an archive manager This is a severe issue as there is no way to differentiate files written by Libreoffice and those written by OO so it is possible to for a user using LibreOffice to corrupt and make unusable files written by even though the files are of an apparently identical type.
I confirm that the 174 kb file does not open with AOO 4.1.2. It does open with LibreOffice 5.0.0. It also opens with Microsoft Office 2016 Word. I do not confirm this to be a general error. It remains to determine what is unusual about this file that is treated as an error by AOO 4.1.2. ADDITIONAL TESTING With the supplied file opened in Microsoft Office 2016 Word, I enabled editing and saved the document, without any actual edits, as a different *.odt file. That 91kb file **crashes** AOO 4.1.2 and opens successfully in LibreOffice 5.0.0. CONFIRMATION With causes yet to be identified, there are apparently interoperable interchange problems with ODF files that appear to be valid and that cause AOO to fail to accept the document or even crash. It is confirmed that whatever the case, two other implementations of ODF can accept the document correctly.
I have added a link to LibreOffice bug number 96882 in the see-also. That bug is RESOLVED NOTOURBUG, but it can of course be reopened if LibreOffice is doing something wrong or unhelpful.
Add me,
This case is added to Issue 126846 because the document is unusable. It is not exactly a case of loss as the result of saving from Apache OpenOffice, but the Read Error situation might tell us something.
I tried to reproduce the issue with a debug build of the current trunk The problem is in SwXFrame::setPropertyValue(), called with property name "Title". An exception is thrown at the last line of the method (see file main/sw/source/core/unocore/unoframe.cxx around line 1936). Why it is impossible to set the "title" on a SwXFrame is unfortunately beyond my understanding. I hope this information helps anyway.
After further investigation, the problems were found to be the <svg:title> and <svg:desc> tags inside content.xml, tag <draw:frame draw:style-name="fr2" draw:name="graphics6" text:anchor-type="page" text:anchor-page-number="2" svg:x="2.5693in" svg:y="1.8091in" svg:width="1.378in" svg:height="1.378in" draw:z-index="1"> After removing those <svg:xxx> element AOO is able to open the document. Now it is time to understand: - is this a known issue? - is this due to XML data out of specifications?
The elements <svg:title> and <svg:desc> are valid ODF 1.2. Use of this elements is recommended for accessibility. Not opening the file or crash is clearly a bug in AOO. http://docs.oasis-open.org/office/v1.2/os/OpenDocument-v1.2-os-part1.html#__RefHeading__440376_826425813
I can still confirm this error in AOO 4.1.9 on Windows 10.
I propose a patch to fix this error: https://github.com/apache/openoffice/pull/12
(In reply to oooforum (fr) from comment #9) > I propose a patch to fix this error: > https://github.com/apache/openoffice/pull/12 While your PR may be valid (I didn't test), how should a change in an export filter fix an issue with opening files?
I have been waiting over 8 years for a resolution to this problem.
Waiting did never fix any problem...