<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - LO7: Tooltips in cui/messages.po contain variable %MOD1 instead of string" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130979#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - LO7: Tooltips in cui/messages.po contain variable %MOD1 instead of string" href="https://bugs.documentfoundation.org/show_bug.cgi?id=130979">bug 130979</a> from <a class="email" href="mailto:ming.v.hua@qq.com" title="Ming Hua <ming.v.hua@qq.com>"> Ming Hua</a> <pre>(In reply to Mike Kaganski from <a href="show_bug.cgi?id=130979#c6">comment #6</a>) > (2) could allow for following extension, where you would provide a UNO name > instead, to convert it to key combination, and it would get actual key > combination -> additionally automatic account for localization differences > (some have different default key combinations) and even user-defined > preferences. I'd like to chime in that the benefit of accounting for l10n differences is not hypothetical, but already existent in current tips, namely <a href="https://opengrok.libreoffice.org/xref/core/cui/inc/tipoftheday.hrc?r=728548f8#88">https://opengrok.libreoffice.org/xref/core/cui/inc/tipoftheday.hrc?r=728548f8#88</a> "Need to insert the date in a spreadsheet cell? Type %MOD1+; or Shift+%MOD1+; to insert the time." Here many locales don't have an easy-to-access semicolon key, and use %MOD1+, and Shift+%MOD1+, (comma instead of semicolon) instead. Such a change would save the translators from double-checking to make sure their localized UI and TotD match, as evidenced in the following mailing list thread: <a href="https://listarchives.libreoffice.org/global/l10n/2020/msg00340.html">https://listarchives.libreoffice.org/global/l10n/2020/msg00340.html</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>