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: Sat, 06 Jun 2015 17:09:13 -0700 [thread overview]
Message-ID: <55738BA9.7050104@cs.ucla.edu> (raw)
In-Reply-To: <20150606205023.GA3862@acm.fritz.box>
[-- Attachment #1: Type: text/plain, Size: 2541 bytes --]
Alan Mackenzie wrote:
> Up till now, all messages output have been ASCII (with the exception of user
> supplied characters and in some other rare instances such as outputting
> `sentence-end').
No, even the current stable version of Emacs (24.4) regularly outputs curved
quotes on typical displays. I just now ran emacs -Q, typed "C-h i m emacs RET",
and saw curved quotes on the first screenful of the Emacs manual. So we're not
making such a drastic change here; we're just evolving Emacs in the natural
direction.
> does the code test the output
> display setup to decide what sort of quotes to output (best), or is it up
> to some user option (middling) or is it hard coded (worst)?
It tests the output display setup.
>> This is not too much to ask of an Emacs developer.
>
> Of course not, but could it be too much to ask of an Emacs user?
Emacs users in 8-bit environments shouldn't need to worry about this; they
should just see straight quotes where the Emacs manual etc. uses curved ones.
This thread is more about the special case of a developer who's using a Linux
console that doesn't support the full Unicode gamut.
> this warrants an extensive entry in NEWS.
Makes sense, and the next iteration of this patch will add a NEWS entry.
> I don't think that's the font for me. It has one-pixel thick spidery
> characters, rather than the two-pixel thick ones the default fonts have.
The font has a bold variant. I'll attach Lat15-TerminusBold16.psf.gz. There
are other variants that are even bigger, if you like.
> ... Its apostrophe is a vertical line rather than a top right to bottom left
> sloping character, and I find its curly single quotes too indistinct
If you just want to continue to use the same font, how about the attached font
lat1-16.psfu.gz instead? It's taken from the current stable version of kbd
<http://kbd-project.org/>; see
<http://kbd-project.org/download/kbd-2.0.2.tar.xz> and extract the file
kbd-2.0.2/data/consolefonts/lat1-16.psfu and then use gzip to get the compressed
version. This handles curved single quotes and if it's the same lat1-16 font
you're used to you should find it comfortable. Curved double quotes don't come
up as often, but if you want them to be displayed using a graphical
representation other than '"', you can do something like the following:
(printf '0x0d3 U+201C\n0x0d9 U+201D\n'; psfgettable lat1-16.psfu) |
psfaddtable lat1-16.psfu - lat1-16-double.psfu
gzip -9n lat1-16-double.psfu
and then use the font lat1-16-double.psfu.gz instead.
[-- Attachment #2: Lat15-TerminusBold16.psf.gz --]
[-- Type: application/gzip, Size: 2383 bytes --]
[-- Attachment #3: lat1-16.psfu.gz --]
[-- Type: application/gzip, Size: 2076 bytes --]
next prev parent reply other threads:[~2015-06-07 0:09 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 [this message]
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
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=55738BA9.7050104@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).