Desktop entry should be localizable
Description
This is not necessary yet, because the desktop entry currently only contains the product name. However, setting it up to be translated wouldn't hurt and would be useful when we decide to add a description to it.
More information on desktop entries can be found in #1600.
Suggested implementation
Generally speaking, a press.freedom.SecureDropClient.desktop.in file could be created that is set up for the translations with GETTEXT, then make or meson could be used to generate the press.freedom.SecureDropClient.desktop file with the correct language entries from the translation files.
Existing example for inspiration: The following template is rendered by ansible to create desktop shortcuts.
Looking for more guidance? @nathandyer and @cfm may be able to help!
How will this impact SecureDrop users?
This would allow us to enhance the desktop entry with a description of the application.
How would this affect the SecureDrop Workstation threat model?
No changes to the threat model. (The translation process is already part of the threat model.)
User Stories
When I am about to start an application, I want to be able to confirm that is is the application I think it is by reading its description in a language I understand.
Keeping open; every string should be open to i18n (in some instances folks may want to transliterate rather than translate).