Bug 146359 - Index for MS Word 2016 document created without special characters
Summary: Index for MS Word 2016 document created without special characters
Status: RESOLVED NOTOURBUG
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-21 15:25 UTC by arudd
Modified: 2022-11-28 12:46 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot (29.11 KB, image/png)
2021-12-21 15:27 UTC, arudd
Details
File with corrupted index entries (9.24 MB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2021-12-28 10:41 UTC, arudd
Details

Note You need to log in before you can comment on or make changes to this bug.
Description arudd 2021-12-21 15:25:24 UTC
The special characters in the marked index become lost
Comment 1 arudd 2021-12-21 15:27:04 UTC
Created attachment 177059 [details]
Screenshot
Comment 2 Ezinne 2021-12-28 10:07:24 UTC
Please can you add a sample file for testing?
Comment 3 arudd 2021-12-28 10:41:41 UTC
Created attachment 177169 [details]
File with corrupted index entries

I have done some experimenting with the faulty entries and have found the “problem”, if not the cause.
Incorrect index entries always have the form: {XE "entry:"}. If I remove the :, the index is displayed with page number; if I add an “:“ (without quotation marks) to a previously correct entry, the index is displayed without page number. What I do not know is how my document became corrupted! Because the problem concerns ALL marked indexed entries (many hundred), the “corruption” was some automated process; I may have been caused by merging Word documents.
Comment 4 QA Administrators 2021-12-29 03:58:28 UTC Comment hidden (obsolete)
Comment 5 arudd 2021-12-31 16:13:33 UTC
With further investigation, the problem was caused by corrupted index entries in the original Word document.
Comment 6 Buovjaga 2022-11-28 12:46:42 UTC
(In reply to arudd from comment #5)
> With further investigation, the problem was caused by corrupted index
> entries in the original Word document.

Ok, sounds like this can be closed.