groff-commit
[Top][All Lists]
Advanced

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

[groff] 08/40: doc/groff.texi: Drop some material.


From: G. Branden Robinson
Subject: [groff] 08/40: doc/groff.texi: Drop some material.
Date: Sat, 12 Nov 2022 14:43:35 -0500 (EST)

gbranden pushed a commit to branch master
in repository groff.

commit f3d5c1bc3bb33a36b99a2cda2f04a86eff3f5fb3
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
AuthorDate: Sun Nov 6 09:45:20 2022 -0600

    doc/groff.texi: Drop some material.
    
    There's a lengthy jeremiad here that (1) characterizes groff as a bit
    old-fashioned (not the likeliest selling point) and (2) rails against
    the fashionability of WYSIWYG apps.  While this may have been timely in
    1999, it's pretty dated now.  According to the Google Books Ngram
    Viewer, as of 2019 the occurrence of this term had fallen by about 80%
    from its 1990-1993 peak, and returned to a level last seen in 1983.
    
    So just get rid of it.
---
 doc/groff.texi | 41 -----------------------------------------
 1 file changed, 41 deletions(-)

diff --git a/doc/groff.texi b/doc/groff.texi
index b41cc466a..62e420482 100644
--- a/doc/groff.texi
+++ b/doc/groff.texi
@@ -607,47 +607,6 @@ resources.
 @c END Keep parallel with groff(1), section "Description" (after the
 @c first sentence).
 
-@code{groff} belongs to an older generation of document preparation
-systems, which operate more like compilers than the more recent
-interactive @acronym{WYSIWYG}@footnote{What You See Is What You Get}
-systems.  @code{groff} and its contemporary counterpart, @TeX{}, both
-work using a @dfn{batch} paradigm: The input (or @dfn{source}) files are
-normal text files with embedded formatting commands.  These files can
-then be processed by @code{groff} to produce a typeset document on a
-variety of devices.
-
-@code{groff} should not be confused with a @dfn{word processor}, an
-integrated system of editor and text formatter.  Also, many word
-processors follow the @acronym{WYSIWYG} paradigm discussed earlier.
-
-Although @acronym{WYSIWYG} systems may be easier to use, they have a
-number of disadvantages compared to @code{troff}:
-
-@itemize @bullet
-@item
-They must be used on a graphics display to work on a document.
-
-@item
-Most of the @acronym{WYSIWYG} systems are either non-free or are not
-very portable.
-
-@item
-@code{troff} is firmly entrenched in all Unix systems.
-
-@item
-It is difficult to have a wide range of capabilities within the confines
-of a GUI/window system.
-
-@item
-It is more difficult to make global changes to a document.
-@end itemize
-
-@quotation
-``GUIs normally make it simple to accomplish simple actions and
-impossible to accomplish complex actions.''  --Doug Gwyn (22/Jun/91 in
-@code{comp.unix.wizards})
-@end quotation
-
 
 @c =====================================================================
 



reply via email to

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