Add L10N comments to several unclear messages

Updating Japanese translation, I found that some of the updated messages
were a little hard to understand without reading the code.

Add comments to some messages I nearly translated in a wrong way.

diff --git a/mutt_account.c b/mutt_account.c
index 41d0a09bdd92dad46e57eea72671a2de000913dd..3302b5ed9f13e1f21aa96def5cb0c5a958d151b1 100644 (file)
--- a/mutt_account.c
+++ b/mutt_account.c
@@ -375,6 +375,11 @@ char *mutt_account_getoauthbearer(struct ConnAccount *account)
 
   if (!cmd)
   {
+    /* L10N: You will see this error message if (1) you have "oauthbearer" in
+       one of your $*_authenticators and (2) you do not have the corresponding
+       $*_oauth_refresh_command defined. So the message does not mean "None of
+       your $*_oauth_refresh_command's are defined."
+     */
     mutt_error(_("No OAUTH refresh command defined"));
     return NULL;
   }

diff --git a/ncrypt/crypt_gpgme.c b/ncrypt/crypt_gpgme.c
index dd825b83f68087d5e1c58ca9860f6cf776c8225f..5f91fe1215576c7dce826e5765c2a55ee064d2d4 100644 (file)
--- a/ncrypt/crypt_gpgme.c
+++ b/ncrypt/crypt_gpgme.c
@@ -1538,6 +1538,9 @@ static void print_smime_keyinfo(const char *msg, gpgme_signature_t sig,
     }
     else
     {
+      /* L10N: You will see this message in place of "KeyID "
+         if the S/MIME key has no ID. This is quite an error.
+       */
       state_puts(_("no signature fingerprint available"), s);
     }
     state_puts("\n", s);

diff --git a/ncrypt/pgp.c b/ncrypt/pgp.c
index 7cc6ac07f5355d3f21236adcbcbade8f27fee1d1..4eb05ee7fc162d24c84a80112bfab7967159f4ab 100644 (file)
--- a/ncrypt/pgp.c
+++ b/ncrypt/pgp.c
@@ -727,7 +727,13 @@ int pgp_class_application_handler(struct Body *m, struct State *s)
           if (could_not_decrypt || (decrypt_okay_rc <= -3))
             mutt_error(_("Could not decrypt PGP message"));
           else if (decrypt_okay_rc < 0)
+          {
+            /* L10N: You will see this error message if (1) you are decrypting
+               (not encrypting) something and (2) it is a plaintext. So the
+               message does not mean "You failed to encrypt the message."
+            */
             mutt_error(_("PGP message was not encrypted"));
+          }
           else
             mutt_message(_("PGP message successfully decrypted"));
         }

diff --git a/recvcmd.c b/recvcmd.c
index b5b503f1120e34e0993514830618ae4fa54db65b..a7d357d4e392c622a05c06d812b9a2aaa4790bd6 100644 (file)
--- a/recvcmd.c
+++ b/recvcmd.c
@@ -1049,6 +1049,9 @@ void mutt_attach_mail_sender(FILE *fp, struct Email *e, struct AttachCtx *actx,
 {
   if (!check_all_msg(actx, cur, 0))
   {
+    /* L10N: You will see this error message if you invoke <compose-to-sender>
+       when you are on a normal attachment.
+     */
     mutt_error(_("You may only compose to sender with message/rfc822 parts"));
     return;
   }