all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: R. H. Allen <kkarie@REMOVEhotmail.com>
Subject: Re: Program structure of Pstricks, what is its basic structure?
Date: Mon, 23 Feb 2004 12:54:31 -0500	[thread overview]
Message-ID: <m7bk30hfgg6a5ubofr5ut7h8dv55jj7ids@4ax.com> (raw)
In-Reply-To: 42414174.0402221953.24c938a6@posting.google.com

On 22 Feb 2004 19:53:00 -0800, crashedandburnt1@hotmail.com
(Crashedandburnt) wrote:

>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.

I have a hard time believing he said that, considering that his last
update to PSTricks apparently came seven years ago and two other people
have been maintaining it since then.

>He said that he has not released
>documentation on the package and will not release the documentation on
>how it works.

Oh, but he has! One must be careful using it, though, as the current
maintainers have made some changes that supersede parts of van Zandt's
original documentation. There isn't documentation explaining why he uses
each and every Postscript command, but there is documentation for the
TeX commands that assemble the Postscript code. It includes enough
information that even a rudimentary Postscript programmer like me can
usually figure out what the code is doing.

>Unless there is real
>free software, with good documentation on its usage and implemenation,
>it is not free software, but a virus software.

I didn't pay a dime for my fully legal TeX installation and learned how
to use it entirely from free, online documentation sources. I later
chose to buy a book because it was more convenient than printing and
carrying a huge binder full of online documentation, and it was money
well spent. That's quite the opposite of my experience with a lot of GNU
software. Based on your definition, that would make GNU the virus
software from my perspective (though I don't really feel that way).
While I'm happy to hear that GNU is finally putting decent documentation
together, I certainly hope they will bind it and offer it for sale at my
local bookstore, even if they do end up making millions (doubtful).

>If a group of volunteers want to save TeX/LaTeX, what is needed is to

Is it just me, or in the past 6 months or so have there been an usual
number of people who aren't regular posters in comp.text.tex barging in
to explain how to "save" TeX/LaTeX?

alan

  parent reply	other threads:[~2004-02-23 17:54 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     ` Program structure of Pstricks, what is its basic structure? Crashedandburnt
2004-02-23 10:52       ` 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 [this message]
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=m7bk30hfgg6a5ubofr5ut7h8dv55jj7ids@4ax.com \
    --to=kkarie@removehotmail.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.