From: Yigit Emre Sahinoglu <yigitemres@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 42099@debbugs.gnu.org
Subject: bug#42099: Emacs -nw Turkish Layout Problem
Date: Mon, 29 Jun 2020 20:06:35 +0300 [thread overview]
Message-ID: <CAKDmE5Eqs7khvqQB8Y93BKHm7sEDQJBNBQknA2mh1M7tFzYqCQ@mail.gmail.com> (raw)
In-Reply-To: <83h7ut27lr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
>
> C-x RET t cp857 RET
>
C-x RET k cp857 RET
Not helping. The problem still exists.
This is Windows 10, right? Do you per chance have the UTF-8 support
> feature enabled?
>
I use Windows 10. I cannot find UTF-8 support feature (look from `Windows
features on or off` from Control Panel) but I'm pretty sure that UTF-8
support feature exists. Only problematic software I'm aware of is `emacs
-nw`.
Yiğit Emre Şahinoğlu
On Mon, Jun 29, 2020 at 6:51 PM Eli Zaretskii <eliz@gnu.org> wrote:
> > Cc: 42099@debbugs.gnu.org
> > From: Yigit Emre Sahinoglu <yigitemres@gmail.com>
> > Date: Mon, 29 Jun 2020 17:42:13 +0300
> >
> > chcp returns "Active code page: 437"
> >
> > All chars displayed correctly on cmd.exe. It's something about Emacs
> > Windows (maybe mingw do something finicky), I'm sure of that.
>
> As long as the codepage reported to Emacs is 437, you will not be able
> to see nor input Turkish characters. the question is why is this
> codepage being returned, when the system evidently uses a different
> encoding...
>
> This is Windows 10, right? Do you per chance have the UTF-8 support
> feature enabled?
>
> You could also try this, once inside Emacs:
>
> C-x RET t cp857 RET
> C-x RET k cp857 RET
>
> Does that help?
>
[-- Attachment #2: Type: text/html, Size: 2787 bytes --]
next prev parent reply other threads:[~2020-06-29 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 1:23 bug#42099: Emacs -nw Turkish Layout Problem Yigit Emre Sahinoglu
2020-06-28 14:19 ` Eli Zaretskii
[not found] ` <CAKDmE5FJM49FgEtPhRhpNHxR1S=8gDjUeSawzucpdUdQDkVHxQ@mail.gmail.com>
2020-06-28 17:01 ` Eli Zaretskii
[not found] ` <CAKDmE5Hx4cH=1HZx+wJ=vD0QY_VD0+fTxwGiT2w08JOQgHDAbg@mail.gmail.com>
2020-06-28 18:25 ` Eli Zaretskii
2020-06-28 18:39 ` Yigit Emre Sahinoglu
2020-06-28 18:43 ` Yigit Emre Sahinoglu
2020-06-28 19:09 ` Eli Zaretskii
2020-06-28 19:46 ` Yigit Emre Sahinoglu
2020-06-29 14:07 ` Eli Zaretskii
2020-06-29 14:42 ` Yigit Emre Sahinoglu
2020-06-29 15:51 ` Eli Zaretskii
2020-06-29 17:06 ` Yigit Emre Sahinoglu [this message]
2020-06-29 17:09 ` Yigit Emre Sahinoglu
2020-06-30 16:25 ` Eli Zaretskii
2020-06-30 16:35 ` Yigit Emre Sahinoglu
2022-03-22 15:38 ` Lars Ingebrigtsen
2022-04-30 16:26 ` Lars Ingebrigtsen
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=CAKDmE5Eqs7khvqQB8Y93BKHm7sEDQJBNBQknA2mh1M7tFzYqCQ@mail.gmail.com \
--to=yigitemres@gmail.com \
--cc=42099@debbugs.gnu.org \
--cc=eliz@gnu.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).