Created attachment 176082 [details] comparison English+German-GUI_TOC_IndexOrBibliography If the LO-GUI language is English everything is fine, if the LO-GUI language is German, the buttons 'Insert', 'Remove' and 'Tab Stop' for inserting alternate entries and for changing the structure of the bibliography and index in the GUI are missing' Table of Contents, Index or Bibliography '
Which LO version do you use? For your information, there are 7.1.6 or brand new 7.2.2 Please, give a try at least one of these.
I use LO 7.0.6 and 7.2.1, both as PortableApps. V 7.2.1 ist the newest LO on PortableApps. V 7.1.6 ist the newest LO Still on PortableApps, but crashes at startup The missung buttons are in both (7.0.6 and 7.2.1) LO-versions (German GUI).
Today I´d trying LO 7.1.6 (PortableApps). LO 7.1.6. don´t crash if I use it without Skia-Rendering. The missung buttons are also in LO 7.1.6.
Thank you for your feedback. No more idea so can't help here=>uncc myself.
I have tested the german gui: 1. going onto menu point "Einfügen" "Verzeichnis" 2. and selected "Verzeichnis..." for creating new table of content It seems this dialog have changed in newer versions a little bit: on the left side there is a list of "Ebenen". I use 7.2.2 (Debian 11) and have no problems with german buttons. And I know from the older Version 7.1.6 there I had no button problems in this dialog, too. Perhaps it is a font style problem. Or there is a compiling problem while create package for PortableApps.
I have tested the German GUI today in LO V6.4.7.2 in Linux (Ubuntu 20.04 LTS preinstalled). I had also no button problems in the 'Verzeichnis bearbeiten' dialog. The same LO version V6.4.7.2 as PortableApps for Windows show the button problem again. I agree with 'joomart', it might be a LO-PortableApps only. What to do? How is the connection to the LO-PortableApps team?
I have tested the German GUI today in LO Portable V7.2.5.2 Win7. I had no longer button problems in the 'Verzeichnis bearbeiten' dialog. I change the bug-status to resolved.
Setting to RESOLVED WORKSFORME since the commit fixing this issue hasn't been identified.