[Libreoffice-ux-advise] [Bug 153259] Enhancement Request: Exclude some pages from field "Page Count"

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153259

Heiko Tietze  changed:

   What|Removed |Added

 CC|heiko.tietze@documentfounda |libreoffice-ux-advise@lists
   |tion.org|.freedesktop.org
   Keywords||needsUXEval

--- Comment #6 from Heiko Tietze  ---
(In reply to ajlittoz from comment #5)
> Consequently we could have a new setting in the
> manual page break dialog to restart page count.

My approach was to exclude page styles from the total count (and ditch the
request in bug 71583). Restarting the count makes it somewhat inconsistent and
error-prone thinking of moving a page around. But nevertheless worth to
discuss, back to UX.

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

[Libreoffice-ux-advise] [Bug 92056] underline dropdown

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92056

V Stuart Foote  changed:

   What|Removed |Added

 Resolution|WORKSFORME  |FIXED
 CC||vsfo...@libreoffice.org

--- Comment #17 from V Stuart Foote  ---
Actually think we can call this FIXED

https://gerrit.libreoffice.org/c/core/+/24491/ by Szymon Kłos

Additional work for bug 153299 would provide Strikethrough. With some UX
decision for doing similar for Overline, or not.

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

[Libreoffice-ux-advise] [Bug 92056] underline dropdown

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92056

Heiko Tietze  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=15
   ||3299
 Resolution|--- |WORKSFORME

--- Comment #16 from Heiko Tietze  ---
Rather WFM since we do have uno:Underline with the various options of line
styles everywhere (which seems not have been in the past). And the
strike-through feature is handled in bug 153299.

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

[Libreoffice-ux-advise] [Bug 153300] Format->Text menu name is confusing in Calc

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153300

--- Comment #4 from Mike Kaganski  ---
(In reply to Heiko Tietze from comment #3)

IMO, if this would be renamed, it should be renamed synchronously everywhere.

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

[Libreoffice-ux-advise] [Bug 153300] Format->Text menu name is confusing in Calc

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153300

--- Comment #3 from Heiko Tietze  ---
Created attachment 185044
  --> https://bugs.documentfoundation.org/attachment.cgi?id=185044=edit
Screenshot

Screenshot for the lazy people. 

Although renaming Text to Character sounds good, the label aligns currently
with Writer and Draw/Impress. And actually I wonder how changing the font
weight to italic, for example, could be mistaken as formatting as text.

In other words: does the (little) improvement of understanding the
functionality outbalance the drawback of diverging labels?

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

[Libreoffice-ux-advise] [Bug 153300] Format->Text menu name is confusing in Calc

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153300

--- Comment #2 from Mike Kaganski  ---
(In reply to Stéphane Guillou (stragu) from comment #1)
> Should it use the term "Font", as that's what's used in the Format >
> Character tabs "Font" and "Font effects", where all the corresponding
> commands are?

Note that not everything there is from "Font" (as noted in bug 152197).

Another option: "Characters"?

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

[Libreoffice-ux-advise] [Bug 153259] Enhancement Request: Exclude some pages from field "Page Count"

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153259

Heiko Tietze  changed:

   What|Removed |Added

   See Also||https://bugs.documentfounda
   ||tion.org/show_bug.cgi?id=99
   ||189
 Status|UNCONFIRMED |NEW
   Keywords|needsUXEval |
 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org,
   ||rb.hensc...@t-online.de
   Severity|normal  |enhancement
 Ever confirmed|0   |1

--- Comment #3 from Heiko Tietze  ---
Clearly a desired feature. MSO allows to manipulate field variables via "Insert
field characters" (Ctrl+F9) and "{ = {NUMPAGES} - 1 }". Quite tedious too. And
saving this as ODF document breaks the formula.

Besides introducing a standard approach to not count pages with a certain
style, I wonder if we should also consider bug 71583 "There is no page count
field for different page styles or sections", which requests "page 1 of 10" for
one part of the document and another "page 1 of 10" for a different part.

A duplicate resp. different use case is bug 149981 "Footer Page numbers with
endnotes". Usually we make the newer ticket a duplicate of the older but in
this case I'd prefer the more generic description.

And we have a kind of see also bug 99189 "Add option to exclude footnotes,
endnotes and textboxes and inline citations from word count".

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

[Libreoffice-ux-advise] [Bug 153300] Format->Text menu name is confusing in Calc

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153300

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 Blocks||85811
 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org
Version|unspecified |6.0.0.3 release

--- Comment #1 from Stéphane Guillou (stragu) 
 ---
Adding libreoffice-ux-advise@lists.freedesktop.org to CC to make sure it
reaches them.

Should it use the term "Font", as that's what's used in the Format > Character
tabs "Font" and "Font effects", where all the corresponding commands are?


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 92056] underline dropdown

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=92056

Stéphane Guillou (stragu)  changed:

   What|Removed |Added

 CC||libreoffice-ux-advise@lists
   ||.freedesktop.org,
   ||stephane.guillou@libreoffic
   ||e.org
   Keywords|needsDevEval|needsUXEval

--- Comment #15 from Stéphane Guillou (stragu) 
 ---
UX, please advise if this should be closed.
We have a split button for underline, a strikethrough button in the sidebar for
all components, and proposal to have a split strikethrough button in bug
153299.

IMHO, main inconsistency is underline but no strikethrough in the Calc toolbar,
but comments seem to indicate we don't seek consistency here because
strikethrough is more useful to Writer.
Won't fix?

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

[Libreoffice-ux-advise] [Bug 153299] Add drop-down menu to "Strikethrough" options

2023-02-01 Thread bugzilla-daemon
https://bugs.documentfoundation.org/show_bug.cgi?id=153299

Heiko Tietze  changed:

   What|Removed |Added

   Keywords|needsUXEval |easyHack
 CC|libreoffice-ux-advise@lists |heiko.tietze@documentfounda
   |.freedesktop.org|tion.org,
   ||hoss...@libreoffice.org,
   ||mentoring@documentfoundatio
   ||n.org
 Blocks||86899, 105752

--- Comment #3 from Heiko Tietze  ---
I think it's not a big deal to enhance the simple strikethrough to allow other
line styles than single lines. Could be an interesting easy hack. Hossein, what
do you think?


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=86899
[Bug 86899] [META] Requests for the addition of UNO commands
https://bugs.documentfoundation.org/show_bug.cgi?id=105752
[Bug 105752] [META] Line content panel of the Properties deck/tab of the
sidebar
-- 
You are receiving this mail because:
You are on the CC list for the bug.