From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Grep Japanese characters
Date: Fri, 13 Jul 2018 10:21:40 +0300 [thread overview]
Message-ID: <838t6feh2z.fsf@gnu.org> (raw)
In-Reply-To: <864lh3g629.fsf@misasa.okayama-u.ac.jp> (message from Tak Kunihiro on Fri, 13 Jul 2018 12:36:46 +0900)
> From: Tak Kunihiro <homeros.misasa@gmail.com>
> Cc: help-gnu-emacs@gnu.org
> Cc: tkk@misasa.okayama-u.ac.jp
> Date: Fri, 13 Jul 2018 12:36:46 +0900
>
> CMD> c:/emacs-26.1/bin/runemacs.exe -Q
>
> M-: w32-ansi-code-page
> --> 65001 (#o176751, #xfde9)
>
> M-: (w32-get-console-codepage) RET
> --> 65001 (#o176751, #xfde9)
>
> M-: (w32-get-console-output-codepage) RET
> --> 65001 (#o176751, #xfde9)
>
> CMD> c:/emacs-26.1/bin/emacs.exe -nw -Q
>
> M-x view-hello-file
> --> Letters besides ascii are all bricks (tofu).
Thanks. That's expected, more or less. The conclusion is that UTF-8
can be used as a locale's codeset (good!), but sending UTF-8 text to
the console still doesn't work well (not so good). So if people use
this knob in Windows 10, they should arrange for console input and
output to be in some codepage other than 65001 (a.k.a. UTF-8).
It's possible that using a better font for the console, such as Lucida
Console, will at least allow you to show Latin, Cyrillic, and Greek
characters in HELLO, btw. Not sure what will happen with characters
beyond the BMP, maybe Windows 10 has improved in that part as well.
next prev parent reply other threads:[~2018-07-13 7:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-11 23:02 Grep Japanese characters Tak Kunihiro
2018-07-12 2:40 ` Eli Zaretskii
2018-07-12 3:05 ` YUE Daian
2018-07-12 13:10 ` Tak Kunihiro
2018-07-12 13:37 ` Eli Zaretskii
2018-07-13 3:36 ` Tak Kunihiro
2018-07-13 7:21 ` Eli Zaretskii [this message]
2018-07-13 14:06 ` Filipp Gunbin
2018-07-13 14:36 ` Eli Zaretskii
2018-07-16 20:11 ` Filipp Gunbin
2018-07-17 2:29 ` Eli Zaretskii
2018-07-13 2:58 ` YUE Daian
2018-07-12 13:23 ` Eli Zaretskii
2018-07-12 5:05 ` Yuri Khan
2018-07-12 13:27 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838t6feh2z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.