Re: [PATCH 2/2] Convert pgp key lookups to use local mode addresses.

"Kevin J. McCarthy" <[email protected]> Sun, 17 May 2026 11:08:17 +0800

Newsgroups	gmane.mail.mutt.devel
Message-ID	<agkxIWM3oB9wC-T4@qinghai>

On Sun, May 17, 2026 at 06:32:29AM +0800, Kevin J. McCarthy wrote:
>On Sat, May 16, 2026 at 02:57:13PM +0200, Werner Koch wrote:
>>On Fri, 15 May 2026 20:28, Kevin J. McCarthy said:
>>
>>>diff --git a/crypt.c b/crypt.c
>>
>>>   rfc822_append(last ? &last : &adrlist, msg->env->bcc, 0);
>>>+  mutt_addrlist_to_local(adrlist);
>>
>>If the address is directly passed to gpgme "local" should be utf8 as
>>this is how gpgme or OpenPGP define user ids and thus mail addresses.
>
>Thank you, Werner.  What about when invoking gpg directly (i.e., mutt 
>in classic mode)?  Does the command line gpg translate user ids from 
>the system locale to utf8 for international domains?

Replying to myself, after RTFM :-).  There is an option --utf8-strings, 
default off, that controls whether command line arguments are 
interpreted as utf-8 or in the native locale (or, as specified by 
--display-charset).

Also, --with-colons output is always in utf-8.

I'll have to look through the classic mode code to see whether it's 
dealing with this properly.  But I don't recall any iconv code in there, 
so looks like more work to be done.

-- 
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

signature.asc (application/pgp-signature, 833 B)