Exporting the attached file (from odt) to docx sets the anchor of the text frame in the header to the body and additionally, MSO (2013) cannot open the file at all (displaying an import error)
A related regression was just fixed, see tdf#117805.
Steps to Reproduce:
1. Open Frames.odt in Writer
2. Export to docx
3. Open the docx in Writer/MSO
Frame in header is now in body + Import error at MSO 2013
Frame stays where it belongs and the file is not corrupted (for MSO)
User Profile Reset: No
You need a fresh master build from at least 19 July 2018 to reproduce
Created attachment 142920 [details]
ODT file cauing the bug
Created attachment 142921 [details]
DOCX export of the sample file
Wow, that was a fast catch!
Regression introduced by:
author Miklos Vajna <firstname.lastname@example.org> 2018-06-18 21:06:30 +0200
committer Miklos Vajna <email@example.com> 2018-06-19 09:02:59 +0200
commit 853350787df9a8d92c269ef1b6e764863e74ec2a (patch)
parent 3a8375eb974eb8ba36ac616478acd881b70f8e19 (diff)
tdf#117805 DOCX export: fix lost header with at-page anchored frames
The bug has two parts: on one hand, the header was not completely lost,
just was written inside a shape. This is not valid, but at least our own
import understood that. This commit restores that old behavior, focusing
on just the regression part of the bugreport.
On the other hand the exported header is still referenced at an
incorrect location: the correct location would be the end of the
document. But that is follow-up work, it seems that never worked.
Bisected with: bibisect-linux64-6.2
Adding Cc: to Miklos Vajna
I would not consider this as a regression. Commit
from Miklos (from yesterday) fixes the related bug
where there was no header at all in the same document export. The bug here is that the Writer export filter creates a corrupt docx file with a misplaced textframe. It seems this was never working correctly and it was "hidden" by the missing header.
Yes, basically there are 3 states:
- baseline: well-formed but not invalid output (but Writer can see the header)
- my earlier patch: valid output, but loosing header content
- my recent patch: restoring the header content
I agree with Patrick that exporting the header content in a valid way didn't work in the past either (for this situation).
I think the bug is caused by a missing header reference in the document.xml file. This should by the reason why Word refuses to open the file. The header reference (and the header file) are indeed created in sw/source/filter/ww8/docxexport.cxx:780.
But when the section properties are written in sw/source/filter/ww8/wrt8sty.cxx:1513 (called by sw/source/filter/ww8/docxattributeoutput.cxx:5900) the header reference is not present.
Miklos gave me a hint that is has to do with postponing the output of the section properties in docxattributeoutput.cxx:5910. But I wasn't able to follow that trace. I think I am missing some background knowledge on this topic.
Dear Patrick Jaap,
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Situation is unchanged in current master