To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=52088





------- Additional comments from [EMAIL PROTECTED] Thu Oct 11 15:19:06 +0000 
2007 -------
I've attached a patch for this issue. The issue depends on which way round the
index marks are.
If you have an index mark with no key first, then use the text from that mark as
the key for a second index mark all is well. However if you do it the other way
round you get the duplicate entry.
This is because SwTOXBaseSection::GetKeyRange won't find the existing entry for
the primary key if it's a proper index entry rather than a dummy custom entry.
This patch removes the condition that the existing entry be a custom entry
fixing the problem.
Sorry for not explaining it better - test it and you will see it works.


---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to