From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Random832 Newsgroups: gmane.emacs.devel Subject: Re: Casting as wide a net as possible Date: Mon, 14 Dec 2015 12:59:10 -0500 Message-ID: <87zixcud1t.fsf@fastmail.com> References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1450116030 9165 80.91.229.3 (14 Dec 2015 18:00:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 14 Dec 2015 18:00:30 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 14 19:00:24 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1a8XQ8-0006IQ-0I for ged-emacs-devel@m.gmane.org; Mon, 14 Dec 2015 19:00:24 +0100 Original-Received: from localhost ([::1]:33123 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8XQ7-0001bB-04 for ged-emacs-devel@m.gmane.org; Mon, 14 Dec 2015 13:00:23 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38355) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8XPP-0000y6-O3 for emacs-devel@gnu.org; Mon, 14 Dec 2015 12:59:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a8XPM-0003Vp-IF for emacs-devel@gnu.org; Mon, 14 Dec 2015 12:59:39 -0500 Original-Received: from plane.gmane.org ([80.91.229.3]:52883) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a8XPM-0003VX-Bs for emacs-devel@gnu.org; Mon, 14 Dec 2015 12:59:36 -0500 Original-Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1a8XPG-0004P7-V9 for emacs-devel@gnu.org; Mon, 14 Dec 2015 18:59:30 +0100 Original-Received: from c-68-39-146-59.hsd1.in.comcast.net ([68.39.146.59]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 14 Dec 2015 18:59:30 +0100 Original-Received: from random832 by c-68-39-146-59.hsd1.in.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Mon, 14 Dec 2015 18:59:30 +0100 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 27 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-68-39-146-59.hsd1.in.comcast.net User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) Cancel-Lock: sha1:bsO8Ft4HZvpozfse01pjfCJbaLk= X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 80.91.229.3 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:196254 Archived-At: Filipp Gunbin writes: > On 14/12/2015 21:01 +0600, Yuri Khan wrote: >> On Mon, Dec 14, 2015 at 8:41 PM, Filipp Gunbin wrote: >>> When I started using Emacs, it attracted me with the ease of working >>> with codings. I've tried some editors at that time, of course >>> (including well-known IDEs, for years), but never before it was so easy >>> to just open a file in a given coding, or re-open it in another. We, >>> non-English-natives, still have problems with different encodings (yes, >>> KOI8-R, CP-1251 and CP-866 for Russian are still here) and Emacs helped >>> me to learn more clearly what the encoding is. >> >> English natives have worse problems with encodings. > > What do you mean? Just interesting. The definition of "worse" is subjective, but I think what he's referring to is the fact that someone might open a file in the wrong encoding, without noticing or caring that some accented word or punctuation symbol in some paragraph deep within the file looks wrong, add more content in the new encoding, save it... then you have a file which has a mixture of bytes in different encodings, which is very difficult to fix automatically. Whereas, if you open a file in Cyrillic (or, say, Japanese), you know immediately that it's in the wrong encoding and won't do any editing until the coding situation is fixed.