Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754623AbdGUR2A (ORCPT ); Fri, 21 Jul 2017 13:28:00 -0400 Received: from ms.lwn.net ([45.79.88.28]:50464 "EHLO ms.lwn.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754028AbdGUR10 (ORCPT ); Fri, 21 Jul 2017 13:27:26 -0400 Date: Fri, 21 Jul 2017 11:27:25 -0600 From: Jonathan Corbet To: frowand.list@gmail.com Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] docs: submitting-patches - change non-ascii character to ascii Message-ID: <20170721112725.45f5f580@lwn.net> In-Reply-To: <1500600655-7938-1-git-send-email-frowand.list@gmail.com> References: <1500600655-7938-1-git-send-email-frowand.list@gmail.com> Organization: LWN.net MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 601 Lines: 18 On Thu, 20 Jul 2017 18:30:55 -0700 frowand.list@gmail.com wrote: > Documentation/process/submitting-patches.rst contains a non-ascii > character. Change it to the ascii equivalent. You should know better than to tell somebody like me that a hyphen and an m-dash are equivalent! :) I don't have any real objection to this change, but I am curious: is the m-dash creating a problem somewhere? We have plenty of non-ASCII characters in Documentation/ and beyond, why change this one? Or to put it another way, do you think we should have an ASCII-only policy for documentation files? Thanks, jon