unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Fatih Aydin <fataydin138@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44604@debbugs.gnu.org
Subject: bug#44604: 27.1; gpg error when language environment is set to Turkish
Date: Wed, 21 Apr 2021 14:42:47 +0300	[thread overview]
Message-ID: <CAHRQZ1yNAspJ4o8XcR_FZrzjNDPU7tv6VshzYv=jb4fiRSpG6A@mail.gmail.com> (raw)
In-Reply-To: <87o8jc4j3d.fsf@gnus.org>

[-- Attachment #1: Type: text/plain, Size: 1234 bytes --]

 I keep encountering this problem with different packages, everything
functions incorrectly, as you can guess. Is there any progress?

On Wed, Dec 2, 2020 at 1:07 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:

> Fatih Aydin <fataydin138@gmail.com> writes:
>
> > Let there be a new variable to define file types (according to
> extension) and the
> > lang. env. for those file types. For '.el' files, English lang. env. can
> be assigned
> > using that variable.
> > That means the user will have an option to say: 'Always evaluate .el
> files using
> > English language' to Emacs.
>
> That's not really the issue -- this is always about .el files, but it's
> about how to handle text in different contexts.
>
> For instance, you may have a mail buffer with code that's generating
> mail headers, so you have a structure that contains
>
> (("MY-NAME-IS" "ASIL"))
>
> and you have code that's supposed to generate, from that, a header that
> looks like:
>
> My-name-is: Asıl
>
> The code has to know that the former bit is a "protocol string" and the
> latter bit is a "language string".
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no
>

[-- Attachment #2: Type: text/html, Size: 1784 bytes --]

  reply	other threads:[~2021-04-21 11:42 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 [this message]
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='CAHRQZ1yNAspJ4o8XcR_FZrzjNDPU7tv6VshzYv=jb4fiRSpG6A@mail.gmail.com' \
    --to=fataydin138@gmail.com \
    --cc=44604@debbugs.gnu.org \
    --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).