https://issues.apache.org/ooo/show_bug.cgi?id=125985
--- Comment #30 from Aivaras Stepukonis <astepuko...@apache.org> --- (In reply to jolatt from comment #29) (In reply to Keith N. McKenna from comment #28) > > > The only change I see that is needed here is in the description on the > toolbar button. The button that says insert footnote/endnot directly should > be changed to insert footnote directly as this is what the button does. > There is already a button to insert endnote directly. The use of the word > directly is correct English in that those buttons by-pass the insert dialog > thereby inserting the footnote or end note directly into the document. It is correct, yet redundant and as such out of place. The description of a toolbar icon should be treated as a case of contextual classification, not of the general taxonomy of the software (as, say, in a conceptually laid out manual). Let visit the local groceries shop and look at the department names: Bread | Dairy | Meat | Beverages | Candy All good. But what if one finds: Bread | Dairy | Pork | Beverages | Candy Wrong classification! A particular type of meat is juxtaposed to more general types of food. Same goes for describing as "Insert Footnote Directly" (pork) what should simply be "Insert Footnote" (meat). Let us mind the context - it is a description of an icon side-by-side with other icons, in a toolbar side-by-side with other toolbars: ...New | Open | Page Preview | Bold | Italics | Gallery | Special Character... It is not the right place to distinguish between different types of inserting footnotes (they're not even being juxtaposed here as options) because one is distinguishing here between different types of tools (printing vs opening, previewing vs navigating and so on). So a better idea in this particular case to just say "meat" instead of specifying it's "pork" (even if that meat is in fact pork). That is to say, "Insert Footnote" is more adequate to the immediate context of the icon than "Insert Footnote Directly." -- You are receiving this mail because: You are the assignee for the issue. You are watching all issue changes.
