From: "Fatih Aydın" <fatihaydin138@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: larsi@gnus.org, 44604@debbugs.gnu.org,
Fatih Aydin <fataydin138@gmail.com>
Subject: bug#44604: 27.1; gpg error when language environment is set to Turkish
Date: Sun, 15 Nov 2020 20:52:49 +0000 [thread overview]
Message-ID: <CAE-wskK0+2_=nFRqZfneoE7DRs57DLvgPV0=89Mk6kSTwZz6FA@mail.gmail.com> (raw)
In-Reply-To: <83sg9bu3bq.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1811 bytes --]
Is there something I can do to help with the process of solving this
problem?
Also do you think that this will solved in the next release?
Eli Zaretskii <eliz@gnu.org>, 14 Kas 2020 Cmt, 19:49 tarihinde şunu yazdı:
> > From: Fatih Aydin <fataydin138@gmail.com>
> > Date: Sat, 14 Nov 2020 19:31:56 +0000
> > Cc: Lars Ingebrigtsen <larsi@gnus.org>, 44604@debbugs.gnu.org
> >
> > To make sure that it will solve the problem, I have applied the solution
> you suggested.
> > Copied the source and changed '^direct' to '^DIRECT' and builded.
> >
> > The proxy problem is solved, but the package-install gpg problem I
> mentioned (Error while verifying signature
> > archive-contents.sig:) is still there.
> >
> > Also I found another weird bug related to this:
> > with English language environment visit 'https://www.google.com.tr'
> using eww, you will see the Turkish
> > characters correctly.
> > with Turkish language environment, do the same thing, you will see weird
> characters instead of Turkish
> > characters.
>
> The ELisp manual says:
>
> Some language environments modify the case conversions of ASCII
> characters; for example, in the Turkish language environment, the ASCII
> capital I is downcased into a Turkish dotless i (‘ı’). This can
> interfere with code that requires ordinary ASCII case conversion, such
> as implementations of ASCII-based network protocols. In that case, use
> the ‘with-case-table’ macro with the variable ASCII-CASE-TABLE, which
> stores the unmodified case table for the ASCII character set.
>
> I guess we need to use this around forms that implement network
> protocols. At least this doesn't seem to help:
>
> M-: (with-case-table ascii-case-table (eww "https://www.google.com.tr"))
> RET
>
[-- Attachment #2: Type: text/html, Size: 2571 bytes --]
next prev parent reply other threads:[~2020-11-15 20:52 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 [this message]
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
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='CAE-wskK0+2_=nFRqZfneoE7DRs57DLvgPV0=89Mk6kSTwZz6FA@mail.gmail.com' \
--to=fatihaydin138@gmail.com \
--cc=44604@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fataydin138@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).