Bug 52396 - Missing index entries when these are on same position
Summary: Missing index entries when these are on same position
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.5.5.3 release
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks: TableofContents-Indexes
  Show dependency tree / graph
 
Reported: 2012-07-23 13:43 UTC by Jan Alwin de Jong
Modified: 2023-12-04 03:15 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Document created as described (53 bytes, text/url)
2013-03-06 12:42 UTC, bfoman (inactive) 		Details
Show Obsolete (1) View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Alwin de Jong 2012-07-23 13:43:09 UTC 
Source: https://issues.apache.org/ooo/show_bug.cgi?id=109659

When there are several index entries at the same place in a .doc file, only the 
first one is available when importing the file in Writer.

To reproduce:
1. Create a .doc (97/2000/XP) document in Microsoft Word with two index entries 
at the same place. It should look like {XE "This"}{XE "Test"}This is a test 
(where XE are special Word index tags). Save and close.
2. Open the file in OO.o.

Expected result: two index keys in OO.o, one "This" and one "Test".

Observed result: only one index key, the first one ("This").
Comment 1 Jan Alwin de Jong 2012-07-23 13:45:28 UTC 
This doesn't work in LibreOffice and OpenOffice. I could find a bug report for OpenOffice. I added this bug report here.

Regards,

Jan Alwin de Jong
Comment 2 bfoman (inactive) 2013-03-06 12:42:56 UTC 
Created attachment 76014 [details]
Document created as described
Comment 3 bfoman (inactive) 2013-03-06 13:02:04 UTC 
Comment on attachment 76014 [details]
Document created as described

Sorry for bug spam, this mime type recognition problem is annoying.
Comment 4 tommy27 2014-02-19 06:28:10 UTC 
@Jan
do you still experience this issue with current 4.1.5 or 4.2.0 final releases?
Comment 5 Owen Genat (retired) 2014-07-28 14:03:07 UTC 
This should be confirmed as the related Apache issue is confirmed. Status set to NEW.

(In reply to comment #4)
> do you still experience this issue with current 4.1.5 or 4.2.0 final
> releases?

The related Apache issue has an example DOC file that can be used for testing. I prepared an equivalent test file using an old copy of MSO2007 just to be sure. Same result opening it under GNU/Linux using v4.3.0.3 so it would appear the problem persists.
Comment 6 QA Administrators 2015-09-04 02:49:11 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2016-09-20 10:28:57 UTC Comment hidden (obsolete)
Comment 8 QA Administrators 2019-12-03 14:04:24 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2021-12-03 04:26:20 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2023-12-04 03:15:25 UTC 
Dear Jan Alwin de Jong,

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