Bug 133155 - EDITING DOCX: LibreOffice Mangles Microsoft Word Index after Update
Summary: EDITING DOCX: LibreOffice Mangles Microsoft Word Index after Update
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.3.5.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:docx
Depends on:
Blocks: DOCX-TableofContents
  Show dependency treegraph
 
Reported: 2020-05-18 20:55 UTC by Joel Madero
Modified: 2025-06-08 03:11 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Zipped File containing original test document, mangled example, and corresponding PDFs (136.68 KB, application/x-zip-compressed)
2020-05-18 20:56 UTC, Joel Madero
Details
The example document in Word and Writer master (140.23 KB, image/png)
2021-08-03 07:48 UTC, NISZ LibreOffice Team
Details
How it looks after updating (90.99 KB, image/png)
2021-08-03 08:19 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Joel Madero 2020-05-18 20:55:24 UTC
Description:
When updating an index created in Microsoft Office, LibreOffice completely mangles the index making it unsable.

Steps to Reproduce:
1. Open attached docx file which has basic index (Basic Word Index - Word.docx) with LibreOffice;
2. Right click on the index (note that the index looks fine when it's first opened)
3. Left click "Update index"

Actual Results:
Index is completely mangled. Page margins are not respected, page numbers no longer present for index, ellipses (...) way too long). Basically 100% unusable.

Expected Results:
Index should maintain its data and its structure after update.


Reproducible: Always


User Profile Reset: Yes



Additional Info:
I have no tested to see if this is a regression or not. I will try to do so later this evening. Confirmed that it exists in Linux and Windows, and that it happens in latest master build from yesterday.
Comment 1 Joel Madero 2020-05-18 20:56:54 UTC
Created attachment 160987 [details]
Zipped File containing original test document, mangled example, and corresponding PDFs
Comment 2 Dieter 2020-05-21 06:54:46 UTC
I confirm it with

Version: 7.0.0.0.alpha1+ (x64)
Build ID: 4804d969bacd25ad586b3bf70d3dc8c27adb48ef
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; 
Locale: en-GB (de_DE); UI: en-GB
Calc: threaded

and with

Version: 6.3.5.2 (x64)
Build-ID: dd0751754f11728f69b42ee2af66670068624673
CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; 
Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE
Calc: threaded
Comment 3 NISZ LibreOffice Team 2021-08-03 07:48:10 UTC
Created attachment 174036 [details]
The example document in Word and Writer master

How it looks after opening in:

Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community
Build ID: 7c38362dbe1922c9825dffb463072030948d406b
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: CL
Comment 4 NISZ LibreOffice Team 2021-08-03 08:19:34 UTC
Created attachment 174039 [details]
How it looks after updating

This is an alphabetical index made in Word with 3 columns. After opening it looks quite okay, only an extra empty paragraph was added since the document started with a continuous section break.

After update it falls apart spectacularly, getting the multicolumn alphabetical index formatting.

After inserting a new alphabetical index (the existing one is protected from manual changes so can't really investigate what's going on) it looks like:
- there is an extra tabulator at the end of each paragraphs at 16.51 cm
- the entries are incorrectly separated such as "Another One:Nothing Interesting" is one paragraph instead of being split to two at the :
- related to the previous one, the last index entries are lost that belong to Test 3: the See nothing interesting part is just gone.
Comment 5 Justin L 2023-06-08 16:52:05 UTC
repro 7.6
Comment 6 QA Administrators 2025-06-08 03:11:49 UTC
Dear Joel Madero,

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 https://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://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug