Subject: bug#44604: 27.1; gpg error when language environment is set to Turkish

From: Lars Ingebrigtsen <[email-masked]>
Date: Mon, 16 Nov 2020 22:26:02 +0100

Eli Zaretskii <[email-masked]> writes:

> I think we need a new infrastructure for solving this.

Looks that way -- we're using the same functions to handle human-input
text (i.e., commands like `M-u') as API/protocol text (comparing DIRECT
and direct by downcasing), and that's problematic.

So we'd have to add a bunch of functions to handle stuff like this, but
it seems like a rather daunting task.

Or we could do something simple, like having a buffer-local variable
that says "the characters in this buffer are protocol data" and which
would make the locale the "C" locale?  Hm...  there'd probably be some
messy fallout from that, too.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no