unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: 21472@debbugs.gnu.org
Subject: bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings
Date: Tue, 15 Sep 2015 16:48:28 -0700 (PDT)	[thread overview]
Message-ID: <d5cea045-91eb-4f41-b4d4-f34344ea21df@default> (raw)
In-Reply-To: <55F86E4D.5030505@cs.ucla.edu>

> > This sentence:
> >    On a decentralized version control system, push changes from the
> >    current branch to another location.
> >
> > where "push" was quoted, is now reads like incorrect English
> 
> Why?  It's idiomatic English to talk about pushing changes in a dVCS.
> See, for example,
> <http://docs.telerik.com/platform/appbuilder/version-control/third-party-
> vc/push-changes>,
> which says “You push changes from your local AppBuilder repository to your
> remote Git repository.”
> 
> >    The external border is normally not shown on fullboth and mazimized
> >    frames.
> >
> > Previously, "fullboth", which is not a word, was quoted to indicate
> > that it's not a real word.
> 
> As I understand it the section is intended to define “fullboth” as an
> invented English word, which is fine: the invented word should be defined
> with @dfn (which quotes the word in info files), and other uses of the
> word should appear unquoted just like any other word.  This is standard
> English style.  The manual should not quote every use of a neologism,
> as scare quotes are not a good style for a manual.
> 
> That being said, there were problems with the section: it did not use @dfn
> to define “fullboth”, and the paragraph defining “fullboth” was written
> awkwardly.
>   I just now installed a followup patch to fix that.  I added index
> entries while I was at it.
> 
> > Many places have a quoted text replaced by @dfn, although there's no
> > terminology here that we describe or index.
> 
> Examples?  I put in @dfn when I thought the text was defining a term.
> 
> Indexing is a separate axis.  If the text uses a term that should be
> indexed, the index entry should be created regardless of whether the
> text surrounds a term with @dfn or with ``...'' or with nothing at all.
> By and large my recent large patch worried about quoting, not about indexing.

I do not object if people want to discuss other occurrences of quoted
terms in the context of this bug thread, _provided_ this bug gets
addressed as reported: it is only about _these particular quoted terms_.

IOW, let us please not lose sight of _THIS_ bug in some larger
consideration of other quoted terms and phrases (which I did not
initiate, and in which I have not participated).





  reply	other threads:[~2015-09-15 23:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-13 15:45 bug#21472: 25.0.50; REGRESSION: (emacs) `Coding Systems' uses curly quotes for Lisp strings Drew Adams
2015-09-13 20:07 ` Eli Zaretskii
2015-09-13 21:11   ` Drew Adams
2015-09-14  6:24     ` Eli Zaretskii
2015-09-14 14:08 ` Richard Stallman
2015-09-15 15:57 ` Paul Eggert
2015-09-15 16:00   ` Eli Zaretskii
2015-09-15 16:22     ` Paul Eggert
2015-09-15 23:48       ` Drew Adams
2015-09-15 16:26   ` Eli Zaretskii
2015-09-15 19:15     ` Paul Eggert
2015-09-15 23:48       ` Drew Adams [this message]
2015-09-16  6:56       ` Eli Zaretskii
2015-09-16  7:32         ` Eli Zaretskii
2015-09-16  7:48         ` Paul Eggert
2015-09-16 10:02           ` Eli Zaretskii
2015-09-15 23:48     ` Drew Adams
2015-09-15 23:48   ` Drew Adams
2015-09-16  7:23     ` Eli Zaretskii
2015-09-16  7:49       ` Paul Eggert
2015-09-16 10:07         ` Eli Zaretskii
2015-09-16 15:31           ` Paul Eggert
2015-09-16 17:18             ` Eli Zaretskii
2015-09-16 18:27               ` Paul Eggert
2015-09-16 18:34                 ` Eli Zaretskii
2015-09-16 20:31                   ` Paul Eggert
2015-09-17  4:46                     ` Eli Zaretskii
2015-09-17  5:21                       ` Paul Eggert
2015-09-17  6:03                         ` Eli Zaretskii
2015-09-17  7:21                           ` Paul Eggert
2015-09-17  7:35                             ` Eli Zaretskii
     [not found]   ` <<831tdz8yf8.fsf@gnu.org>
2015-09-15 23:48     ` Drew Adams
     [not found] <<c7ebc07d-51c9-4d10-9238-d42b0b3845b7@default>
     [not found] ` <<83vbbe9j7k.fsf@gnu.org>
     [not found]   ` <<661f3a80-cdaf-47f0-a096-4be744409150@default>
     [not found]     ` <<83pp1la58d.fsf@gnu.org>
2015-09-14 13:51       ` Drew Adams
2015-09-15  0:21         ` Richard Stallman
     [not found] ` <<55F83FDF.2070202@cs.ucla.edu>
     [not found]   ` <<3aa1fafa-ed4d-4935-8a3e-cae7d0842c5f@default>
     [not found]     ` <<83r3ly7rpd.fsf@gnu.org>
2015-09-16 15:16       ` Drew Adams

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=d5cea045-91eb-4f41-b4d4-f34344ea21df@default \
    --to=drew.adams@oracle.com \
    --cc=21472@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@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).