Bug 44152 - Duplicate alphabetical-index-mark entries
Summary: Duplicate alphabetical-index-mark entries
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version: 3.4.4 release
Hardware: All All
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-26 06:32 UTC by fox.talk
Modified: 2015-01-08 08:44 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments
File has the issue described above. (9.17 KB, application/vnd.oasis.opendocument.text)
2011-12-26 06:32 UTC, fox.talk
Details

Description fox.talk 2011-12-26 06:32:36 UTC
Created attachment 54824 [details]
File has the issue described above.

If one adds an alphabetical index to a ODT document with concordance file and modifies the concordance file entries several times, then all keyword occurences in the text will get duplicate "alphabetical-index-mark" entries like that:
<text:alphabetical-index-auto-mark-file
				xlink:href="../keywords.sdi" />
			<text:p text:style-name="Standard">
				<text:alphabetical-index-mark
					text:string-value="Test1" />
				<text:alphabetical-index-mark
					text:string-value="Test1" />
				<text:alphabetical-index-mark
					text:string-value="Test1" />
				Name1
			</text:p>


This behaviour may easily blow up the document and makes it hard to delete obsolete index entries.
Comment 1 Christian Lohmaier 2011-12-28 07:38:19 UTC
cannot reproduce with 3.5.0beta2 - please give a more detailed description on how to trigger the bug.

I did:
* create new document
* insert blindtext/dummytext
* Insert index, check concordance checkmark, create a new file
* add "Dilemma" as index entry (german blindtext contains that word) and closed the dialog, index is entered, the Dilemma in the text is flagged accordingly.

* save the file and verify that the index-mark is written to the document only once.

* Use edit index from the context-menu on the index, choose "Edit file" from the concordance-file button, change the ignore case toggle of the dilemma entry, close both dialogs.
* save the file and verify the xml → still only one index-mark.

* use edit index from the context-menu, choose edit file from the concordance-file button, add another word "Dunkelheit", apply & close the dialogs
* other word is added to the index and flagged in the document
* save and verify the xml → still only one entry on dilemma, only one entry on Dunkelheit.

Thus → needmoreinfo
(please also report back when you cannot reproduce yourself anymore in the current version)
Comment 2 fox.talk 2011-12-28 10:44:03 UTC
The description provided in last comment exactly describes the steps for triggering the bug.
but there are two additions:
* add "dilemma" as index entry and "Dilemma" as alternative entry.
* after saving and checking the XML you should close and re-open the ODT document before applying modifications to concordance file (It seems that the problem does not occur otherwise).

I can confirm that the problem still exists in LibreOffice 3.5 Beta 2.
Comment 3 Joel Madero 2014-11-06 20:31:31 UTC
Never confirmed by QA - moving to UNCONFIRMED.
Comment 4 Robinson Tryon (qubit) 2015-01-08 08:44:07 UTC
TESTING on Ubuntu 14.04 + LO Version: 4.5.0.0.alpha0+
Build ID: 5c60dab390d66a4d5abeaf548efecf3913b90839
TinderBox: Linux-rpm_deb-x86_64@46-TDF, 
Branch:master, 
Time: 2014-12-31_00:20:30
Locale: en_US

(In reply to Christian Lohmaier from comment #1)
> cannot reproduce with 3.5.0beta2 - please give a more detailed description
> on how to trigger the bug.
> 
> I did:
> * create new document
> * insert blindtext/dummytext

(using 'dt', then <F3>)

> * Insert index, check concordance checkmark, create a new file

I'm not sure where to find the 'concordance checkmark'...

pfux: Are you still seeing this problem with modern builds of LibreOffice?

Status -> NEEDINFO

(Please change status to UNCONFIRMED after you report back)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.