all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Paul Eggert <eggert@cs.ucla.edu>, emacs-devel@gnu.org
Subject: RE: How to opt out of curly-quote spamming altogether?
Date: Mon, 24 Aug 2015 10:06:35 -0700 (PDT)	[thread overview]
Message-ID: <8ef60519-6660-4743-9c82-1442ca039a5a@default> (raw)
In-Reply-To: <55DB3788.5060505@cs.ucla.edu>

> > that option has no effect on the quotation style used in the
> > manuals.
> 
> Correct.  Display of info files is unaffected by the changes in
> Emacs master over the past month or two.  Info files use curved
> quotes as of Emacs 24.5, due to a 2013 change in Texinfo, not in Emacs.

Not good.  Users should have control over this, or the previous
behavior should be restored.

It makes no sense for Emacs to impose curly quoting for inline code
fragments.  That doesn't make much sense for other programming
contexts either.  Why should Texinfo make such decisions about the
doc for a particular product such as Emacs?  This is truly a step
backward.

Wrt the argument that a 2013 Texinfo change forces Emacs's hand:
I have Emacs builds that are much more recent than 2013, and which
do not exhibit this breakage.  Sounds to me like a cop-out, to
blame this only on a Texinfo change.

Hard to believe that Texinfo/makeinfo does not give builders any
choice about the resulting characters.  And Eli seems to make clear
that Emacs _can_ still be built without curly quotes, "telling
makeinfo not to produce Unicode characters there".

If nothing else works, the doc should be built both ways, and users
should be allowed to choose which presentation to use.




  reply	other threads:[~2015-08-24 17:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24  4:16 How to opt out of curly-quote spamming altogether? Drew Adams
2015-08-24 15:22 ` Eli Zaretskii
2015-08-24 15:26 ` Paul Eggert
2015-08-24 17:06   ` Drew Adams [this message]
     [not found] <<a4c77735-a9de-400e-88f2-243c66e24836@default>
     [not found] ` <<83fv38hfsx.fsf@gnu.org>
2015-08-24 16:34   ` Drew Adams
2015-08-24 16:45     ` Eli Zaretskii
2015-08-24 17:09     ` Paul Eggert
2015-08-24 17:29       ` Drew Adams
2015-08-24 18:44         ` Paul Eggert
     [not found]   ` <<c8408881-dddb-4661-9e7f-6ec42d9bf5fa@default>
     [not found]     ` <<837fokhby1.fsf@gnu.org>
2015-08-24 17:06       ` Drew Adams
2015-08-24 17:25         ` Eli Zaretskii
     [not found] <<c1f42565-e538-49e6-b246-07e43dab673a@default>
     [not found] ` <<834mjoha4r.fsf@gnu.org>
2015-08-24 17:57   ` Drew Adams
2015-08-24 18:05     ` Eli Zaretskii
2015-08-24 18:36     ` David Kastrup
2015-08-24 21:44       ` Drew Adams
2015-08-25  4:25         ` David Kastrup

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

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

  git send-email \
    --in-reply-to=8ef60519-6660-4743-9c82-1442ca039a5a@default \
    --to=drew.adams@oracle.com \
    --cc=eggert@cs.ucla.edu \
    --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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.