For non-Latin based languages, such as Chinese, the mnemonic letters (keyboard accelerators) are usually put in paratheses after the translated string. Example: For opening a file, the "~Open" string is translated to "打开 (~O)" (or "OpenInChinese (~O)" for those having problem displaying Chinese). This works well for the menu items, as the "O" letter is rendered with an underline, and Chinese users are used to such notation for mnemonic letters. However, the same string seems to be also used for the pop-up tooltip of the "Open" icon on the toolbar, just without the underline. So when a Chinese user mouse-over the icon, he/she sees "打开 (O)" and wouldn't know what the "(O)" part means. For Latin based language with in-line mnemonic letters this approach works fine, however for non-Latin based language this is cumbersome and confusing. Obviously make these two separate strings for translation would work, but that adds a lot of strings for all the languages, many of which unnecessarily. Hope someone will have a better solution.
@Sophi, what is your opinion here ?
I need to investigate, but there seems to be a confusion between mnemonics (underlined letter rendered with a ~ in translation) and the shortcut key which is the one between parenthesis in the tooltip i.e. in en_US version: Open (Ctrl+O). They are not the same strings, tooltips are part of the help files while menu strings are part of the UI files and shortcut keys are not localized. So I will discuss it with the Chinese translation team.
Created attachment 150806 [details] Screenshot of the tooltip described in the original report Hmm, it seems my original report was not clear enough. Attached is a screenshot of the problem I was describing - mnemonic letter in the tooltip. The "打开" part is the Chinese translation of "Open", the "(O)" is what I was complaining about, and the final "(Ctrl+O)" is the keyboard shortcut that I have no problem with. There was no confusion between the mnemonics and the shortcuts. Thanks for looking into this report.
Is there any progress on this bug? Can I at least get a confirmation that my problem is well understood? This "unconfirmed" status is rather unassuring. :-( @Sophie, did you discuss with the zh_CN translation team? Or should I try to contact them myself?
So I tried the keyID feature in 6.3.0 alpha1, and both the "File -> Open..." menu item and the open icon tooltip has the keyID EKctU. I assume this confirms that they are using the same translation.
So DaeHyun confirmed: ------------------------- Here's the strings in the source tree: https://cgit.freedesktop.org/libreoffice/core/tree/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu#n5332 I'm specifically using "Find & Rep~lace..." as a query keyword here but I suspect the other offending strings are also in this file. The underline formatting is ignored in the non-localized toolbar icon tooltip unfortunately this won't work for non-English locales as the accelerator key is denoted separately. -------------------------- Set as confirmed.
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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
No longer reproducible in 7.4.5: Version: 7.4.5.1 (x64) / LibreOffice Community Build ID: 9c0871452b3918c1019dde9bfac75448afc4b57f CPU threads: 12; OS: Windows 10.0 Build 22621; UI render: default; VCL: win Locale: zh-CN (zh_CN); UI: zh-CN Calc: CL I vaguely remember reading about some developer working on this, probably Caolan. Don't want to dig into git logs to find out the exact commit fixing this bug, though, so to WORKSFORME for now.