From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: fatihaydin138@gmail.com, 44604@debbugs.gnu.org
Subject: bug#44604: 27.1; gpg error when language environment is set to Turkish
Date: Tue, 17 Nov 2020 05:30:17 +0200 [thread overview]
Message-ID: <831rgsslrq.fsf@gnu.org> (raw)
In-Reply-To: <871rgtxac5.fsf@gnus.org> (message from Lars Ingebrigtsen on Mon, 16 Nov 2020 22:26:02 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Fatih Aydın <fatihaydin138@gmail.com>,
> fataydin138@gmail.com,
> 44604@debbugs.gnu.org
> Date: Mon, 16 Nov 2020 22:26:02 +0100
>
> Eli Zaretskii <eliz@gnu.org> 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.
I thought about something rather simple: a global variable, let's name
it overriding-case-table, that will be heeded to by the various case
conversions ('downcase' etc.) in preference to any other case-table.
Then commands that need strict ASCII case rules could bind that
variable, or we could use with-case-table macro, without fear that
different buffers will behave in different ways.
I didn't look at the code yet, so maybe this simple idea is not
workable. But if it is, it should be very simple to implement.
next prev parent reply other threads:[~2020-11-17 3:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 19:44 bug#44604: 27.1; gpg error when language environment is set to Turkish Fatih Aydin
2020-11-13 8:12 ` Eli Zaretskii
2020-11-13 9:10 ` Fatih Aydin
2020-11-13 12:07 ` Eli Zaretskii
2020-11-13 14:19 ` Fatih Aydin
2020-11-14 16:39 ` Lars Ingebrigtsen
2020-11-14 17:09 ` Fatih Aydin
2020-11-14 17:51 ` Eli Zaretskii
2020-11-14 19:31 ` Fatih Aydin
2020-11-14 19:48 ` Eli Zaretskii
2020-11-15 20:52 ` Fatih Aydın
2020-11-16 16:16 ` Eli Zaretskii
2020-11-16 20:53 ` Fatih Aydin
2020-11-17 3:22 ` Eli Zaretskii
2020-12-01 11:06 ` Fatih Aydin
2020-12-02 10:07 ` Lars Ingebrigtsen
2021-04-21 11:42 ` Fatih Aydin
2021-04-25 18:58 ` Lars Ingebrigtsen
2021-04-25 19:03 ` Eli Zaretskii
2020-11-16 21:26 ` Lars Ingebrigtsen
2020-11-17 3:30 ` Eli Zaretskii [this message]
2020-11-24 5:16 ` Lars Ingebrigtsen
2020-11-24 15:20 ` Eli Zaretskii
2020-11-25 6:19 ` Lars Ingebrigtsen
2020-11-25 15:24 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831rgsslrq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44604@debbugs.gnu.org \
--cc=fatihaydin138@gmail.com \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).