A quick look in the customization tool confirms that a few commands have been added with a missing capitalization title. I haven't found any guide about the writing style used in the LibreOffice suite; I therefore applied some kind of consistency. I also want to make it clear that there is no good or bad style guide, but it's important for the team in charge of the design or the UI to define rules (which preposition should be capitalized, how to capitalize when a noun or an adjectif is hyphenated, etc.). I look forward to your feedback, thank you! Apply document classification ➔ Apply Document Classification Cross-reference ➔ Cross-Reference Delete index ➔ Delete Index Edit index ➔ Edit Index Half-width ➔ Half-Width Full-width ➔ Full-Width Go to next faulty table ➔ Go to Next Faulty Table Go to next table formula ➔ Go to Next Table Formula Go to previous table formula ➔ Go to Previous Table Formula Insert Narrow No-break Space ➔ Insert Narrow No-Break Space Insert non-breaking hyphen ➔ Insert Non-Breaking Hyphen Insert non-breaking space ➔ Insert Non-Breaking Space Insert soft hyphen ➔ Insert Soft Hyphen Insert single-column frame manually ➔ Insert Single-Column Frame Manually Jump To Specific Page ➔ Jump to Specific Page Left-To-Right ➔ Left-to-Right Left-to-right Mark ➔ Left-to-Right Mark Right-To-Left ➔ Right-to-left Right-to-left Mark ➔ Right-to-Left Mark Text direction from left to right ➔ Text Direction from Left to Right Text direction from top to bottom ➔ Text Direction from Top to Bottom Anchor To Frame ➔ Anchor to Frame Anchor To Page ➔ Anchor to Page Anchor To Paragraph ➔ Anchor to Paragraph Demote One Level With Subpoint ➔ Demote One Level with Subpoint Promote One Level With Subpoint ➔ Promote One Level with Subpoint lowercase ➔ Lowercase Small capitals ➔ Small Capitals No-width Optional Break ➔ No-Width Optional Break Refresh document layout ➔ Refresh Document Layout Show outline-folding buttons ➔ Show Outline-Folding Buttons Show resolved comments ➔ Show Resolved Comments Show tracked selection in margin ➔ Show Tracked Selection in Margin Text from file ➔ Text from File Use header/footer menu ➔ Use Header/Footer Menu Data source as Table ➔ Data Source as Table Area Style / Filling ➔ Area Style/Filing
"Lowercase" should stay "lowercase" as "Uppercase" command is written "UPPERCASE", and "Toggle Case" is written "tOGGLE cAse". Although I don't really like it when the writing is supposed to illustrate a function.
UX-team, we need your opinion -1 from me, btw
In our style of Title Capitalization, we do not capitalize the second element of hyphenated terms. The rest should; please provide a patch.
(In reply to Adolfo Jayme from comment #3) > In our style of Title Capitalization, we do not capitalize the second > element of hyphenated terms. The rest should; please provide a patch. First, thank you for your answer. This removes some elements but adds others: Drop-Down Form Field ➔ Drop-down Form Field Form-Base Filters ➔ Form-base Filters Sorry, I'm not qualified-enough to write a patch and I have concern about adding more bugs by doing so. Moreover, I didn't have a look at the labels in the other LibreOffice softwares. Still, I'm at the disposal of whoever would like a more extensive list, which of course should be checked by the proper service before being submitted. My report followed the reading of a similar remark in bug #145109.
Here are guidelines [1] and there [2] how to fix such an issue. In a nutshell: it depends on the context whether a string is a title or not. For example .uno:ClassificationApply and .uno:ClassificationDialog in [3]. So to make this report an actionable ticket I suggest to list only those strings that need action. Shouldn't be too many since we continuously improve here. [1] https://wiki.documentfoundation.org/Design/Guidelines [2] https://design.blog.documentfoundation.org/2018/02/28/easyhacking-all-about-terminology/ [3] https://opengrok.libreoffice.org/xref/core/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu?r=95e7a57d&mo=273533&fi=7106#7106
As a translator I'd also like to ask whoever finally act on this issue to synchronize the changes with the start of a development cycle. For example, right now is a bad time for such (mostly) cosmetic changes, it's better to wait a month until 7.3 is branched and master is for 7.4 development. This way translators can concentrate on more important missing translations before the 7.3 release. If a single opinion from me is not enough, one can ask the l10n mailing list l10n@global.libreoffice.org for a wider consensus.
Needinfo for several month now. Terminology is continuously improved and the few items that need action should be picked up.
I’ll take it
Dear Adolfo Jayme Barrientos, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assign it back to yourself if you're still working on this.