C Y <[EMAIL PROTECTED]> wrote:

> The ANSI draft specification dpANS2 and it's unofficial revision dpANS3
> have essentially been the bible for free Lisp implementations since
> Common Lisp became an ANSI spec - they contain virtually all the
> material present in the actual ANSI spec and are freely available
> (although the tex style is apparently rather old - not surprising given
> it was written in the early 1990s.)  It is available from here:
> ftp://parcftp.xerox.com/pub/cl/

Actually, my suggestion is a bit subversive, but we can do it like
LAME. LAME was distributed as a set of patches for the original
Frauenhofer patented MP3 encoding procedure. Apply patch to patent
application source -> voila mp3 encoder.

You can take the tex sources and provide patches against this tex
sources. The reader takes both pieces as input and gets an updated ANSI
spec as output. Of course, we have to carefully construct the patches,
so a simple diff -u foo bar isn't going to do it, as we are not allowed to
redistribute sniplets of the original text. diff does by default, but it
would be trivial to construct a variation of diff/patch that works
solely with line numbers. If that's not enough you can use a levenshtein
generated edit sequence -- I think that's what diff does anyway -- but
not on line basis but on character basis. Then, a correction of a typo would
not lead to an almost identical input line in the diff output.

However, this can only be an intermediate solution for small
clarifications and small fixes in the ANSI spec. Every reader would have
to produce the spec for himself. You would not be allowed to distribute
it as nice printable PDF. This can be remedied with trivial
scripting. Several website tried to make it extra comfortable for the
user and promote stuff like this "wget -q -O - http://go.ximian.com |
sh" [1]. I'm not a fan of this, but moving the assembling of the spec to
the users realm isn't a real problem.

Hence, it _is_ possible to shell out this copyright issue with a bit of
technological tricks. But when I think about it, this is actually ok, as
the patches we are writting will be our intellectual fruits. Still, I
think this is only useful for small changes, let's say 1% of the
original text.

Regards,
-- 
Fruhwirth Clemens - http://clemens.endorphin.org 
for robots: [EMAIL PROTECTED]

_______________________________________________
Gardeners mailing list
[email protected]
http://www.lispniks.com/mailman/listinfo/gardeners

Reply via email to