unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Alan Mackenzie <acm@muc.de>
Cc: 20707@debbugs.gnu.org
Subject: bug#20707: [PROPOSED PATCH] Use curved quoting in C-generated errors
Date: Tue, 09 Jun 2015 13:49:47 -0700	[thread overview]
Message-ID: <5577516B.9020709@cs.ucla.edu> (raw)
In-Reply-To: <20150609133423.GA3735@acm.fritz.box>

[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]

 >>> we don't control Info output
 >
 >> Actually, we do control it, and can easily tell makeinfo to output 
straight
 >> ASCII quotes.
 >
 > Can we?

I'm sure we can, though I'm too lazy to look it up right now.  And we 
can transliterate the .info files ourselves, though that would be just 
as silly.

 > The abstract principle at work here is that ASCII quotes are
 > @dfn{working} characters, whereas the curly quotes are merely
 > @dfn{display} characters.

Curved single quotes are also "working" characters, both in Emacs 
(master branch) and in Texinfo (latest stable version).  It's true that 
not every keyboard can generate them in every Emacs context with just a 
single keypress, but that's also true for many ASCII characters.  In 
practice the data entry problem is not that big a deal.

 > I meant change the appearance of your 0x27 apostrophe

It's not my apostrophe.  It's the appearance of U+0027 APOSTROPHE in 
most environments nowadays.  You may not like its appearance, and I may 
not like it either, but it's a waste of our time to reargue this now.  
The appearance has been common practice for many years, and Emacs should 
work well out of the box in common and standard environments.

 > Yes, the single curly quotes are "hard linked" to the ASCII single
 > quotes in the font.  That isn't acceptable for me - they should have
 > distinct glyphs if they're going to be there at all.

That's easy enough.  Just take lat1-16.psfu and run this shell script:

   (psfgettable lat1-16.psfu
    echo '0x0c3 U+2018'
    echo '0x0c9 U+2019'
    echo '0x0d3 U+201C'
    echo '0x0d9 U+201D') |
   psfaddtable lat1-16.psfu - lat1cq-16.psfu
   gzip -9n lat1cq-16.psfu

I'll attach the resulting font file, so you can save it and run 
'setfont' on it.  This font provides easy-to-distinguish glyphs for 
curved quotes (both single and double), and it retains the appearance of 
all ASCII characters in the font you've expressed a preference for.  
Most users won't need this sort of thing of course -- I'm just trying to 
help create a font that meets your specific needs.

 > So, it's going to be a pain in the posterior for most, if not all, users
 > of Emacs on terminals,

No, it works fine for users of Emacs on terminals in most environments 
(gnome-terminal, xterm, etc.).  It works fine even on most Linux 
consoles, where curved single quotes display as curved single quotes out 
of the box.  Ordinary users shouldn't have to fiddle with font files; 
things just work.

[-- Attachment #2: lat1cq-16.psfu.gz --]
[-- Type: application/gzip, Size: 2085 bytes --]

  reply	other threads:[~2015-06-09 20:49 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-01  7:39 bug#20707: [PROPOSED PATCH] Use curved quoting in C-generated errors Paul Eggert
     [not found] ` <mailman.4052.1433144480.904.bug-gnu-emacs@gnu.org>
2015-06-01 10:49   ` Alan Mackenzie
2015-06-01 16:01     ` Paul Eggert
2015-06-01 17:17       ` Alan Mackenzie
2015-06-01 18:50         ` Paul Eggert
2015-06-02 11:56           ` Alan Mackenzie
2015-06-02 13:25             ` Drew Adams
2015-06-02 15:39             ` Paul Eggert
2015-06-02 15:51               ` Dmitry Gutov
2015-06-02 20:05                 ` Paul Eggert
2015-06-02 17:07               ` Alan Mackenzie
2015-06-02 20:44                 ` Alan Mackenzie
2015-06-04 15:43                   ` Paul Eggert
2015-06-06 15:54                     ` Alan Mackenzie
2015-06-06 18:11                       ` Paul Eggert
2015-06-06 20:50                         ` Alan Mackenzie
2015-06-07  0:09                           ` Paul Eggert
2015-06-08 17:18                             ` Alan Mackenzie
2015-06-09  6:53                               ` Paul Eggert
2015-06-09 13:34                                 ` Alan Mackenzie
2015-06-09 20:49                                   ` Paul Eggert [this message]
2015-06-09 22:46                                     ` Alan Mackenzie
2015-06-09 23:42                                       ` Paul Eggert
2015-06-10 13:39                                         ` Alan Mackenzie
2015-06-10 16:20                                           ` Paul Eggert
2015-06-10 17:39                                             ` Dmitry Gutov
2015-06-10 19:42                                               ` Paul Eggert
2015-06-10 19:17                                             ` Alan Mackenzie
2015-06-10 19:44                                               ` Paul Eggert
2015-06-11 19:06                                                 ` Alan Mackenzie
2015-06-12  2:41                                                   ` Paul Eggert
2015-06-12 11:25                                                     ` Alan Mackenzie
2015-06-12 23:46                                                       ` Paul Eggert
2015-06-13 11:54                                                         ` Alan Mackenzie
2015-06-13 17:54                                                           ` Paul Eggert
2015-06-07 13:17                       ` Wolfgang Jenkner
2015-06-09 16:58                         ` Alan Mackenzie
2015-06-02 23:26                 ` Paul Eggert
2015-06-01 14:34 ` Eli Zaretskii
2015-06-01 16:48   ` Glenn Morris
2015-06-01 17:55   ` Paul Eggert
2015-06-01 18:29     ` Eli Zaretskii
2015-06-01 21:13     ` Stefan Monnier
2015-06-09 19:44 ` Wolfgang Jenkner
2015-06-11 13:06 ` bug#20707: " Andy Moreton
2020-08-12 13:02 ` bug#20707: [PROPOSED PATCH] " Lars Ingebrigtsen

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=5577516B.9020709@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=20707@debbugs.gnu.org \
    --cc=acm@muc.de \
    /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).