unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40011@debbugs.gnu.org, rms@gnu.org
Subject: bug#40011: Remove unnecessary abbreviations from documentation
Date: Mon, 27 Apr 2020 08:05:34 +0200	[thread overview]
Message-ID: <878siha2fl.fsf@stefankangas.se> (raw)
In-Reply-To: <83v9nc9sdk.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 10 Mar 2020 16:49:59 +0200")

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

Eli Zaretskii <eliz@gnu.org> writes:

>> Please consider removing the following acronyms from the
>> documentation, both the manual(s) and doc strings:
>> 
>> 1. no. ("number")
>> 2. e.g. ("for example")
>> 3. i.e. ("that is", "namely", etc.)
>> 4. c.f. ("in contrast to", "compared with", etc.)
>> 5. w.r.t. ("with respect to")
>
> Let's not be too extreme: I'm against removing "e.g." and "i.e." at
> the least.

There are many such instances to get right, so maybe we can find a way
forward which avoids changing all of them.

How about adding something along the lines of the attached patch, and
leave it at that?  Would that be acceptable?

Best regards,
Stefan Kangas


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Recommend-avoiding-unnecessary-abbreviations-in-doc.patch --]
[-- Type: text/x-diff, Size: 1144 bytes --]

From a44c03f6a2b2b98b34b4c7836e3291fd2c458190 Mon Sep 17 00:00:00 2001
From: Stefan Kangas <stefankangas@gmail.com>
Date: Mon, 27 Apr 2020 07:53:10 +0200
Subject: [PATCH] Recommend avoiding unnecessary abbreviations in doc

* doc/lispref/tips.texi (Documentation Tips): Recommend avoiding
unnecessary abbreviations.  (Bug#40011)a
---
 doc/lispref/tips.texi | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index 3b8da35b6c..382e6d7c61 100644
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -820,6 +820,12 @@ Documentation Tips
 most cases, the meaning is clear with just ``if''.  Otherwise, try to
 find an alternate phrasing that conveys the meaning.
 
+@item
+Avoid abbreviations like ``e.g.'' (for ``for example''), ``i.e.'' (for
+``that is''), ``no.'' (for ``number''), ``c.f.'' (for ``in contrast
+to'') and ``w.r.t.'' (for ``with respect to'').  It is almost always
+both more clear and easier to read the expanded version.
+
 @item
 When a command is meaningful only in a certain mode or situation,
 do mention that in the documentation string.  For example,
-- 
2.26.2


  reply	other threads:[~2020-04-27  6:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10 13:54 bug#40011: Remove unnecessary abbreviations from documentation Stefan Kangas
2020-03-10 14:49 ` Eli Zaretskii
2020-04-27  6:05   ` Stefan Kangas [this message]
2020-04-27 14:39     ` Eli Zaretskii
2020-04-27 17:08       ` Stefan Kangas
2020-04-27 18:30         ` Eli Zaretskii
2020-04-30 16:05           ` Stefan Kangas
2020-04-28  2:46       ` Richard Stallman
2020-04-27 16:08     ` Drew Adams
2020-04-27 16:21       ` Stefan Kangas
2020-04-27 16:41         ` Drew Adams
2020-04-28  2:49     ` Richard Stallman

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=878siha2fl.fsf@stefankangas.se \
    --to=stefan@marxist.se \
    --cc=40011@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=rms@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).