[Libreoffice-ux-advise] [Bug 155205] Why is a menu called "Data", when it has processing functions?
https://bugs.documentfoundation.org/show_bug.cgi?id=155205 Roman Kuznetsov <79045_79...@mail.ru> changed: What|Removed |Added Keywords||needsUXEval CC||79045_79...@mail.ru, ||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #1 from Roman Kuznetsov <79045_79...@mail.ru> --- The difference is Insert something, not only data Wirk with Data I dislike the idea, -250 from my side -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 155131] Differentiate between lines in LO Base table editor and viewer with alternating shades.
https://bugs.documentfoundation.org/show_bug.cgi?id=155131 --- Comment #7 from Gerhard Weydt --- An option to set alternating colours or shadings, as is possible for tables in dialogs or in Writer, would indeed be helpful in some cases. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 155153] Calc: menu item "Format - Group" should be more clear
https://bugs.documentfoundation.org/show_bug.cgi?id=155153 --- Comment #5 from Heiko Tietze --- Code pointer: .uno:GroupMenu in [1] and in [2] (both labels are "Group") AFAICS all apps (sw*, sc, sd*) collect the commands .uno:FormatGroup, .uno:FormatUngroup, .uno:EnterGroup, and .uno:LeaveGroup under this submenu. Calc has a context menu for drawing objects with this submenu. [1] officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu [2] officecfg/registry/data/org/openoffice/Office/UI/DrawImpressCommands.xcu -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 155153] Calc: menu item "Format - Group" should be more clear
https://bugs.documentfoundation.org/show_bug.cgi?id=155153 --- Comment #4 from Heiko Tietze --- (In reply to Roman Kuznetsov from comment #2) > Format - Shapes Group may be? +1, yet it reads strange -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153623] [Character styles] Make more clear that the font used is from the paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=153623 --- Comment #8 from Mike Kaganski --- (In reply to Heiko Tietze from comment #7) > I wonder if there is more than font name. Every property of a character style can appear in a paragraph style. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153623] [Character styles] Make more clear that the font used is from the paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=153623 --- Comment #7 from Heiko Tietze --- This particular case is about one attribute of CS that clashes with the same attribute on PS. I wonder if there is more than font name. As a potential solution we could add the font "[Default]" to the list. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153623] [Character styles] Make more clear that the font used is from the paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=153623 --- Comment #6 from Mike Kaganski --- (In reply to Mike Kaganski from comment #5) > Basically, this is a part of bug 88559. And there, in bug 88559 comment 17, I argued that the character styles' "some properties unspecified" are a separate issue :-) So this one could be it :) -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153623] [Character styles] Make more clear that the font used is from the paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=153623 --- Comment #5 from Mike Kaganski --- Basically, this is a part of bug 88559. The said bug 88559 is about display of *any* case when any property is not defined in this style; and the specific case when *the whole hierarchy* of styles (of a specific kind) does not define such a property should be resolved together (and character styles are not some kind of an edge case). We definitely need to use *some* font for preview. But the preview can have a tooltip or another notification that "properties not defined in the character style and its ancestors are taken from document's defaults". The fields themselves should have the indication of inheritance (bug 88559) and some indication that no inherited value exist, to address what RGB reports. Note that Liberation Serif is the hardcoded *default* for a new document, and can de changed (with the awful, not intuitive, and actually misleading UI) - see bug 152537. It is *not* the same as Paragraph's Default style's font, but the UI in the Options dialog affects them both. (In reply to Heiko Tietze from comment #3) > That's what the Styles Inspector was introduced for (the 6th item on the > Sidebar). > > => NAB/WF :) Please see bug 88559 comment 10 ;) -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153623] [Character styles] Make more clear that the font used is from the paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=153623 --- Comment #4 from RGB --- (In reply to Heiko Tietze from comment #3) > (In reply to RGB from comment #0) > > Liberation Serif seems to be hard-coded... > CS attributes are independent from PS; the only way to solve the problem is > to not being able to change the font on CS. If you make Emphasis, as an > example, inherit from Bullets the font will be OpenSymbol; using the PS as > default sounds wrong to me. > > > Some clear way of knowing when the base font will be used... > That's what the Styles Inspector was introduced for (the 6th item on the > Sidebar). > > => NAB/WF I hope you agree that if you see one thing on the style editor while creating the style and a completely different thing on the style inspector then you have a consistency problem. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 153623] [Character styles] Make more clear that the font used is from the paragraph style
https://bugs.documentfoundation.org/show_bug.cgi?id=153623 Heiko Tietze changed: What|Removed |Added CC||mikekagan...@hotmail.com --- Comment #3 from Heiko Tietze --- (In reply to RGB from comment #0) > Liberation Serif seems to be hard-coded... CS attributes are independent from PS; the only way to solve the problem is to not being able to change the font on CS. If you make Emphasis, as an example, inherit from Bullets the font will be OpenSymbol; using the PS as default sounds wrong to me. > Some clear way of knowing when the base font will be used... That's what the Styles Inspector was introduced for (the 6th item on the Sidebar). => NAB/WF -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 154795] Font selection pane offers choice of "language" - which isn't.
https://bugs.documentfoundation.org/show_bug.cgi?id=154795 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #5 from Heiko Tietze --- (In reply to Eyal Rozenberg from comment #4) > (In reply to Heiko Tietze from comment #3) > > So you suggest to have a separate dropdown for Country in the font tab, > > probably one for all three groups? > > I can't suggest that, because the whole situation is invalid: Font selection > has nothing to do with language or country selection. Not a topic for UX then (likely a duplicate). -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 154795] Font selection pane offers choice of "language" - which isn't.
https://bugs.documentfoundation.org/show_bug.cgi?id=154795 --- Comment #4 from Eyal Rozenberg --- (In reply to Heiko Tietze from comment #3) > So you suggest to have a separate dropdown for Country in the font tab, > probably one for all three groups? I can't suggest that, because the whole situation is invalid: Font selection has nothing to do with language or country selection. If we did that, however, it would resolve this particular bug, while maintaining, perhaps even underlining, the bug of having country/locale selection in the wrong place. I suppose that would be an improvement over the current state of affairs. As for the deeper solution... I'll first say that I think there should be a deep paradigmatic discussion about these issues. Possibly even deeper than at the LibreOffice app level. I'll then say that maybe it makes sense for the choice of locale to be outside the app, tied to the choice of keyboard layout. Because there's no reason the user should not be able to enter text in multiple locales in the same language group, regardless of font; and that action is not specific to LO, but does seem to tie nicely with the desktop-environment-level choice of keyboard layout. And as for fonts and font families - the dialog should allow the specification of a font-set, as discussed in bug 151215: A mapping from languages to fonts with fallbacks for languages not explicitly specified or when glyphs are missing etc. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 147680] Autotext replacement not willing to ignore space after shortcut
https://bugs.documentfoundation.org/show_bug.cgi?id=147680 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 155054] UI: Remediate frustration of unclear style names in style-name picklist contexts
https://bugs.documentfoundation.org/show_bug.cgi?id=155054 Heiko Tietze changed: What|Removed |Added Blocks|107833 |103427 --- Comment #4 from Heiko Tietze --- Some of the paragraph styles (PS) are used by internal functions such as "Content " for the Table of Contents (check the Styles tab), and some depend on the context, for example Caption > Text- you may want a different PS for frame captions vs. tables captions. The Stylist (this complex sidebar UI) has various filters to accommodate many different needs. The full list is not recommendable for novices; and while you like the tree it's not a simple UI. Some effort has been done to bring the best into the Automatic style (for example bug 69551). Please review bug 103427 for duplicates, there are many. I think your request is not actionable (we cannot submit a patch that resolves an issue) nor entirely justified. We can discuss some names, fiddle around with the organization but in the end it remains the same workflow. And the actual use case of "I struggle to pick the right PS for my task" requires to read the documentation. The second part of expanding a dropdown into a tree makes no sense to me. Trees are not recommended usability-wise (although expert user may love it), neither the styles dropdown nor the Notebookbar styles area list all PS but offer access to the Stylist. Lot of room for improvements here, see bug 90646, bug 93111, bug 143987, and bug 153581. Just to pick a few. My take here: WONTFIX (ticket has been tagged as needsUXEval so we seek for input from different people ideally and either agree and forward to developers or resolve WF/NAB; you can always reopen a ticket, I wont close it again). Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103427 [Bug 103427] [META] Styles and Formatting sidebar deck and floating window https://bugs.documentfoundation.org/show_bug.cgi?id=107833 [Bug 107833] [META] Writer paragraph style bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 154795] Font selection pane offers choice of "language" - which isn't.
https://bugs.documentfoundation.org/show_bug.cgi?id=154795 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEEDINFO -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 154795] Font selection pane offers choice of "language" - which isn't.
https://bugs.documentfoundation.org/show_bug.cgi?id=154795 --- Comment #3 from Heiko Tietze --- So you suggest to have a separate dropdown for Country in the font tab, probably one for all three groups? -- You are receiving this mail because: You are on the CC list for the bug.
