unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation
Date: Mon, 14 Mar 2016 11:24:55 -0700	[thread overview]
Message-ID: <56E701F7.6060101@cs.ucla.edu> (raw)
In-Reply-To: <83shztc7qg.fsf@gnu.org>

On 03/14/2016 10:03 AM, Eli Zaretskii wrote:
> Are we sure NEWS will always be read either in Emacs or on a terminal
> that supports these characters?  I frequently look at it with Less,
> but maybe I'm alone.

I use Less a lot too, and it works fine (Fedora 23). These days the 
problem with non-ASCII characters typically isn't the Less program, it's 
the terminal or operating system being misconfigured for UTF-8, or not 
supporting UTF-8. This problem is not limited to etc/NEWS of course; it 
occurs with all the UTF-8 source files. The question is whether etc/NEWS 
is enough of a special case that we should keep it in ASCII despite the 
rest of Emacs moving to UTF-8.



  reply	other threads:[~2016-03-14 18:24 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160314154123.2684.74715@vcs.savannah.gnu.org>
     [not found] ` <E1afUcV-0000iS-4N@vcs.savannah.gnu.org>
2016-03-14 15:44   ` [Emacs-diffs] emacs-25 26b56dc: Fix some single quotes in documentation John Wiegley
2016-03-14 16:31     ` Paul Eggert
2016-03-14 16:39       ` John Wiegley
2016-03-14 16:42         ` Dmitry Gutov
2016-03-14 17:19           ` Clément Pit--Claudel
2016-03-14 17:37             ` Dmitry Gutov
2016-03-14 17:53               ` Kaushal Modi
2016-03-14 18:10                 ` Drew Adams
2016-03-14 18:32           ` Paul Eggert
2016-03-14 18:43             ` Eli Zaretskii
2016-03-14 18:48               ` John Wiegley
2016-03-14 18:58                 ` Eli Zaretskii
2016-03-14 18:45             ` John Wiegley
2016-03-14 19:14               ` Paul Eggert
2016-03-14 19:29                 ` John Wiegley
2016-03-14 20:47                   ` Paul Eggert
2016-03-14 20:50                     ` John Wiegley
2016-03-15  0:30                       ` Paul Eggert
2016-03-15 22:21                         ` John Wiegley
2016-03-15 23:13                         ` Lars Magne Ingebrigtsen
2016-03-15 23:56                           ` Drew Adams
2016-03-16  0:11                           ` Paul Eggert
2016-03-16  0:52                             ` Drew Adams
2016-03-16  8:16                               ` John Wiegley
2016-03-16 17:55                               ` Paul Eggert
2016-03-16 21:26                                 ` Drew Adams
2016-03-16 23:37                                   ` Paul Eggert
2016-03-16 23:41                                     ` Drew Adams
2016-03-14 20:56                     ` Alan Mackenzie
2016-03-15  0:39                       ` Paul Eggert
2016-03-14 18:50             ` Kaushal Modi
2016-03-14 19:11             ` Dmitry Gutov
2016-03-14 19:16             ` Drew Adams
2016-03-14 19:39               ` John Wiegley
2016-03-14 19:47                 ` Dmitry Gutov
2016-03-14 17:03       ` Eli Zaretskii
2016-03-14 18:24         ` Paul Eggert [this message]
2016-03-14 18:42           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56E701F7.6060101@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).