Use title case for context menu entries on macOS and Linux

[xhon-pelushi]

Summary

• Use title case for shell/Finder context menu labels on macOS and Linux (Lock File, Share Options, Open in Browser, Copy Internal Link, File Actions).
• Keep Windows sentence case via Q_OS_WIN helpers.
• Title-case Mac File Provider "Always Keep Downloaded" and Linux/macOS VFS pin/free-space actions.

Fixes #10525

Test plan

• On Linux: open a synced file context menu and confirm title-cased labels.
• On Windows: confirm sentence case is unchanged.
• On macOS File Provider: confirm "Always Keep Downloaded" label.

[Rello]

we need to check the translation system to be still working.
as translators need to adjust the strings in transifex, this should not be merged shortly before a release

[github-actions]

Hello there,
Thank you so much for taking the time and effort to create a pull request to our Nextcloud project.

We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process.

Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6

Thank you for contributing to Nextcloud and we hope to hear from you soon!

(If you believe you should not receive this message, you can add yourself to the blocklist.)

[i2h3]

Overall, it looks fine to me. However, I do not know how the different casing in the keys of the localizable strings work out during the lookup (could be evaluated in a manual test of development builds on the different platforms). I mean the Qt code, the file provider is approved by me as it is. And also: does Transifex support different translation keys which differ only in casing? 😵‍💫

[Rello]

@rakekniven
Hi,
can you check the recent comment? do you see an issue with the translations?

[rakekniven]

Even after reading it twice, I still haven’t understood the reason for this change?

Over the last few years, we have changed a great many strings as follows:
"Form Title" -> "Form title"
"FORM TITLE" -> "Form title"
"FormTitle" -> "Form title"

Request for clarification.

And also: does Transifex support different translation keys which differ only in casing?

Unfortunately yes, it does. Translators often ask why we have several strings for different capitalisation. We have therefore gone to the expense of standardising the strings.

[i2h3]

@rakekniven The Nextcloud guidelines conflict with user experience and expectations on Apple devices at our own cost. Based on my experience, platform conventions always beat product conventions. Especially on Apple devices, where users have the highest expectation for consistency compared to the others. Simply put: not following the casing which is present everywhere in the surrounding user interface sticks out negatively and looks unprofessional. I assume that end users will not care for our reasoning and justification in that context but just consider our product badly maintained or not conveying the feeling of being made for the platform beyond an alibi.

To be consistent with platform experiences, use title-style capitalization. Although a game might have a different writing style, generally prefer using title-style capitalization, which capitalizes every word except articles, coordinating conjunctions, and short prepositions, and capitalizes the last word in the label, regardless of the part of speech. For complete guidance on this style of capitalization in English, see title-style capitalization.

References

• Context menus in Human Interface Guidelines
• About labels in menus in Human Interface Guidelines
• title-style capitalization in the Apple Style Guide