Description: When run with localized UI, the translation of toolbar names are saved in the user profile. So if the UI translators change the translation in a future version, the user with old user profile will still see the old translation. This is different behavior than the rest of the UI (where translation changes are always shown in new versions), and seems not intended, or at least not documented. Steps to Reproduce: 1. Start LibreOffice with a fresh user profile and localized (non-English) UI. 2. Open Impress, enable for example "Outline" toolbar via menu "View > Toolbars > Outline". 3. Close LibreOffice, view the content of the user profile file $USER_PROFILE_DIR/user/registrymodifications.xcu, see a line containing the translated name of the toolbar enabled in step 2, in my case (zh-CN UI): <item oor:path="/org.openoffice.Office.UI.ImpressWindowState/UIElements/States/org.openoffice.Office.UI.WindowState:WindowStateType['private:resource/toolbar/outlinetoolbar']/UIName"><value xml:lang="zh-CN">提纲</value></item> 4. (Optional and harder to do) Change the translation of this name, in file translations/source/<locale>/officecfg/openoffice/Office/UI.po, search for KeyID 92W6B. Rebuild LibreOffice with new translation, install and start new LO, observe that translation is not updated. Delete old user profile or start in Safe Mode, observe that translation is updated now. Expected Result: Translated names not saved in user profile. At least not explicitly enabled, i.e. an (expert?) option defaulting to no. Version Information: The steps above are tested with 7.1.7 on Windows 10: Version: 7.1.7.2 (x64) / LibreOffice Community Build ID: c6a4e3954236145e2acb0b65f68614365aeee33f CPU threads: 2; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: threaded But I also experienced the same "toolbar name translation not updated" issue with 7.3/master daily build, presumably the same cause: Version: 7.3.0.0.alpha1+ (x64) / LibreOffice Community Build ID: c7500945fc5d5bd2130a2d38be0bd4b15445cd90 CPU threads: 2; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: threaded
(In reply to Ming Hua from comment #0) > 2. Open Impress, enable for example "Outline" toolbar via menu "View > > Toolbars > Outline". > > [...] > > The steps above are tested with 7.1.7 on Windows 10: > Version: 7.1.7.2 (x64) / LibreOffice Community > Build ID: c6a4e3954236145e2acb0b65f68614365aeee33f One more thing for people who are interested in reproducing but lacking resources to rebuild LO -- the zh-CN translation for this "Outline" toolbar in Impress changed between 7.1.6 and 7.1.7, so can be used to test without manually editing the translation and rebuilding LO.
Yes, I can reproduce this on master. In short: 1. Build commit A (enable any lang pack). 2. Make sure no ./instdir/user exist. Run your build with your langpack, then enable "Outline" toolbar via menu "View > Toolbars > Outline". -> Now the translation of the the toolbar name is “hardcoded” in registrymodifications.xcu of the user profile. 3. Change the translation in translations/source/<locale>/officecfg/openoffice/Office/UI.po for KeyID 92W6B. Rebuild without `make clean`, then run your build. -> Toolbar name not updated. This issue had impact on release builds. Assume a user installed version A, and a translation is updated in version B, the user will not see the translation updates unless he/she removes the user profile. Actually I can see multiple such names in registrymodifications.xcu.
Change component to LibreOffice as this is a UI coding issue rather than a translation issue.
(In reply to Kevin Suo from comment #2) > Actually I can see multiple such names in registrymodifications.xcu. I believe all active toolbars, whether active by default or manually activated by user, in all modules that are started at least once, get their translated (and the original English one, for that matter) names stored in user profile.
Dear Ming Hua, 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 with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. 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) from https://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: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug