all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: crashedandburnt1@hotmail.com (Crashedandburnt)
Subject: Re: Program structure of Pstricks, what is its basic structure?
Date: 22 Feb 2004 19:53:00 -0800	[thread overview]
Message-ID: <42414174.0402221953.24c938a6@posting.google.com> (raw)
In-Reply-To: c1a78u$6bm$01$1@news.t-online.com

Herbert Voss <Herbert.Voss@gmx.net> wrote in message news:<c1a78u$6bm$01

> The problem is, that there is no documentation about this
> low level structure.

I am sorry to report a telephone conversation that I had some years
ago with
the author of this package. I vaguely remember his exact name, Timothy
van zandt or sth like that. But what I clearly remember is that he was
some kind of
economist and wrote this package to write his book(s). He said that
Leslie Lamport has made millions from his LaTeXbook and he expects
[big] money for his package. He said that he has not released
documentation on the package and will not release the documentation on
how it works. I asked how he knew LL had made million? He said, just
look at the printings, it has over a million. Assuming LL gets a
dollar for the royalty, he has made a million bucks.

The conclusion I want to present to the readership is the following.
Only Richard Stallman, and Linus Trovalds are the true gnu/free
software people.
Gnu is coming with good books and manuals on the software.

But Donald Knuth and others are all using free software slogan for
their virus software. The Texbook is not available free, LEGALLY. It
cannot be re-formed. Knuth has made millions off his books. Omega and
Lout are emerging as strong competitors to TeX. Unless there is real
free software, with good documentation on its usage and implemenation,
it is not free software, but a virus software.

If a group of volunteers want to save TeX/LaTeX, what is needed is to
combine
existing free manuals into a single good and comprehensive free
manual. I can assure you, if it is free, tons of people will
contribute to it, and Knuth+Lamport+Timothy's books and manuals will
be obsolete overnight. What we need is a trust worthy coordinator like
Mr Richard Stallman.

Knuth's book is scrap. It is convoluted by malice or twist of his
mind. It mixes advanced usage with basics. For contrast, compare, for
example, the Adobe cookbook or thinking in postscript. I pick
postscript because it is as extensive as TeX in its functions. CB has
a very nicely organized glossary. Knuth wrote his book to impress his
colleagues so that he can get an early retirement from Stanford by
dominating his colleagues. This is exactly what the abuse of software
to control the world is, and what Richard Stallman is crusading
against. Gnu is now active in the next phase of its mission which is
quality documentation. But since TeX is not FSF software, they are not
likely to focus on it. Someone active in this group is gonna have to
do that.

crashed and burnt

       reply	other threads:[~2004-02-23  3:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <m3n07dv5xj.fsf@pdrechsler.fqdn.th-h.de>
     [not found] ` <QY8DY60K38039.536875@Gilgamesh-Frog.org>
     [not found]   ` <c1a78u$6bm$01$1@news.t-online.com>
2004-02-23  3:53     ` Crashedandburnt [this message]
2004-02-23 10:52       ` Program structure of Pstricks, what is its basic structure? Giuseppe Bilotta
2004-02-24  0:36         ` Crashedandburnt
2004-02-23 14:18       ` Tim McNamara
2004-02-23 14:52       ` Timothy Van Zandt
2004-02-24  0:04         ` Crashedandburnt
2004-02-24  3:10           ` Tim McNamara
2004-02-24  7:49             ` Brooks Moses
2004-02-24  8:15             ` Crashedandburnt
2004-02-24  8:39               ` David Kastrup
2004-02-24 16:28                 ` R. H. Allen
2004-02-24  3:21           ` David Kastrup
2004-02-24  8:51             ` Crashedandburnt
2004-02-24  9:20               ` David Kastrup
2004-02-24 19:18               ` Tim McNamara
2004-02-24 15:08           ` Paul Thompson
2004-02-23 15:49       ` Timothy Van Zandt
2004-02-23 17:34         ` Donald Arseneau
2004-02-23 17:54       ` R. H. Allen
2004-02-24 15:23       ` Cameron Laird

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=42414174.0402221953.24c938a6@posting.google.com \
    --to=crashedandburnt1@hotmail.com \
    /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.