1. Open a new text document. 2. Insert table of contents into it (Insert - Table of Contents and Index - Table of Contents, Index or Bibliograpyh - OK). 3. Right-click to the inserted table of contents. You will see the commands "Update/Edit/Delete Index", even if they are related to the table of contents. Till to the 5.1 version, these commands were correctly named as "Update/Edit/Delete Index or Table of Contents".
Hello Stainislav, *, I can confirm your bug with OS: Debian Testing AMD64 LO Version: 5.2.0.3 Build-ID: 7dbd85f5a18cfeaf6801c594fc43a5edadc2df0c CPU-Threads: 4; BS-Version: Linux 4.5; UI-Render: Standard; Gebietsschema: de-DE (de_DE.UTF-8) (parallel installed, following the instructions from https://wiki.documentfoundation.org/Installing_in_parallel/Linux) In LO: Version: 5.1.5.1 Build ID: 1:5.1.5~rc1-1 CPU Threads: 4; OS Version: Linux 4.5; UI Render: GL; Locale: de-DE (de_DE.UTF-8); Calc: group (Debian's own version) it is "Update Index or Table of Contents", "Edit..." and "Delete...", so it seems a regression to former versions ... :( HTH Thomas.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.4.1 or 5.3.6 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170901
Still reproducible in 5.3.1.
Now it's more slick. But let's ask for an opinion. And find an explanation.
Don't remember the request nor find the patch but doesn't the change make sense to you? I mean a table of contents is a special index and the long string has no advantage for the user. Actually the text "Apply Foo _or_ Bar" makes me wonder if there are similar commands doing only one of the two options. So it's a clear WFM (and 2 years old anyway).
The change probably makes sense in English as the word "index" means both special type of index and general term for indexes, but: - it might not work in other languages, e.g. "index"-"rejstřík" in Czech cannot be used as general term (and this bugreport says that it is used incorrectly), - using of ambiguous terms increases confusion of localizers, it would be much clearer if we have "index" and "real special index" (I don't know which word is proper for it). Your note about preferring general terms over list of specific terms is interesting, but I can imagine cases where the list is useful for users (e.g. in searching for menu item names). In any case, the current state of index related items is really inconsistent - menu item or dialog title is in the long form.