Created attachment 124695 [details] Comparison of lists for menu and style properties Compare the list of items: Format / Text / Change case and the list of drop-down items: Styles / Edit style / Font effects / Effects. I attached screenshot with both lists side-by-side opened in two Writer's instances. It is easy to see that some of items do not have counterparts. My guess it to have been overlooked (so I decided to file it as a bug). I wonder if the «Small capitals» item was not included in the list on the left intentionally though. Apart from that the same items have different names (and ordered differently) on the left and on the right. Would it be a good idea to use identical names as well as the same order of items? Best regards, Sergey Nemna
The drop-down list of font effects for character styles looks exactly the same as for paragraph styles.
They are not the same. The items in Format>Text>Change Case change the actual text, while "Font effects" only change the appearance, but the underlying text stays the same. Try both with Format>Clear Direct Formatting, or by copy-paste to another text editor.
The Paragraph and Character dialogs are different .UI constructs than the Format -> Text -> Change case menus (the dialogs evolved from older .src handling, the menus are more "dynamic"). They also assert differently on the selected text. Specific .uno commands must exist to implement a button action on the menus. Don't know if one has been created for "Small caps" effect. Not sure that adding the actions for sentence case and toggle case to either dialog makes sense--the Direct Formatting vs. Style context issues. However--the *labeling* probably should be consistent between menus and dialogs--and the correct linkages made for Pootle i10n needs. @UX thoughts on priority of adjusting this?
(In reply to V Stuart Foote from comment #3) > Don't know if one has been created for "Small caps" effect. Not that I'm aware of. It's requested in Bug 87914 and Bug 38604. > Not sure that adding the actions for sentence case and toggle case to either > dialog makes sense--the Direct Formatting vs. Style context issues. Not sure I understand. Sentence case and toggle case currently _change_ the actual text. They are not "effects" - unlike the items from the dialog. And if they were effects - they could be applied for both direct formatting and via styles. > However--the *labeling* probably should be consistent between menus and > dialogs I disagree. Same labeling would make users think that they do the same thing, while they don't. We can introduce _new_ command that correspond to the dialog items, and give them same labels as in the dialog. But _renaming_ the current items is a very bad idea IMHO.
(In reply to V Stuart Foote from comment #3) > Not sure that adding the actions for sentence case and toggle case to either > dialog makes sense--the Direct Formatting vs. Style context issues. If sentence case and toggle case are something supported in the ODF and OOXML formats and in other office suites, then it would be useful to have it as part of a character style. > However--the *labeling* probably should be consistent between menus and > dialogs--and the correct linkages made for Pootle i10n needs. I think we can use upper case, lower case, and title case in both places and change the 'Effects:' label in the dialog to 'Capitalization:' and 'Relief:' to 'Effects:'. (In reply to Maxim Monastirsky from comment #4) > I disagree. Same labeling would make users think that they do the same > thing, while they don't. We can introduce _new_ command that correspond to > the dialog items, and give them same labels as in the dialog. But _renaming_ > the current items is a very bad idea IMHO. We already have 'lowercase' in the menu and 'Lowercase' in the dialog, so 1 of the 3 is already the same and 'Capitalize Every Word' isnt a good label. I would assume that most users want the non-font effect version of these commands to actually modify the underlying text, so dont think dialog corresponding commands are needed.
My understanding is the same as Maxim's. IT doesn't make sense to compare the menu and the dialog. It are different things. For me, a WFM
There are some concerns to make the two lists more similar. Plus, setting a character style (e.g. upper case) cannot be overriden with the toggle case method. Putting all together it's a WF.