<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - "About Libre Office" should enable copy (like it used to)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134445#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_UNCONFIRMED " title="UNCONFIRMED - "About Libre Office" should enable copy (like it used to)" href="https://bugs.documentfoundation.org/show_bug.cgi?id=134445">bug 134445</a> from <a class="email" href="mailto:telesto@surfxs.nl" title="Telesto <telesto@surfxs.nl>"> Telesto</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=134445#c6">comment #6</a>) > (In reply to Telesto from <a href="show_bug.cgi?id=134445#c1">comment #1</a>) > > And Heiko can't get enough of it. > > \o/ > > (In reply to Jan-Marek Glogowski from <a href="show_bug.cgi?id=134445#c3">comment #3</a>) > > And it would be nice, if someone could restore the Ctrl+C functionality, but > > I don't consider this essential with the button. > > That's the only option I would implement. The discussion where to place the > copy button was long and fruitless. Way too much bike-shedding. > > I suggest to bring this request into <a class="bz_bug_link bz_status_NEW " title="NEW - macOS: add keyboard shortcut ⌘W to close about dialog" href="show_bug.cgi?id=133728">bug 133728</a>, which I took as shortcut > enhancement ticket though it's about macOS. The discussion where to place the copy button was long and fruitless. -> Pointer please.. ; the smaller one with icon was more a surprise. Or did you attempt to dodge 'translation' discussion of <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTABUG - French translation missing in 'help' menu and in 'about LibreOfficeDev' window" href="show_bug.cgi?id=133662">bug 133662</a> this way (assume so) The version information shouldn't be translated at all.. would make the whole stupid issue go away.. The translation department is slightly obsessive in their opinion, IMHO. Or I'm underestimating the the user who complain few lines of technical terms being english as bad translation. While most translations produce some weird - awful - result (hmm, maybe I should start reporting bugs about awful 'about' window translations ;-). Surprising the didn't propose the macro language being localised too :-) So my preference.. don't translate those lines, period. Reintroduce the copy button with text label. Copy version info. The translation team should back off. As the never produced some meaningful translation anyhow; and the about is often not translated at all. Next best alternative: Copy version info. No tooltip nothing, about what the tooltip copies.. most user don't need it. So won't notice.. In the current setup nobody notice the button at all.. And does save some time when reporting a lot.. It's only an about dialog. Not a major component of the application, where you work with all day. Except if you report bugs (or those instances where you not aware which version you're running). I don't think people object against the button.. It didn't do what it supposed to do/ said to be doing (English only). Which ends up again with the translation team. Yes, I started the don't translate request. As Roman started to post a Russian about screen. Which is unreadable.. especially skia/vulkan/raster. Never thought we get such an endless fuzz about it :-( If people start selecting an copying a translated about screen again, we are back to where we started. Not the desired outcome ;-) As said the button is an improvement for regular reporters.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>