[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #24 from Heiko Tietze --- I can follow the argument that users might misunderstand Formatting Mark as "show the pilcrows". And the InDesign example is tempting: "Insert > White Space and Break Character". But still bike-shedding. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146261] Bookmark... dialog should hold its resize from defaults for current session
https://bugs.documentfoundation.org/show_bug.cgi?id=146261 --- Comment #6 from Heiko Tietze --- Restoring the dialog size is tricky, see also bug 123123 and bug 134640. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146576] Use clipboard content when inserting a hyperlink
https://bugs.documentfoundation.org/show_bug.cgi?id=146576 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Ever confirmed|0 |1 Summary|Hyperlink content from |Use clipboard content when |clipboard |inserting a hyperlink Status|UNCONFIRMED |NEW Blocks||112125 --- Comment #1 from Heiko Tietze --- Sounds like a good idea. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=112125 [Bug 112125] [META] Hyperlink dialog bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Make it easier to find Single, Double, etc. Page View in the View Menu, so it is easier to Hide Whitespace, and mark documents as edited when these h
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 Heiko Tietze changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #19 from Heiko Tietze --- Having the whitespace option persistent was requested in bug 142450 - and the patch is IMO ready for submission. Guess this will also resolve your problem. *** This bug has been marked as a duplicate of bug 142450 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Make it easier to find Single, Double, etc. Page View in the View Menu, so it is easier to Hide Whitespace, and mark documents as edited when these h
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #18 from Mike Kaganski --- (In reply to MarjaE from comment #17) > But LibreOffice already shows 3 View > Layout options in the corner. If I open a new document, and click one > layout, and then click another, and then click back, I don't see any > indication of the current View Layout. Why not show which one it is? Do you say that you do not see the current layout being shown in a different color in the status bar? The attachment 174749 from your bug 144075 shows the two-page layout in blue, while the two other options are in black. The current layout *is* highlighted. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146578] select colors from dynamic color scheme
https://bugs.documentfoundation.org/show_bug.cgi?id=146578 Heiko Tietze changed: What|Removed |Added Resolution|--- |WONTFIX Keywords||needsUXEval Blocks||107380 Status|UNCONFIRMED |RESOLVED --- Comment #2 from Heiko Tietze --- The Document Colors palette is supposed to do exactly this. See also bug 107380 for what is not working. It will not provide a wheel, however, or any other fancy picking interaction. My take: out of scope for an office application but maybe a nice to have extension. And we do have some fancy extensions at https://extensions.libreoffice.org/?Tags%5B%5D=51. Maybe the PaletteMaker is basically what you are interested in (likely with potential to enhance). Please reopen if I've mistaken your idea. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=107380 [Bug 107380] [META] Document colors palette issues -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146578] select colors from dynamic color scheme
https://bugs.documentfoundation.org/show_bug.cgi?id=146578 --- Comment #1 from andreas_k --- compare to other office suites, the dynamic color scheme give the user an very easy to use tool for non predefined looking styles. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146578] select colors from dynamic color scheme
https://bugs.documentfoundation.org/show_bug.cgi?id=146578 andreas_k changed: What|Removed |Added CC||kain...@gmail.com, ||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Make it easier to find Single, Double, etc. Page View in the View Menu, so it is easier to Hide Whitespace, and mark documents as edited when these h
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #17 from MarjaE --- > And maybe add a crystal ball to the program, to guess what should be > highlighted for another user who needs another item highlighted? Maybe "Highlight" is too strong a word. But LibreOffice already shows 3 View Layout options in the corner. If I open a new document, and click one layout, and then click another, and then click back, I don't see any indication of the current View Layout. Why not show which one it is? This would make it easier for users to figure out if they're in Single, Double, or Auto, and figure out whether LibreOffice has detected their choice. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146576] Hyperlink content from clipboard
https://bugs.documentfoundation.org/show_bug.cgi?id=146576 andreas_k changed: What|Removed |Added CC||kain...@gmail.com, ||libreoffice-ux-advise@lists ||.freedesktop.org -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Make it easier to find Single, Double, etc. Page View in the View Menu, so it is easier to Hide Whitespace, and mark documents as edited when these h
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #16 from Mike Kaganski --- (In reply to MarjaE from comment #11) > 2. I suggest ... renaming "Zoom..." to "Zoom and View Layout." Possibly that would make sense. > 3. I suggest adding the Show Whitespace option to that dialogue. I have no preference here. Heiko? > 4. I suggest highlighting the current View Layout in the lower right corner, > so people can see what layout they have, since depending on screen size and > zoom, there may not be any other indication. And maybe add a crystal ball to the program, to guess what should be highlighted for another user who needs another item highlighted? ;-) I strongly disagree, that we need to "highlight" UI elements (that BTW were put to *front*, available directly on the main window, instead of having user to look in some menu/dialog - so it *already* *is* highlighted), when someone had a feeling that they could find it easier if it was highlighted. Every user has own preference for "this could be highlighted" - so it would end up highlighting everything. > 5. I suggest adding the Show Whitespace option there. No. That is not a feature that most users need. It is explained in help, in guide, and is discoverable in the logical View menu. > 6. I don't know if this would cause anyone trouble, but I wonder if it would > help if unchecking Show Whitespace automatically chanced the View Layout to > Single. This is bug 98446. (In reply to MarjaE from comment #15) > When I change the settings, LibreOffice doesn't note that the document has > been edited. So it lacks an important clue that these are savable > document-by-document settings instead of LibreOffice preferences. Possibly; but OTOH, marking documents changed just because of changing its view is a bit too much. There's some balance here; I don't know if it would make more problems to most, than would solve problems to minority ... -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Make it easier to find Single, Double, etc. Page View in the View Menu, so it is easier to Hide Whitespace, and mark documents as edited when these h
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 MarjaE changed: What|Removed |Added Summary|(Enhancement) Add Single, |(Enhancement) Make it |Double, etc. Page View to |easier to find Single, |the View Menu, so it is |Double, etc. Page View in |easier to Hide Whitespace, |the View Menu, so it is |and stop automatically |easier to Hide Whitespace, |reverting documents to |and mark documents as |Auto. |edited when these have been ||changed. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace, and stop automatically reverting documents to Auto.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #15 from MarjaE --- When I change the settings, LibreOffice doesn't note that the document has been edited. So it lacks an important clue that these are savable document-by-document settings instead of LibreOffice preferences. I still think some or all of the interface changes in comment 11 would make it easier to find and apply these settings. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace, and stop automatically reverting documents to Auto.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #14 from Mike Kaganski --- (In reply to MarjaE from comment #11) > 1. I don't understand the logic of reverting Show Whitespace, View Layout, > and Zoom every time people open a file. I think a persistent user preference > would be appropriate. This is per-document setting. So when you create a document, and set it to two-page view, and save it, this document will open two-page next time, both for you, and for other people. But other documents, having a different layout setting, will use their own setting. Thus, if you had created lots of documents in two-page layout, all they will have that setting individually. When used *normally*, this feature allows you to have some documents in book view, some in single page view, and that would be defined by your preference for them. You may have different kinds of documents, with multiple page sizes, orientations, some for reading/reference, some for day-to-day editing ... and using same layout for all is not OK. But of course, if the feature was used incorrectly - e.g., when you've set it without clear understanding, then created tens of documents, and now want all of them to look single-page, you might feel like "give me an option to undo my previous mistake for all at once". Still, that is not a use case that needs such an option - it's a user mistake. Note also, that if you created a template with such a setting, new documents created from that template will all have that setting applied. Hope that helps. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace, and stop automatically reverting documents to Auto.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #13 from MarjaE --- As for the preferences interface, that's bug 144075. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace, and stop automatically reverting documents to Auto.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #12 from MarjaE --- (In reply to Mike Kaganski from comment #10) > (In reply to MarjaE from comment #9) > > It's hidden in a separate dialogue when I try that. > > You are telling puzzles. What's hidden where? The View Layout options are hidden in a separate dialogue in View > Zoom > Zoom... Why would a user expect to find them under Zoom, or under Zoom > Zoom...? > > > It keeps reverting. > > What keeps reverting, and at which moment? Each time I open the document, I find that all these settings have reverted. > > > So I have to go into this hidden dialogue every time I open every Writer > > document. > > This seems to confirm my idea that "it reverts" for other documents. > > > If there is an option under Preferences, I can't find it, because I can't > > enlarge the "perfectly readable" text in that interface to read it. > > Which option you are talking about? We already discussed the option in the > View menu. And what "I can't find it, because I can't enlarge the "perfectly > readable" text in that interface to read it" might mean? An option to set the View Layout, instead of having it always revert to Auto, and to turn off Show Whitespace, instead of havuing it always revert to on. > > Generally, you seem to fight with the interface, and try to find answers > here; but this is not a user support resource - this is a bug tracking site, > where issues need to be described clearly, with steps to reproduce, > screenshots, problematic documents, etc. - not to help user to workaround or > to learn, but to reproduce the issue, confirm it, and then hopefully fix. And this interface is a bug. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace, and stop automatically reverting documents to Auto.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #11 from MarjaE --- 1. I don't understand the logic of reverting Show Whitespace, View Layout, and Zoom every time people open a file. I think a persistent user preference would be appropriate. 2. I suggest either adding all the options to the View menu itself, or renaming "Zoom..." to "Zoom and View Layout." 3. I suggest adding the Show Whitespace option to that dialogue. 4. I suggest highlighting the current View Layout in the lower right corner, so people can see what layout they have, since depending on screen size and zoom, there may not be any other indication. 5. I suggest adding the Show Whitespace option there. 6. I don't know if this would cause anyone trouble, but I wonder if it would help if unchecking Show Whitespace automatically chanced the View Layout to Single. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace, and stop automatically reverting documents to Auto.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #10 from Mike Kaganski --- (In reply to MarjaE from comment #9) > It's hidden in a separate dialogue when I try that. You are telling puzzles. What's hidden where? Indeed, the menu 'View->Zoom->Zoom...' opens a dialog, as indicated in comment 8. Are you talking about that? > It keeps reverting. What keeps reverting, and at which moment? When you set the setting, and press OK? Or when you close a document and open another? (Which would be OK, since this option is saved per document, and when you have that setting already saved in a document to multi-page view, it must open that way.) > So I have to go into this hidden dialogue every time I open every Writer > document. This seems to confirm my idea that "it reverts" for other documents. > If there is an option under Preferences, I can't find it, because I can't > enlarge the "perfectly readable" text in that interface to read it. Which option you are talking about? We already discussed the option in the View menu. And what "I can't find it, because I can't enlarge the "perfectly readable" text in that interface to read it" might mean? Generally, you seem to fight with the interface, and try to find answers here; but this is not a user support resource - this is a bug tracking site, where issues need to be described clearly, with steps to reproduce, screenshots, problematic documents, etc. - not to help user to workaround or to learn, but to reproduce the issue, confirm it, and then hopefully fix. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 V Stuart Foote changed: What|Removed |Added Status|NEW |UNCONFIRMED Ever confirmed|1 |0 --- Comment #23 from V Stuart Foote --- -1, on both changes (the Insert -> "Special Character..." dialog, or the list of Insert -> Formatting Mark) they are self-documenting and self explanatory. No real advantage to changing our legacy labeling/naming of the UI elements. And as to the "Symbols..." dialog in the sm module of comment 9--that is a completely different implementation that has no relevance to the "Special Character..." dialog. Nor could the dialog be linked for use in sm without major refactoring--its off topic. Back to Unconfirmed as there is NO consensus this change is needed, nor UX movement in that direction. Frankly this is 'bikeshedding'--I won't close it Won't Fix, but that is my suggestion for any UX action. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace, and stop automatically reverting documents to Auto.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 MarjaE changed: What|Removed |Added Summary|(Enhancement) Add Single, |(Enhancement) Add Single, |Double, etc. Page View to |Double, etc. Page View to |the View Menu, so it is |the View Menu, so it is |easier to Hide Whitespace. |easier to Hide Whitespace, ||and stop automatically ||reverting documents to ||Auto. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #9 from MarjaE --- It's hidden in a separate dialogue when I try that. It keeps reverting. So I have to go into this hidden dialogue every time I open every Writer document. If there is an option under Preferences, I can't find it, because I can't enlarge the "perfectly readable" text in that interface to read it. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #22 from jsv --- (In reply to Dave Barton from comment #20) > proceeded to attack, abuse, insult and make meaningless > infantile derogatory "cats dogs" commentary about the > view/opinion of another Bugzilla reporter. my God... i'm from Russia. is it OK that you, brave western guys who conquested the world, are so snowflakes now? is it OK for **YOU** ? this is just disgusting. Dave, you are not a man. You are a 12-years old girl. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #8 from Mike Kaganski --- (In reply to MarjaE from comment #7) > I suggest adding Single, Double, etc. Page View to the View Menu. It's already there: View->Zoom->Zoom...; the dialog has the View Layout section with the Single Page radio button. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 MarjaE changed: What|Removed |Added Ever confirmed|1 |0 Status|NEEDINFO|UNCONFIRMED -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Add Single, Double, etc. Page View to the View Menu, so it is easier to Hide Whitespace.
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 MarjaE changed: What|Removed |Added Summary|(Enhancement) Either add a |(Enhancement) Add Single, |Continuous View or add a|Double, etc. Page View to |working Show/Hide |the View Menu, so it is |Whitespace |easier to Hide Whitespace. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Either add a Continuous View or add a working Show/Hide Whitespace
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 --- Comment #7 from MarjaE --- Single-Page View is hidden in the lower right corner and sometimes seems unresponsible. I had to select it 4 times before I could get LibreOffice to hide the whitespace. I don't see any other changes because I don't have the space. Although 22" looks and feels giant to me-- I can't focus on more than a small part of the monitor at a time. I suggest adding Single, Double, etc. Page View to the View Menu. Possibly listing Single Page Without Whitespace, to replace Hide Whitespace. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #21 from jsv --- to summarize: * calling a menu item that is used to insert characters such as em dash or non-breaking space "Formatting marks" is wrong and confusing, and since this affect writing documentation, this does matter * calling a menu item that is used to get access to all of the character of the font "Special characters" is wrong and confusing, and since this affect writing documentation, this does matter * using argumentation "you are the first and probably the last user who have problems with it" is either naive or manipulative, and it can be proven in many ways, e.g. comparing with other software (german Papyrus Author, if you don't like InDesign) or by talking with "casual", that is, not biased, users. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #20 from Dave Barton --- (In reply to Thomas Lendo from comment #19) > Please, calm down all. jsv made a valid suggestion to improve the software > for all users in his view. Thomas, it is NOT a case of "calming down". Agreed, (Anonymous NON-CONTRIBUTING jsv) ORIGINALLY expressed a view/opinion about a subject and as someone involved with this project for over a decade, I respect that everyone is entitled to that, but (Anonymous NON-CONTRIBUTING jsv) then proceeded to attack, abuse, insult and make meaningless infantile derogatory "cats dogs" commentary about the view/opinion of another Bugzilla reporter. THIS IS NOT THE WAY THAT TDF & LibreOffice MEMBERS TREAT EACH OTHER. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146261] Bookmark... dialog should hold its resize from defaults for current session
https://bugs.documentfoundation.org/show_bug.cgi?id=146261 Thomas Lendo changed: What|Removed |Added CC||thomas.le...@gmail.com Blocks||102019 --- Comment #5 from Thomas Lendo --- I support the request to remember the dialog size during a session. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=102019 [Bug 102019] [META] Dialog bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 Thomas Lendo changed: What|Removed |Added Blocks||85811 CC||thomas.le...@gmail.com --- Comment #19 from Thomas Lendo --- Please, calm down all. jsv made a valid suggestion to improve the software for all users in his view. I support a change if it's "viewed holistically" for all parts of the program and all strings in menus, options, help, etc. Personally I've no idea what's a better wording. Also keeping the status would okay for me. 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 on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146369] An extra word in the tooltip when hovering over a footnote
https://bugs.documentfoundation.org/show_bug.cgi?id=146369 Thomas Lendo changed: What|Removed |Added CC||thomas.le...@gmail.com Blocks||103164 --- Comment #6 from Thomas Lendo --- I prefer the annotation as it is now in LibreOffice. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=103164 [Bug 103164] [META] Footnote and Endnote bugs and enhancements -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #18 from Dave Barton --- (In reply to jsv from comment #17) > To Dave: > > You just one person who advoactes for calling a cat as "dog" and a dog as > "cat". > > Just because "nobody strugged before". > > OK, I don't want to waste my time arguing with people who have no > understanding how the professional should look. To (Anonymous jsv) This is NOT an open forum for NON-CONTRIBUTORS like you, to jump in insult and attack the views and opinions of project members who have contributed to this project and it's predecessors for 20+ years. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #17 from jsv --- > MS Word, in recent versions, actually does something similar > to what jsv proposes: ... Thanks, Jan. -- To Sophie: This doesn't make a difference whether we talk about an office suite or desktop publishing software in this particular case. What I mean is that Adobe (and even better example is Apple) pay a lot of attention to thing like design, naming, wording, typography and so on. -- Actually, unless I started to write my own LO documentation, I never have problems with the current naming. But once you will start to write such documentation, you will soon discover that referring to things like "non breaking spaces" as formatting marks is confusing, especiallyn when the same name is used for "virtual" things such as blue paragraph marks. -- To Dave: You just one person who advoactes for calling a cat as "dog" and a dog as "cat". Just because "nobody strugged before". OK, I don't want to waste my time arguing with people who have no understanding how the professional should look. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #16 from Dave Barton --- This was the terminology used by StarOffice and subsequently in OpenOffice and now LibreOffice. With millions of users over more than 20 years the is the first and only known report of our users being "confused" by this. My take is NOT A BUG. Please let's stop "Bike-shedding", playing with semantics and concentrate on REAL issues. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #15 from jan d --- The question of what other software is doing makes sense in case we know that there is a problem and a change is needed. People come to new software with existing experiences and it makes sense to see what they might be familiar with and thus what is intuitive to them (https://www.asktog.com/papers/raskinintuit.html). I agree that the current lables might not be ideal. Aside of the suggested design tools, MS Word, in recent versions, actually does something similar to what jsv proposes: Insert-Ribbon → Symbols → [Window with two tabs:]"Symbols" (big table of characters), "Special Characters" (typographical and control characters like non-breaking space, en-dash, em-dash, ellipsis and writing-direction overwrite) However, it still is something that I would not change without some test or other data, and if we can’t research is further, leave as it it. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #14 from jan d --- Without having a clear case where users are irritated by the current labels, I would stick with what we have. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #13 from sophie --- (In reply to jsv from comment #11) > > I've never met a user confused by those strings too. I don't see any > > benefit of renaming them. > > These strings are simply wrong, and this is, in fact, plain obvious. > > It seems these names are "inherited" from MS Word, but this doesn't make > them correct. they were already there in StarOffice, we usually don't care what proprietary software are doing. >Neither InDesign nor Affinity Publisher follow this naming. > > See the InDesign UI screenshot which I have just added. These are specific tools dedicated to design or PAO, not an office suite. I still don't see why we should ask l10n, documentation teams and our users to change when they don't see a need to, that will only confuse them. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #12 from jsv --- Created attachment 177308 --> https://bugs.documentfoundation.org/attachment.cgi?id=177308=edit indesign -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 --- Comment #11 from jsv --- > I've never met a user confused by those strings too. I don't see any benefit > of renaming them. These strings are simply wrong, and this is, in fact, plain obvious. It seems these names are "inherited" from MS Word, but this doesn't make them correct. Neither InDesign nor Affinity Publisher follow this naming. See the InDesign UI screenshot which I have just added. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146493] "Insert > Special Character" and "Insert > Formatting Mark" should be renamed
https://bugs.documentfoundation.org/show_bug.cgi?id=146493 sophie changed: What|Removed |Added CC||so...@libreoffice.org --- Comment #10 from sophie --- (In reply to Heiko Tietze from comment #8) > IMO this is a lot for sake of renaming itself, haven't met a user who > actually struggles with the terms. But if we change the non-breakable > formatting marks into special character this will bring a lot confusion for > users who are familiar with the terms. > > But what term suits better should be decided primarily by the native > speakers. I second your comment, I've never met a user confused by those strings too. I don't see any benefit of renaming them. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146369] An extra word in the tooltip when hovering over a footnote
https://bugs.documentfoundation.org/show_bug.cgi?id=146369 Heiko Tietze changed: What|Removed |Added Status|NEEDINFO|UNCONFIRMED Ever confirmed|1 |0 CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #5 from Heiko Tietze --- The footnotes are not necessarily latin numbers and endnote roman numbers. You can show both in cyrillic lowe case letters, for example (Tools > Foot/Endnotes...). So the question is whether our users want to know what type of annotation it is or just the reference text. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146380] (Enhancement) Either add a Continuous View or add a working Show/Hide Whitespace
https://bugs.documentfoundation.org/show_bug.cgi?id=146380 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 CC||libreoffice-ux-advise@lists ||.freedesktop.org --- Comment #6 from Heiko Tietze --- Web View is supposed to show HTML content. We have plenty of features to adjust the UI: different types of UI, the mentioned continuous reading mode, the full screen mode... In the end, 22" is not giant. DIN A4 comes with 21 x 29.7 cm and you need this space for 100% (plus some pixels for the UI). The 22" are 17.6 x 13.6 in case of 4:3 or 19.2 x 10.8 for 16:9. Besides I struggle a bit with the actual request and the use case. If you want to get rid of the whitespace all tips have been given. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146356] ODT: No easy way to create an empty paragraph before Table of Content if document starts with table of content
https://bugs.documentfoundation.org/show_bug.cgi?id=146356 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org --- Comment #5 from Heiko Tietze --- Don't see how we can improve this. Users just have to learn Alt+Enter. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146033] Output to HTML: Field shadings shouldn't be part of Html-export
https://bugs.documentfoundation.org/show_bug.cgi?id=146033 --- Comment #6 from Heiko Tietze --- Created attachment 177304 --> https://bugs.documentfoundation.org/attachment.cgi?id=177304=edit Screenshot Apparently we show/hide the shading individually. Me uses the Formatted Dummy Text extension for testing [1] and single/multi-character bookmarks are hidden but not the hiding bookmark (...behind [him].) All other (easy to observe) fields have a clear background too. [1] https://extensions.libreoffice.org/en/extensions/show/132 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146356] ODT: No easy way to create an empty paragraph before Table of Content if document starts with table of content
https://bugs.documentfoundation.org/show_bug.cgi?id=146356 Telesto changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WONTFIX |--- Ever confirmed|1 |0 --- Comment #4 from Telesto --- (In reply to Heiko Tietze from comment #3) > Same for tables, enter goes into the first cell and you have to press > alt+enter to add a paragraph before. This is clearly a WF. > > With the ongoing work for bug 130318 the (missing) use case will be solved > too. I read comment 2 as going into different direction, suggesting it's a bug? And there is still the discrepancy with LibO behavior for DOCX where enter does work (and shouldn't if ALT+ENTER should be the only way) -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 144195] UI: PNG export dialog has radio button doesn't allow 'dimensions' or 'DPI' to be set both
https://bugs.documentfoundation.org/show_bug.cgi?id=144195 Heiko Tietze changed: What|Removed |Added CC||steven.missh...@gmail.com --- Comment #14 from Heiko Tietze --- *** Bug 146552 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146552] DRAW: Export Functionality (deprecated efficiency)
https://bugs.documentfoundation.org/show_bug.cgi?id=146552 Heiko Tietze changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #3 from Heiko Tietze --- Good point, let's discuss on bug 144195. *** This bug has been marked as a duplicate of bug 144195 *** -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146552] DRAW: Export Functionality (deprecated efficiency)
https://bugs.documentfoundation.org/show_bug.cgi?id=146552 --- Comment #2 from Telesto --- (In reply to Heiko Tietze from comment #1) Well I agree with initial poster (comment 0). The current design not being 'it'. Not saying the old design being OK either. See bug 144195 (with number of off-topic comments), and especially comment bug 144195 comment 10 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146356] ODT: No easy way to create an empty paragraph before Table of Content if document starts with table of content
https://bugs.documentfoundation.org/show_bug.cgi?id=146356 Heiko Tietze changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WONTFIX See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=13 ||0318 CC||andreas.heini...@yahoo.de --- Comment #3 from Heiko Tietze --- Same for tables, enter goes into the first cell and you have to press alt+enter to add a paragraph before. This is clearly a WF. With the ongoing work for bug 130318 the (missing) use case will be solved too. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146092] Make inserted frames rotatable
https://bugs.documentfoundation.org/show_bug.cgi?id=146092 Heiko Tietze changed: What|Removed |Added Ever confirmed|0 |1 Keywords|needsUXEval | CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||lukebe...@hotmail.com, ||rb.hensc...@t-online.de, ||vmik...@collabora.com Status|UNCONFIRMED |NEW --- Comment #1 from Heiko Tietze --- Reading Regina's bug 91530 comment 9 it seems possible. But OTOH Luke's c12 in the same bug states that rotation cannot applies to frames. Now I wonder if rotation is possible with ODF. Rotating an image means to enlarge the surrounding frame to the size of the diagonals of the content. Doing the same for text with all formatting could be difficult. To support the request: Since we want to foster the use of (interactive) frames over text boxes (see bug 139606) the missing rotation might be a regression for some users. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146097] RED CROSS -- search toolbar close button's RED color is ambiguous
https://bugs.documentfoundation.org/show_bug.cgi?id=146097 Heiko Tietze changed: What|Removed |Added CC||kain...@gmail.com, ||riz...@libreoffice.org --- Comment #3 from Heiko Tietze --- All shipped icon themes except Sifr show a red cross, and except Sukapura with a red background. Searching the Internet for images with symbol size using the term "close" returns more or less the same: red crosses. Rizal, Andreas: What do you think? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 105985] Make Template Manager's directory scanning smarter
https://bugs.documentfoundation.org/show_bug.cgi?id=105985 Heiko Tietze changed: What|Removed |Added Keywords|needsUXEval |needsDevEval CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org, ||mikekagan...@hotmail.com --- Comment #10 from Heiko Tietze --- (In reply to Buovjaga from comment #8) > Let's actually ask the UX design team what they think of these ideas. The implementation has been improved recently for bug 131850 by removing the encryption check. Yet there are still some more or less corner cases left: files on a slow network storage, access via slow connections, unexpected number of files etc. The correct solution is to separate the loading of files (actually thumbnails) from the interaction, which requires to be done in an extra thread. And not knowing what files exists on the target must not block the interaction too. Could be an interesting GSoC project. Reading templates from the program directory makes not much sense. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 140820] Should there be a "Default Frame Style", which each builtin Frame Style "Inherits from"?
https://bugs.documentfoundation.org/show_bug.cgi?id=140820 Heiko Tietze changed: What|Removed |Added Resolution|--- |WONTFIX Status|UNCONFIRMED |RESOLVED --- Comment #19 from Heiko Tietze --- (In reply to sdc.blanco from comment #18) > Is there a better generic name that could be used to describe the different > kinds in the current "Frame Styles" list? A frame is a frame, and renaming would make everything rather worse. Looking at your original intention I think we should resolve this ticket as WF. Having hierarchical relations has some bugs, there is no Default nor it should be, and frames have no "None" in terms of "take attributes from parent" option like CS. (In reply to Regina Henschel from comment #2) > I would not touch inheritance until at least the anchor problem is solved. (In reply to Mike Kaganski from comment #6) > (No) "fake default" behavior (like at CS) (In reply to Mike Kaganski from comment #16) > "Default" styles in other places are created specifically to be > roots of (possibly large) hierarchies. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146386] Drop support for FTP
https://bugs.documentfoundation.org/show_bug.cgi?id=146386 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |caol...@redhat.com, |.freedesktop.org|heiko.tietze@documentfounda ||tion.org Keywords|needsUXEval |security --- Comment #2 from Heiko Tietze --- Caolan, what's your take on this? -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 137269] Table of Contents dialog is too large
https://bugs.documentfoundation.org/show_bug.cgi?id=137269 Heiko Tietze changed: What|Removed |Added CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda |.freedesktop.org|tion.org Keywords|needsUXEval | --- Comment #21 from Heiko Tietze --- (In reply to Dieter from comment #18) > Index dialog has been moved to the right... Don't get this. You mean the dialog's position on the parent? Would be a different topic. The issue here is the oversized ToC dialog likely caused by the area style tab. And the proposed solution is to access these options in an extra dialog. I suggest a button "Background" at the Styles tab. -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 144195] UI: PNG export dialog has radio button doesn't allow 'dimensions' or 'DPI' to be set both
https://bugs.documentfoundation.org/show_bug.cgi?id=144195 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||6552 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146552] DRAW: Export Functionality (deprecated efficiency)
https://bugs.documentfoundation.org/show_bug.cgi?id=146552 Telesto changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=14 ||4195 -- You are receiving this mail because: You are on the CC list for the bug.
[Libreoffice-ux-advise] [Bug 146552] DRAW: Export Functionality (deprecated efficiency)
https://bugs.documentfoundation.org/show_bug.cgi?id=146552 Heiko Tietze changed: What|Removed |Added Blocks||116082, 109323 Component|Draw|UI See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||5464 OS|Windows (All) |All --- Comment #1 from Heiko Tietze --- Please read comments at bug 115464 and see also for the reason to this change. (In reply to steven.misshula from comment #0) > 1) The TAB feature skips over the radial button True > 2) The Dimension or Resolution change is obfuscated to the user Not true. Or rather not done at 100%. In fact the controls become disabled depending on what radio button is checked. And to make it perfectly clear we should also disable the unit dropdown. > 3) An extra step has been added to export when choosing to control > Resolution AND Dimension. By design, see bug 115464 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=109323 [Bug 109323] [META] Graphic export bugs and enhancements (jpg, png, eps, tiff, gif ...) https://bugs.documentfoundation.org/show_bug.cgi?id=116082 [Bug 116082] [META] Image issues related to image DPI -- You are receiving this mail because: You are on the CC list for the bug.
