Currently we list internal names such as CharPosture (italic for PS Citation) or ParaTopMargin (212) while users understand Font > Western > Style and Indents & Spacing > Above Paragraph > 0.21cm (0.39 line). If we can pick the labels from the properties dialog I suggest to only use the actual label and show the tab name in tooltip.
What can be a way to implement this ? There is a way in my mind. To have an unordered map and store all the properties with their correct display name something like :- { {"DisplayName", "Display Name"}, {"CharHeight", "Char Height"} .... } I think it would be a good plan to implement this before making strings localisable.
... or in most of the cases, we need to add a space in the property name whenever we get a Capital letter, so just insert space in before all the capital letters(except first). I implemented this and it works pretty well. https://imgur.com/a/C8MFCru
We need to use the map of API names to RID_ defines, which should be defined as en-US names in a dedicated .hrc. IMO we still need to also provide API name in SI, too. It should be either as a tooltip, or in third column. That would be useful for those who are creating macros. The same way as we added tooltips with UNO names to the entries in customization dialog. Inserting spaces before capitals is not a solution. It is not translatable. It does not allow to come with a good name for things like "ContinueingPreviousSubTree" (a property name that has a typo - Continu*e*ing, that we cannot change because of API breakage) or like "UsePP" (will you output it as "Use P P"? that's wrong, it should be "Use pp", because it 'determines if following page numbers are displayed using a "pp."').
Shivam Kumar Singh committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f39f37326ac787e88a0782915afac91cf418a539 tdf#134560 tdf#135107 make inspector contents human readable It will be available in 7.1.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
"Para Hyphenation Max Leading Chars" is too big, and gets trimmed towards the end when displayed in the panel. Can we change "Hyphenation" -> "Hyphen" or increase the column width, perhaps ?
Heiko had suggested at gerrit "Can we show ellipsis when the column is too small?"
(In reply to Shivam Kumar Singh from comment #6) > Heiko had suggested at gerrit "Can we show ellipsis when the column is too > small?" inspectorpanel.ui: cellrendertext1 > ellipsis = end (initial column width for value is minimized in case of very long strings and ellipsis show from the beginning, so no additional max-width setting needed)