Hi, after the debug session yesterday we found the problem: The translation was not switched to the LC_MESSAGES value as received from gpg. Thus the gpg-agent displayed static strings in it own locale while displaying strings received from gpg (description of the key) in gpg's locale.
The fix was not trivial but fianlly I am able to switch gpg's locale at will and Pinentry shows the correct translation. I have commited this to master and it will go into 2.1.6. The question is whether the work and possible breakage of backporting this to 2.0 is justified. This bug has been around for about a decade but was not really noticed. Thus, I would suggest not to backport it to 2.0. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org