Date: prev next · Thread: first prev next last
March 2015 Archives by date, by thread · List index


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

            Bug ID: 89830
           Summary: Ambiguous naming of character background
           Product: LibreOffice
           Version: Inherited From OOo
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: ux-advise
          Assignee: libreoffice-bugs@lists.freedesktop.org
          Reporter: zolnaitamas2000@gmail.com
                CC: libreoffice-ux-advise@lists.freedesktop.org

Character background has two names in LibreOffice. On character dialog it is
called "Background" (a tab page) on the toolbar (and sidebar) it is called
"Highlighting".

These two names make harder to solve an old MSO compatibility issue:
https://bugs.documentfoundation.org/show_bug.cgi?id=64490

From a user point of view the name "character background" can be closer to MSO
shading in meaning while "highlighting" can be closer to MSO highlighting. If
LO would have only one name for character background, then it will be
unambiguous to which MSO property to export it (by now RTF export saves it as
MS highlighting, while DOC and DOCX filters export it to MSO shading) and it
also would be clear our users which property can they expect when open an LO
exported MSO document.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.