GnuPG 2.0 vs. 1.4 locale; gpgme_set_locale

Albrecht Dreß albrecht.dress at
Tue Nov 28 20:30:53 CET 2006

Am 28.11.06 09:04 schrieb(en) Werner Koch:
> It is actually easier:  We have the options
>     --display
>     --ttyname
>     --ttytype
>     --lc-ctype
>     --lc-messages
> To override the values from the environment.  Just pass them to gpg
> (>= 1.3.0).

That is actually trivial, and I already have a patch for gpgme.  However,  
it doesn't work...  I have the agent launched with locale de_DE (i.e.  
Latin1).  When I run gpg 2.0.0 from a command line, also in locale de_DE,  
with the following command

gpg --lc-ctype de_DE.UTF-8 --lc-messages de_DE.UTF-8 --sign --armor

pinentry comes up, but still with a wrong string!  I dumped the input  
string, and here is what I get:

Sie benötigen eine Passphrase, um den geheimen Schlüssel zu entsperren.
Benutzer: "Albrecht Dreß (NetCologne) <albrecht.dress at>"
1024-bit DSA Schlüssel, ID D027FFD1, erzeugt 2002-04-15

The information string is still in Latin1 (e.g. ö == 0xf6), but the key  
information is in utf-8 (e.g. ß == 0xc39f).  Replace the same command  
above with gpg-1.4, and the /complete/ string is properly encoded in utf8  
(i.e. ö == 0xc3b6).

Any ideas?

Cheers, Albrecht.

  Albrecht Dreß  -  Johanna-Kirchner-Straße 13  -  D-53123 Bonn (Germany)
        Phone (+49) 228 6199571  -  mailto:albrecht.dress at
   GnuPG public key:
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : /pipermail/attachments/20061128/5d19caa9/attachment.pgp

More information about the Gnupg-devel mailing list