From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#20385: [PATCH] Support curved quotes in doc strings Date: Sat, 16 May 2015 00:48:00 +0300 Message-ID: <55566990.8020506@yandex.ru> References: <1429555155-4695-1-git-send-email-eggert@cs.ucla.edu> <5552FDAC.4080004@cs.ucla.edu> <55534080.6010400@yandex.ru> <555369FD.30701@cs.ucla.edu> <5553D12F.7000809@yandex.ru> <5554155E.70000@cs.ucla.edu> <55547DC6.3090509@yandex.ru> <5555A4ED.8090500@cs.ucla.edu> <55562BB0.2010605@yandex.ru> <555640E9.4060203@cs.ucla.edu> <55564460.4020208@yandex.ru> <55566196.40105@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1431726563 10603 80.91.229.3 (15 May 2015 21:49:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 15 May 2015 21:49:23 +0000 (UTC) To: Paul Eggert , 20385@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri May 15 23:49:12 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1YtNTj-00010K-04 for geb-bug-gnu-emacs@m.gmane.org; Fri, 15 May 2015 23:49:11 +0200 Original-Received: from localhost ([::1]:33060 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtNTi-0005Iu-CV for geb-bug-gnu-emacs@m.gmane.org; Fri, 15 May 2015 17:49:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39849) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtNTe-0005In-Bw for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 17:49:07 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YtNTb-0004vd-62 for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 17:49:06 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:36562) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YtNTb-0004vK-1C for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 17:49:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YtNTa-0001xB-H4 for bug-gnu-emacs@gnu.org; Fri, 15 May 2015 17:49:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 15 May 2015 21:49:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 20385 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 20385-submit@debbugs.gnu.org id=B20385.14317264937443 (code B ref 20385); Fri, 15 May 2015 21:49:02 +0000 Original-Received: (at 20385) by debbugs.gnu.org; 15 May 2015 21:48:13 +0000 Original-Received: from localhost ([127.0.0.1]:46537 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YtNSm-0001vy-0i for submit@debbugs.gnu.org; Fri, 15 May 2015 17:48:13 -0400 Original-Received: from mail-wg0-f44.google.com ([74.125.82.44]:36786) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YtNSk-0001vj-AV for 20385@debbugs.gnu.org; Fri, 15 May 2015 17:48:11 -0400 Original-Received: by wgbhc8 with SMTP id hc8so94599829wgb.3 for <20385@debbugs.gnu.org>; Fri, 15 May 2015 14:48:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=DEAYOhposCXISYlzSRpkNQ0P5ZGaq5ixt0L3PDm8Jqc=; b=FyMyDkW63Z9Hq44b9os8O59ex942JaitOrcm5MV43XaIDm5kzAZXACP2Yj94ey1W1U ad2yxOd+EADw+h8w+2Lbdo/WQV7VzlUFSwoSfbLbBQhlI3AS5x0FlUhMc811vBLIZ0fx cQDd2mLjf+v9of5Y5Q1XxG//5ZJ47gp40QbsqClkId2MAqjqmPnXQ4O+oIEPDA+zp/md /O6iL36l2UU2j5R0ePd7/yuTdjjqOkIQjWt8jlUha2tIxx9Nq/3GkLE6hjB8fLShbWHP UJcQpqELfNuWDz9gyr5qMQNx0swG3Z0loe08sjzGWDQ1JEkTjp8kawf0mf5nlNGi9jsN bfkw== X-Received: by 10.194.122.105 with SMTP id lr9mr22537643wjb.153.1431726484583; Fri, 15 May 2015 14:48:04 -0700 (PDT) Original-Received: from [192.168.1.2] ([82.102.93.54]) by mx.google.com with ESMTPSA id wv3sm4400428wjc.0.2015.05.15.14.48.03 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 May 2015 14:48:04 -0700 (PDT) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 In-Reply-To: <55566196.40105@cs.ucla.edu> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:102847 Archived-At: On 05/16/2015 12:13 AM, Paul Eggert wrote: > In contrast, if we use curved quotes in the source, cutting and pasting > will work naturally. It's true that here if the display doesn't support > curved quotes (the atypical case) then cutting and pasting may not work > -- but that's not a problem we need to worry about, since it's rare > nowadays particularly among developers. What if the locale mandates the use of some other kind of quotes? Then copying and pasting won't work anyway. In any case, I've never had a need to copy a diagnostic message with the intention to paste it into the source code. Web search or bug report? Sure, but never that. > That will all require explanation, indefinitely. And this won't be as > easy as one might think, particularly if opt-out is common. I've never noticed turning lambda into λ while rendering to be a significant problem among users, as long as copy and paste works. > I suppose it might work in some cases (killing and yanking within a > single GUI Emacs, say) but not in others (cutting from one Emacs running > remotely under gnome-terminal and pasting into another in a different > locale). The other cases are common enough that they will be a > continuing hassle. Again, if there are different locales involved, and you intend to honor their different quotings, copying and pasting won't work anyway. Actually, it's a decent argument against using *any particular locale's* quoting, in order not to confuse casual contributors, who'd have to know that *these* fancy quotes will be localized, but *those* - won't. > This sounds backwards. Even now, one can cut curved quotes from an Info > file and paste them into a .texi file and it will work, on a typical > system with proper UTF-8 support (and assuming the latest Emacs on the > master branch and Texinfo 5). Maybe you could paste quotes, but not any other kind of formatting. So nobody will be too surprised that you can't, in general, paste quotes too. > Sorry, I meant tildify-space. (I mixed up functions: > prettify-symbols-mode uses a different Unicode character, namely ≤.) Yes, it does - as a part of content, not markup. And you can notice that if we delimited docstrings with curly quotes instead of the straight quotation marks, tildify-space wouldn't have been able to use them exactly this way inside the docstring. > Had these uses been there 20 years or go, or even 10, we would > have had significant problems in practice; but nowadays, UTF-8 is not a > problem. I know of no serious markup language that utilizes unicode, even now. > I'm not so sure, given the cutting-and-pasting issues mentioned above. > But even if you're right there would still be a tradeoff: would we want > a trivial transition now to a complex and klunky approach long-term, or > a nontrivial transition now to a simple and intuitive approach > long-term? Let's strive for simplicity. Guess I don't see it as clunky. Using ASCII in markup and rendering in to something fancier later is fairly common approach. And the benefits are marginal either way. We have bigger difficulties (how to delimit code blocks in docstrings and comments, for instance), but here we are discussing changing something that has been working fine for years.