🚀 go-pugleaf

Fellow users:

     I agree with Dave Valentine <dwv@MAGIC.UCSB.EDU> that styles
should be uploaded as individual files.  I also think that we
could use file extensions to distinguish between mac and pc
versions, rather than making two directory trees for the two
platforms, especially if the two versions are the same.  I
suggest that for maximum flexibility of downloading, we store the
style files as printable characters.  (This is in spite of the
fact that the first few styles that I uploaded were binaries :-).
For PC files this is probably best implemented using the
utilities UUENCODE and UUDECODE.  I can upload a file containing
instructions and including a version of UUDECODE.COM that is
composed entirely of printable characters.  If space is limited
on magic, we could UUENCODE zipped files of our styles before
uploading.  If Dave is willing to convert mac versions to pc and
vica versa, it would save a lot of effort and allow both
communities to share the fruits of each other's efforts.  How
about it, Dave?  Will you have time to do this when finals are
over?

     Uploading files in UUCODE format will allow us to identify
the author and how to get in touch with him/her if we have
questions.  Jean-Michel Lacroix made some suggestions for what to
include in this section.  If it's all in one file, it will be
easier than having separate readme and style files to keep track
of.  The beauty of storing the styles as printable characters is
that we can add descriptions as a header that will get stripped
off when the file is decoded.  I also vote for calling PC files
filename.uu (or .uue) as a way to distinguish them from mac
files.

     If there's interest, I'll upload the starter kit that
includes the ASCII UUDECODE.COM.

Gary Rudnick