unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 17:42:13 +0300	[thread overview]
Message-ID: <cef1fb0e-cf57-ba78-9b36-ed57ddb1c848@gmail.com> (raw)
In-Reply-To: <83sgee0xu8.fsf@gnu.org>

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

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. WSL Emacs 
works perfectly fine with "emacs -Q -nw" even from cmd.exe. You can look 
at the attachments.


On 2020-06-29 17:07, Eli Zaretskii wrote:
>> From: Yigit Emre Sahinoglu <yigitemres@gmail.com>
>> Date: Sun, 28 Jun 2020 22:46:39 +0300
>> Cc: 42099@debbugs.gnu.org
>>
>> w32-get-console-codepage = 437 (#0665, #x1b5). Problem still exists as
>> I described (ö, ç, ü works but ş, İ (types 0), ğ are broken.)
> OK.  So I think the problem might be in the setup of the Windows
> system.  If you type "chcp RET" in the Command Prompt window, does it
> also show codepage 437?  And if you type the problematic characters
> into the Command Prompt window (outside of Emacs) at the cmd.exe
> prompt, do you also see those characters displayed incorrectly?

[-- Attachment #2: cmd_XAWZQ3ayEB.png --]
[-- Type: image/png, Size: 25778 bytes --]

[-- Attachment #3: cmd_3LO9oNHOnO.png --]
[-- Type: image/png, Size: 25654 bytes --]

  reply	other threads:[~2020-06-29 14:42 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 [this message]
2020-06-29 15:51                     ` Eli Zaretskii
2020-06-29 17:06                       ` Yigit Emre Sahinoglu
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=cef1fb0e-cf57-ba78-9b36-ed57ddb1c848@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).