Inconsistent use of terminology, ctd: OpenPGP, PGP, GnuPG
Submitted by Jens Erat
Link to original bug (#741840)
Description
Seahorse has no consistent use regarding the terms OpenPGP, PGP and GnuPG, mixing standards and implementations, and even using the wrong terms.
This question on Ask Ubuntu pretty much describes the confusion created by this, and also includes an example screenshot: http://askubuntu.com/q/564024/167385
I propose following:
- Never use the (trademarked!) term PGP, as I'm pretty sure Seahorse does not interface PGP anywhere.
- Use OpenPGP instead, whenever talking about keys, messages and similar things. OpenPGP is the standard behind PGP and GnuPG, and keys and messages are compatible with other OpenPGP implementations.
- Use GnuPG if actually referring to the implementation used, ie. with error messages and/or explanations what's going on under the hood. It might be reasonable also to use it with the keyring, as the keys actually are stored in GnuPG.
Getting a proper wording, so the user is not confused by the difference between "OpenPGP" and "GnuPG" might not be easy, but it can't get worse than the current one.
In the free software world, we should pay attention on emphasizing the difference between standards and implementations.
Version: 3.14.x