[COSMETIC] Update all lowercase context menu descriptions to match sentence casing of other entries

[3QQPcr]

Please consider unifying all context menu descriptions to use sentence case without closing periods (e.g. "This is sentence case") oppose to all lowercase (e.g. "this is all lowercase obviously").

For example, I have noticed the following right click context menu entry descriptions are all lowercase:
Move to Other Pane ... "move selected item(s) from active pane to other pane"
Copy to Other Pane ...
-
Move Up ...
Show 64-bit Context Menu ...
Example: https://i.imgur.com/M05yfv0.png.

All "Rename Special" context menu sub-entries are also in all lowercase ("rename all selected list items") or "toggle preview for all ..." for the "Preview All" entry.
Example: https://i.imgur.com/4Wp18qq.png.

You can see other descriptions are in standard Title Casing with periods: https://i.imgur.com/AN5JnjP.png.

In conclusion, I suggest that all context menu entries be unified in either all lowercase, all Title Case (with closing periods) or all Title Case (without closing periods - I think this looks best and is most practical since I don't see any examples of descriptions that require a period to separate two statements).

I imagine this could be an easy update and would help improve uniformity within XYplorer.

[admin]

It's done to save space.

[3QQPcr]

It's done to save space.

I'm not trying to argue with you, I truly appreciate all the time and effort the dev team puts into XYplorer, but:

• Why can the "Cut" context entry description with 61 characters, "Removes the selected items and copies them onto the Clipboard.", start with a capital letter (https://imgur.com/AN5JnjP);

• and the shorter "Move to Other Pane" context entry description with 52 characters, "move selected item(s) from active pane to other pane", need to start with a lowercase letter when it has less characters (https://imgur.com/M05yfv0)?

• If done to save space, shouldn't the longer description be in all lowercase and the shorter description start with a capital letter? This is why I am a bit confused.

Maybe I'm misunderstanding your reasoning "to save space", but shouldn't all descriptions be able to start with a capital letter if they're at least 61 characters or under, as demonstrated above?
I think that may be the longest description I've encountered and if that's the case I would think all descriptions would qualify for Sentence casing.

If it's not possible to Sentence case all context menu descriptions, then you might want to consider just lowercasing all descriptions for uniformity, especially considering many of them are already all lowercase.
It's a bit odd to have mixed Sentence case and lowercase descriptions, especially if character limits are supposed to determine the casing.

I don't mean to make this a big issue because it's not, I just wanted to clarify what I was suggesting in case I was not clear originally.

Thanks again for taking the time to address feedback.

[admin]

I understand (and also feel) your unhappiness with the different orthographies. The thing is that they come from different sources. The "Cut" item and its description are from the Windows shell, I just present them how they are given to me from Windows. "Move to Other Pane" OTOH is my own and a long time ago (when monitors were much smaller than today) I tried to save every pixel I could and therefore went for lower case in the status bar.

Today I would be ready to change that, because we have the space now and can afford it. However, there is another problem: The translations. If I change a single letter in a sentence then this sentence is presented to each of our translators as "needs new translation". I have to weigh up carefully whether it's worth it.

[admin]

Next beta will add sentence case to quite some status bar messages. Looks good.

[3QQPcr]

... a long time ago (when monitors were much smaller than today) I tried to save every pixel ...
... However, there is another problem: The translations ...

Good explanation, I now understand the issue is more complex than I imagined.

Next beta will add sentence case to quite some status bar messages. Looks good.

Great work, thanks again for your time and consideration!