https://bugs.documentfoundation.org/show_bug.cgi?id=160873

Stéphane Guillou (stragu) <stephane.guil...@libreoffice.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |stephane.guillou@libreoffic
                   |                            |e.org
             Blocks|                            |85811

--- Comment #1 from Stéphane Guillou (stragu) 
<stephane.guil...@libreoffice.org> ---
In essence, I agree that users might not use that submenu because of how
obscure the name is to them. But if we go further and actually rename from "OLE
object" to something else, there are many places where the term is used,
including the Navigator. And then there's hundreds of updates for help pages
and guides.
How would one differentiate OLE objects from others then? It would have to be
more verbose, like "Linked or Embedded Objects".

So I guess my opinion is: OK to not use "OLE" in the menu, but against changing
it to something else elsewhere.

(In reply to jan d from comment #0)
> I could not find out if QR-Code actually uses OLE,
> since there is no editing capability exposed and the result seems to be
> handeled as an image, which is what OLE actually should overcome.
I was actually wondering about that. Seems like QR/Barcode shouldn't be in
there anyway. And when the feature was recently shared on social media, users
were surprised it was so hidden away.

+1 to pull those out of the OLE submenu if possible, or use a more intuitive
categorisation so it doesn't get too big. (It's already the biggest menu in
Writer with View and Format.)
Also: chart is not in the OLE submenu, but it is an OLE object!


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=85811
[Bug 85811] [META] Main menu bar bugs and enhancements
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to