From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Karl Fogel Newsgroups: gmane.emacs.devel Subject: Re: Policty question - encoding to use in git repository? Date: Mon, 17 Feb 2014 10:39:39 -0600 Message-ID: <87ha7xk81g.fsf@ktab.red-bean.com> References: <20140217152937.8D831380525@snark.thyrsus.com> Reply-To: Karl Fogel NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1392655204 2005 80.91.229.3 (17 Feb 2014 16:40:04 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Feb 2014 16:40:04 +0000 (UTC) Cc: emacs-devel@gnu.org To: esr@thyrsus.com (Eric S. Raymond) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 17 17:40:11 2014 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 1WFREo-0007ie-0g for ged-emacs-devel@m.gmane.org; Mon, 17 Feb 2014 17:40:10 +0100 Original-Received: from localhost ([::1]:42573 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFREn-0003SR-JN for ged-emacs-devel@m.gmane.org; Mon, 17 Feb 2014 11:40:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50550) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFREf-0003OJ-5o for emacs-devel@gnu.org; Mon, 17 Feb 2014 11:40:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WFREW-0003NK-PG for emacs-devel@gnu.org; Mon, 17 Feb 2014 11:40:01 -0500 Original-Received: from mail-ob0-x22d.google.com ([2607:f8b0:4003:c01::22d]:35204) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WFREW-0003M6-KI for emacs-devel@gnu.org; Mon, 17 Feb 2014 11:39:52 -0500 Original-Received: by mail-ob0-f173.google.com with SMTP id vb8so17332757obc.18 for ; Mon, 17 Feb 2014 08:39:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:reply-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=32vgf+TjfL2EykSGbY2NmGyLrlcbBbWlaKqfZtrxotM=; b=Q7/HrXhLYqausrDV7U6oZ2wCI+OruinxMSw0oBq8hbQLXEjUrtjz/afih8oT0y3O7W FFbpC31LE8IW5U9DnmnMuDSH11Dly/AuPplCtklDN0VYW0N4viTkHSvHIhu/7vOgWtC2 XYcd9+sNW+l8vakJSCi8Y1JZ1AMO7EoJc5N3vhqIRBJXzbp4BdSPmRqZStZ3wGYnd9Ci GVLagf/Ygqdd9EtTXr28K+ctO9TtKOfl8XQ9eGYJu1SWIZWDMSabYxoKfiuvR35RSvNX uYmM6bgJGm+HBWy7G+KhLLvUfrmpB5jEit75+No6xh8r9xYytEoCxdzuRtQ51Lxj51JA /qNQ== X-Received: by 10.182.225.137 with SMTP id rk9mr2461286obc.51.1392655181087; Mon, 17 Feb 2014 08:39:41 -0800 (PST) Original-Received: from ktab.red-bean.com (74-92-190-113-Illinois.hfc.comcastbusiness.net. [74.92.190.113]) by mx.google.com with ESMTPSA id g4sm48716491obe.5.2014.02.17.08.39.40 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Mon, 17 Feb 2014 08:39:40 -0800 (PST) In-Reply-To: <20140217152937.8D831380525@snark.thyrsus.com> (Eric S. Raymond's message of "Mon, 17 Feb 2014 10:29:37 -0500 (EST)") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:4003:c01::22d 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:169700 Archived-At: esr@thyrsus.com (Eric S. Raymond) writes: >While continuing to try to identify correct deletion points for attic >files, I have run across a minor problem: Latin-1 characters in >Changelog files. I have seen two, c-cedilla and something I can't >identify that renders as a backtick. There may be more. I can fix >them up. > >I request a policy decision about what encoding the repository >content should use. I see three reasonable choices: > >* Leave Latin-1 in place. > >* Transcode to UTF-8. (I favor this as the best long-term solution.) > >* Transcode to ASCII approximations - easy in the two cases I've > found so far. +1 to UTF-8 !