gnustandards-commit
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

gnustandards standards.texi


From: Richard M. Stallman
Subject: gnustandards standards.texi
Date: Fri, 9 Aug 2019 19:15:30 -0400 (EDT)

CVSROOT:        /sources/gnustandards
Module name:    gnustandards
Changes by:     Richard M. Stallman <rms>       19/08/09 19:15:30

Modified files:
        .              : standards.texi 

Log message:
        (GNU Manuals): It is good to refer to the free software philosophy.

CVSWeb URLs:
http://cvs.savannah.gnu.org/viewcvs/gnustandards/standards.texi?cvsroot=gnustandards&r1=1.261&r2=1.262

Patches:
Index: standards.texi
===================================================================
RCS file: /sources/gnustandards/gnustandards/standards.texi,v
retrieving revision 1.261
retrieving revision 1.262
diff -u -b -r1.261 -r1.262
--- standards.texi      9 Aug 2019 23:13:52 -0000       1.261
+++ standards.texi      9 Aug 2019 23:15:30 -0000       1.262
@@ -3323,8 +3323,8 @@
 different cultural reference points; many things that "everyone knows
 about" today may be mostly forgotten.
 
-For this reason, try to avoid writing in a way that crucially depends on
-cultural reference points for understanding, or that refers to them in
+For this reason, try to avoid writing in a way that depends on
+cultural reference points for proper understanding, or that refers to them in
 ways that would impede reading for someone that doesn't recognize them.
 
 Likewise, be conservative in your choice of words (aside from technical
@@ -3337,6 +3337,12 @@
 an aside.  Changing these few things (which in any case stand out) when
 they no longer make sense will not be a lot of work.
 
+By contrast, it is always proper to refer to concepts of GNU and the
+free software movement, when they are pertinent.  These are a central
+part of our message, so we should take advantage of opportunities to
+mention them.  They are fundamental moral positions, so they will
+rarely if ever change.
+
 Programmers tend to carry over the structure of the program as the
 structure for its documentation.  But this structure is not
 necessarily good for explaining how to use the program; it may be



reply via email to

[Prev in Thread] Current Thread [Next in Thread]