[Upstream] [hardy] OOo Writer index errors when entries have multiple hits and chapter numbers are enabled

[StephanBeal]

Binary package hint: openoffice.org

OOo Writer 2.2.0 on Kubuntu 7.04:

When creating an index there is the option to show Page numbers and/or Chapter numbers alongside each indexed word. When multiple entries exist for a given word AND Chapter numbers are turned on, OOoW only shows the LAST Chapter number associated with each entry is shown.

i am attaching 3 screenshots which demonstrate:

a) OOo-index-page-numbers.png:
correct/expected behaviour when only Page Numbers are enabled.

b) OOo-index-chapter-numbers.png:
incorrect (or unexpected) behaviour when Chapter numbers are enabled.

c) OOo-index-page-and-chapter-numbers.png
mixed correct/incorrect behaviour when both Page and Chapter numbers are enabled.
(Note that the "/" character in the entries was the defined Page/Chapter separator.)

Unless documented otherwise, i would expect the index to behave the same for both (a) and (b). In case (c) i would expect the entries (in the case of multiple hits) to look something like:

entry_key ....... page1/chap1, page2/chap2, page3/chap3
(where "/" is the user-defined separator for those fields in the Index editor dialog)

[Chris Cheney (ccheney)]

Does this problem still affect you on Ubuntu 7.10 or Ubuntu hardy? If so can you include an example document that exhibits this problem so I can send it to official (upstream) openoffice.org bugtracker.

Thanks,

Chris Cheney

[StephanBeal (sgbeal)]

On Thu, Mar 13, 2008 at 8:21 PM, Chris Cheney <email address hidden>
wrote:

> Does this problem still affect you on Ubuntu 7.10 or Ubuntu hardy?

Hi, Chris!

Yes, the behaviour is identical in OOo 2.3 on Ub7.10 (with all current
patches as of 2008.03.13). i don't yet have Hardy to try out, and all my
attempts at getting a buildable source tree of OOo (to try newer versions)
have ended in frustration.

> If so
> can you include an example document that exhibits this problem so I can
> send it to official (upstream) openoffice.org bugtracker.

Attached is an ODT which exhibits the various problems. To reproduce it:

- scroll all the way to end end (the index)

- right-click the index and click "Edit Index/Table"

- Click the Entries tab and look directly under the "Structure and
Formatting" label.

- Experiment by adding/removing "Chapter info" and "Page no." items from the
"Structure" list. After each change you'll need to right-click the Index and
"Update Index/Table".

:)

--
----- stephan beal
http://wanderinghorse.net/home/stephan/

[Chris Cheney (ccheney)]

Can you attach the file via the launchpad web interface it doesn't seem to attach them via the email.

Thanks,

Chris Cheney

[StephanBeal (sgbeal)]

Attached...

[Chris Cheney (ccheney)]

Confirmed on upstream's openoffice.org 2.4.0~rc5 and found upstream bug report relating to it.

[penalvch (penalvch)]

StephanBeal (sgbeal), please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 119097
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

Regarding your comment #5:
> - Experiment by adding/removing "Chapter info" and "Page no." items from the "Structure" list. After each change you'll need to right-click the Index and "Update Index/Table".

Could you please specify click for click what one must do to reproduce the problem?

Does LibreOffice work for you? If using Lucid or Maverick feel free to perform at the Terminal:

sudo add-apt-repository ppa:libreoffice/ppa && sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y install libreoffice-writer

[StephanBeal (sgbeal)]

Hi, Chris,

i'm sorry, but i honestly can't be bothered to go through this again. i submitted this bug more than 4 years ago and there has been no activity on it since then. All of the details, including an example doc which demonstrates the problem, are in this bug report.

[penalvch (penalvch)]

StephanBeal, we are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!