From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Grep Japanese characters Date: Fri, 13 Jul 2018 17:36:33 +0300 Message-ID: <83lgafcidq.fsf@gnu.org> References: <20180712.080255.586725992291613595.tkk@misasa.okayama-u.ac.jp> <83a7qxfa7r.fsf@gnu.org> <87d0vt2lxj.fsf@yue-d-PC.i-did-not-set--mail-host-address--so-tickle-me> <86pnzsbnvu.fsf@misasa.okayama-u.ac.jp> <8336wofudf.fsf@gnu.org> <864lh3g629.fsf@misasa.okayama-u.ac.jp> <838t6feh2z.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1531492509 25371 195.159.176.226 (13 Jul 2018 14:35:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 13 Jul 2018 14:35:09 +0000 (UTC) To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Jul 13 16:35:05 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fdzA0-0006S6-Ss for geh-help-gnu-emacs@m.gmane.org; Fri, 13 Jul 2018 16:35:04 +0200 Original-Received: from localhost ([::1]:37671 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzC7-0004T6-Ih for geh-help-gnu-emacs@m.gmane.org; Fri, 13 Jul 2018 10:37:15 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35335) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzBV-0004Sm-UI for help-gnu-emacs@gnu.org; Fri, 13 Jul 2018 10:36:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fdzBR-0000pn-HX for help-gnu-emacs@gnu.org; Fri, 13 Jul 2018 10:36:37 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:47882) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fdzBR-0000pb-CO for help-gnu-emacs@gnu.org; Fri, 13 Jul 2018 10:36:33 -0400 Original-Received: from [176.228.60.248] (port=1038 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1fdzBQ-0003Oy-BJ for help-gnu-emacs@gnu.org; Fri, 13 Jul 2018 10:36:33 -0400 In-reply-to: (message from Filipp Gunbin on Fri, 13 Jul 2018 17:06:38 +0300) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:117436 Archived-At: > From: Filipp Gunbin > Cc: help-gnu-emacs@gnu.org > Date: Fri, 13 Jul 2018 17:06:38 +0300 > > > 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). > [..] > > But in message <86pnzsbnvu.fsf@misasa.okayama-u.ac.jp> above it was > reported that grepping of these non-ascii chars worked from emacs, no? When you gerp from Emacs, the results of the search are not displayed by the Windows console, they get read by Emacs and displayed by Emacs. And (GUI) Emacs can display _any_ character supported by the fonts installed on the systems, regardless of the codepage. But if people run Grep from the shell prompt, they will see unreadable output, even on Windows 10 with that setting in effect. > And what does "using as locale's codeset" then means in your message? A locale's most general specification is ll_CC.ENC, where ll is the language, CC is the country, and ENC is the encoding. Example from Posix systems: pr_BR.UTF-8, for Brazilian variety of Portuguese with UTF-8 encoding. Example from Windows: French_Canada.1252 (where 1252 is the codepage used for encoding). The ENC part is also known as "codeset". More about that, for Windows in particular, here: https://msdn.microsoft.com/en-us/library/x99tb11d.aspx You will see that the MS doc still says UTF-8 is not supported as the ENC part.