[Bug 159277] It would be nice to have an exclude file type option from Recent Files.
https://bugs.documentfoundation.org/show_bug.cgi?id=159277 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval |easyHack, needsDevAdvice Status|REOPENED|NEW CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||hoss...@libreoffice.org, ||mentoring@documentfoundatio ||n.org --- Comment #9 from Heiko Tietze --- We discussed the topic in the design meeting. While this could be a nice example for a macro because the use case is not so common, the majority agrees with the need and suggest to implement the filter. It would be a string in the expert options that allows to filter the MRU list. Could be an interesting easyhack. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159040] provide easy UI to automatically apply digital signature when storing documents
https://bugs.documentfoundation.org/show_bug.cgi?id=159040 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Keywords|needsUXEval | Status|UNCONFIRMED |NEW Blocks||105605 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #3 from Heiko Tietze --- We discussed the topic in the design meeting. The most easy solution might be to have a default signature defined in tools > options > security and just the option to apply in the save dialog; if another than the default signature is needed one would have to use file > digital signature as of today. To avoid too cluttering the save dialog with options we could move all into a dialog. Or "hide" all checkboxes behind an expander. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=105605 [Bug 105605] [META] Digital signatures bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159261] Use Noto family fonts as default fonts for documents, bundle as needed for l10n
https://bugs.documentfoundation.org/show_bug.cgi?id=159261 Heiko Tietze changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #7 from Heiko Tietze --- We discussed the topic in the design meeting. Fonts are a very subjective matter. Liberation is kind of a trademark, and Google artwork not an ideal open source solution. So we decided to keep the current default. Feel free to reopen if you have substantial backup for the idea. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158877] Non-corrective Autoformat settings can't just be placed under AutoCorrect
https://bugs.documentfoundation.org/show_bug.cgi?id=158877 Heiko Tietze changed: What|Removed |Added Resolution|--- |NOTABUG Status|UNCONFIRMED |RESOLVED --- Comment #2 from Heiko Tietze --- We discussed the topic in the design meeting. The term AutoCorrect uses camel case and might be not clear for some users. However, alternatives such as "Text Refinement" would not be familiar and detrimental to usability. We decided to keep the term therefore. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158876] Clarify Autocorrect options
https://bugs.documentfoundation.org/show_bug.cgi?id=158876 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Summary|Autocorrect options are |Clarify Autocorrect options |very confusing and | |difficult to use| --- Comment #6 from Heiko Tietze --- We discussed the topic in the design meeting. Separating the list is very subjective and one may have a concept of replacement vs. formatting while others would make a different distinction. Therefore this idea was rejected. Renaming some entries make sense, however, even when the (online) help is still needed. Before any patch could be done we need to complete the list of changes. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159432] Sort and/or filter Named Ranges And Expressions from Manager
https://bugs.documentfoundation.org/show_bug.cgi?id=159432 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval, topicUI| --- Comment #5 from Heiko Tietze --- So let's sort on click at the header and add a filter input box. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159432] Sort and/or filter Named Ranges And Expressions from Manager
https://bugs.documentfoundation.org/show_bug.cgi?id=159432 --- Comment #4 from Thomas Patrick Welborn --- Hey Heiko - Yes, that is what I was imagining: click on the column header to sort alphanumerically. I am not certain about the other thing you mentioned. More specifically what I imagined was some sort of text input field (I am only familiar with web user interface concepts) that filters listed Named Ranges according to input text matches. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159432] Sort and/or filter Named Ranges And Expressions from Manager
https://bugs.documentfoundation.org/show_bug.cgi?id=159432 --- Comment #3 from Thomas Patrick Welborn --- For the time being I am going to use the keyboard typing effect described by Stephanie to match long lists from the Named Ranges and Expressions Manager. I am not sure what the best design solution is, honestly. I have worked with the software for several hundred hours and it suits my purpose well, but I do not know what kind of limitations a software programmer has to implement features. Alternate to my filtering enhancement request, there could be some kind of group management feature where a tree structure could be created to manage many Named Ranges under. Maybe my actual enhancement request is a user interface feature to manage large or very large volume of Named Ranges. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158101] Disabled popup menu items are visible with non-gtk backend
https://bugs.documentfoundation.org/show_bug.cgi?id=158101 Stéphane Guillou (stragu) changed: What|Removed |Added CC||s...@onet.pl --- Comment #10 from Stéphane Guillou (stragu) --- *** Bug 159487 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158101] Disabled popup menu items are visible with non-gtk backend
https://bugs.documentfoundation.org/show_bug.cgi?id=158101 Rafael Lima changed: What|Removed |Added See Also|https://bugs.documentfounda |https://bugs.documentfounda |tion.org/show_bug.cgi?id=15 |tion.org/show_bug.cgi?id=15 |9486|9487 -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158101] Disabled popup menu items are visible with non-gtk backend
https://bugs.documentfoundation.org/show_bug.cgi?id=158101 Rafael Lima changed: What|Removed |Added Status|ASSIGNED|RESOLVED See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||9486 Resolution|--- |FIXED --- Comment #9 from Rafael Lima --- It's now OK with: Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 379968864c42f4bd99d874a4ce1949dd6eed45b8 CPU threads: 16; OS: Linux 6.5; UI render: default; VCL: kf5 (cairo+xcb) Locale: pt-BR (pt_BR.UTF-8); UI: en-US Calc: CL threaded This should be cherry-picked for 24.2. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158518] Allow user to specify any of three italic types (It, Em, Cite) in character styles; allow this to determine html code of created ebooks
https://bugs.documentfoundation.org/show_bug.cgi?id=158518 --- Comment #7 from V Stuart Foote --- (In reply to Heiko Tietze from comment #6) > (In reply to V Stuart Foote from comment #4) > > Rather, this was a request for expanding our "Emphasis" character style(s) > What hinders a user to create a new character style? Why should we ship more > default styles, given that users complain about too many items in the > Stylist (see bug 158791 for instance). A user defined CS could not support export filter needs. As Regina notes, requirement would need to be both the additional character styles but also adjustments to the export filters (EPub, HTML and probably PDF). Enhancing the export filters to support ebooks/EPub in general would need a well crafted set of pre-defined CS (italic, emphasis, citation of some markup) for the export filters to correctly parse. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158518] Allow user to specify any of three italic types (It, Em, Cite) in character styles; allow this to determine html code of created ebooks
https://bugs.documentfoundation.org/show_bug.cgi?id=158518 --- Comment #6 from Heiko Tietze --- (In reply to V Stuart Foote from comment #4) > Rather, this was a request for expanding our "Emphasis" character style(s) What hinders a user to create a new character style? Why should we ship more default styles, given that users complain about too many items in the Stylist (see bug 158791 for instance). -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158518] Allow user to specify any of three italic types (It, Em, Cite) in character styles; allow this to determine html code of created ebooks
https://bugs.documentfoundation.org/show_bug.cgi?id=158518 --- Comment #5 from Regina Henschel --- (In reply to V Stuart Foote from comment #4) > Not clear if there is native ODF support for the additional 'Italic', > 'Emphasis', or 'Citation' that ebook and html could consume. Export filters are not related to ODF. If an application uses a specific style to export a specific element/attribute in the target format, then this is entirely up to the application. The issue here is not only the definition of further styles, but in addition changes to the export filter. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158518] Allow user to specify any of three italic types (It, Em, Cite) in character styles; allow this to determine html code of created ebooks
https://bugs.documentfoundation.org/show_bug.cgi?id=158518 V Stuart Foote changed: What|Removed |Added CC||rb.hensc...@t-online.de Resolution|DUPLICATE |--- Status|RESOLVED|NEW --- Comment #4 from V Stuart Foote --- (In reply to Heiko Tietze from comment #2) > Doesn't it depend entirely on the font whether more than one italic form is > available, eg. oblique? Or do you have a slider control in mind that adjusts > the slantness? => NEEDINFO > > In any case you can define character styles with your choices. We predefine > "Emphasis" using just italic (and show this on the "Formatting (Styles)" > toolbar). And "Quotation" (not using the same attributes, indeed a bit odd. > > Bug 35538 requests a better handling of fonts with more than 4 styles and > bug 151322 is about to stop identifying italic with slanted/oblique. Maybe > we can make this ticket a duplicate of one. Back to NEW. Not a font issue at all. Rather, this was a request for expanding our "Emphasis" character style(s) to support additional named styles within the document--not the "slantness" of a particular font (either its foundry provided, or our VCL implementation). Not clear if there is native ODF support for the additional 'Italic', 'Emphasis', or 'Citation' that ebook and html could consume. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 155618] Allow resizing Writer tables by dragging while keeping proportions
https://bugs.documentfoundation.org/show_bug.cgi?id=155618 Buovjaga changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC|libreoffice-ux-advise@lists | |.freedesktop.org| Keywords|needsUXEval | Resolution|--- |DUPLICATE --- Comment #12 from Buovjaga --- Oh, looks like bug 61835 already asks for basically the same. Regina has a hint there: "Use Alt+Left/Right Arrow to change column width while keeping the width of the other columns. Of cause this can only work as long as the entire table width fits into the text area width." *** This bug has been marked as a duplicate of bug 61835 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 155618] Allow resizing Writer tables by dragging while keeping proportions
https://bugs.documentfoundation.org/show_bug.cgi?id=155618 Buovjaga changed: What|Removed |Added Keywords||needsUXEval Summary|table behaviour can't be|Allow resizing Writer |customized |tables by dragging while ||keeping proportions Severity|normal |enhancement CC||ilmari.lauhakangas@libreoff ||ice.org, ||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #11 from Buovjaga --- Writer doesn't have the ability to grab a table by its corner and resize the whole thing while keeping the proportions like Impress. You can tweak column widths proportionally via table properties and there is bug 114633 for improving the dialog. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158869] [UI] Normalize command string for Table Styles
https://bugs.documentfoundation.org/show_bug.cgi?id=158869 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |NOTABUG Blocks||101756, 115596 --- Comment #2 from Heiko Tietze --- No further input, I'd rather keep the different names. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=101756 [Bug 101756] [META] Table styles bugs and enhancements https://bugs.documentfoundation.org/show_bug.cgi?id=115596 [Bug 115596] [META] Labels of UNO commands bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158874] Want MS-Word like auto-formatting of beginning of list item
https://bugs.documentfoundation.org/show_bug.cgi?id=158874 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA --- Comment #11 from Heiko Tietze --- Feel free to reopen with the screencast. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158996] Floating table
https://bugs.documentfoundation.org/show_bug.cgi?id=158996 Heiko Tietze changed: What|Removed |Added Resolution|--- |DUPLICATE Status|NEEDINFO|RESOLVED --- Comment #3 from Heiko Tietze --- Missing feedback (and solution is given in comment 1). The duplicate ticket requests a different approach with "unified table management", which could be helpful in this case too. *** This bug has been marked as a duplicate of bug 113603 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158799] Editing. Have a cell background separate from the document background.
https://bugs.documentfoundation.org/show_bug.cgi?id=158799 Heiko Tietze changed: What|Removed |Added Resolution|--- |INSUFFICIENTDATA Status|NEEDINFO|RESOLVED --- Comment #9 from Heiko Tietze --- Missing feedback, I'll close the ticket for now. Feel free to reopen. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 130278] Line spacing "Fixed" not setable if the odt comes from doc
https://bugs.documentfoundation.org/show_bug.cgi?id=130278 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |INSUFFICIENTDATA --- Comment #9 from Heiko Tietze --- Closing the unclear issue for now. Feel free to reopen. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158518] Allow user to specify any of three italic types (It, Em, Cite) in character styles; allow this to determine html code of created ebooks
https://bugs.documentfoundation.org/show_bug.cgi?id=158518 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Heiko Tietze --- No further input, making it a duplicate. *** This bug has been marked as a duplicate of bug 151322 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158174] EDITING: AutoCorrect locale options should have an exception for single smart quotes to be substituted back to apostrophes when in the middle of a word
https://bugs.documentfoundation.org/show_bug.cgi?id=158174 Heiko Tietze changed: What|Removed |Added CC||nem...@numbertext.org --- Comment #5 from Heiko Tietze --- László, can you clarify what exactly is needed? -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 158127] INDEX should use en dash (not hyphen) for number ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=158127 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|NEW Keywords|needsUXEval |difficultyMedium, easyHack, ||skillCpp CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||mentoring@documentfoundatio ||n.org --- Comment #6 from Heiko Tietze --- No further input, let's implement. -- You are receiving this mail because: You are on the CC list for the bug.
[Bug 159406] Possibility to define Styles for lightmode or darkmode
https://bugs.documentfoundation.org/show_bug.cgi?id=159406 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |WONTFIX --- Comment #6 from Heiko Tietze --- So let's resolve this ticket as WF. Feel free to reopen. -- You are receiving this mail because: You are on the CC list for the bug.
