Fix up user-facing Remote Access terminology

[SaschaCowley]

Link to issue number:

Fixes #17815

Summary of the issue:

NVDA's new Remote Access feature currently uses inconsistent terminology.

Description of user facing changes

Remote Access:

• Is consistently referred to as "Remote Access".
• Uses the term "computer" to refer to clients.
  • Previously both "computer" and "machine" were used. I also considered "device", as this seems to be the preferred terminology in Windows.
• Uses the word "send" instead of "push" for sending the clipboard to connected clients.
• Has descriptive help items for its menu items, all of which are complete sentences.
• Uses sentence fragments for UI messages where appropriate

Description of development approach

Generated a pot file, and searched for the word "remote" therein. If it was referring to Remote Access, and some other name was used, replaced it with Remote Access.

Searched for the word "remote" in the user guide and edited as appropriate. Also did a full readthrough of the remote section.

Reviewed the strings in the settings dialog, menu, and cues explicitly and edited as appropriate.

Calculated the diff 1b4a28d4d...9833d7812. Searched in it for newly introduced translator comments, and edited them if related to Remote Access and I thought they were unclear.

Calculated the diff 9833d7812...42aaea791. Reviewed it for any changed strings that used gettext (_(...)), and changed to use pgettext (pgettext("remote", ...)).

Testing strategy:

pre-commit.
Unit tests.
Checking the generated pot file.

Known issues with pull request:

The remote section of the user guide still needs some TLC, however I believe this is best worked through in a separate PR with input from @qchristenson.

Code Review Checklist:

• Documentation:
  • Change log entry
  • User Documentation
  • Developer / Technical Documentation
  • Context sensitive help for GUI changes
• Testing:
  • Unit tests
  • System (end to end) tests
  • Manual testing
• UX of all users considered:
  • Speech
  • Braille
  • Low Vision
  • Different web browsers
  • Localization in other languages / culture than English
• API is compatible with existing add-ons.
• Security precautions taken.

@coderabbitai summary

[CyrilleB79]

Here are various comments.

• Translators comments: some of them still use remote or NVDA remote.
• Other comments (code comment): idem

Maybe you missed them. Searching the whole code could be better than doing it on a diff? I have flagged some of them but there are more of them.

I have also made other little remarks. If you find them off-topic, let me know and I'll add them in a separate issue or PR if needed.

[LeonarddeR]

Sorry for the close/reopen mess I made there.
Now that Terminologie is being looked at, I like to ask attention to the following.
There is still #3564. I wrote the RDAccess add-on for that. That add-on has a "remote desktop" category in settings, and mostly refers to remote desktop.
I'm considering donating at least parts of that add-on to core, but I expect a conflict in terminology. Any thoughts on that matter? Or may be that's more for a follow up. I'm bringing this up here because this seems to be a moment to discuss it.

[CyrilleB79]

"Mute remote" is still there, for "Mute remote computer". But maybe in menus, we want to keep something very short.

Unfortunately, to translate (French), we'll need to make something much longer. English language has the capability to precisely express an idea with very few words, but other languages are not so good at it...

[Qchristensen]

UserGuide Reads well!