[comp.sys.next] Abode's file server has some new NeXT specific documents

izumi@violet.berkeley.edu (Izumi Ohzawa) (03/26/90)

Since I haven't seen this info in this news group, I am posting this.
I hope Adobe doesn't mind me doing this.

Adobe now has 4 or 5 documents that may be of interest to you, from
their "ps-file-server@adobe.com".
These files may be obtained by placing a command,

send Documents filename

in the Subject: line or as body message.

Read the notes about file sizes carefully before sending mail(s).

I wonder if Adobe has any objection to having these files uploaded
to  NeXT archives for anon. FTP.

Izumi Ohzawa, izumi@violet.berkeley.edu

---------------------------------------------------------------------
[ Excerpts from message returned by ps-file-server@adobe.com 
in response to command "send index Documents". ]

>From: Adobe PostScript File Server <ps-file-server@adobe.com>

REALLY IMPORTANT: Some of these document files are larger than 100k.  
Most (if not all) USENET mail transport systems will bounce this mail 
back to the server as being too large.  PLEASE, if you need a copy of
struct.ps or PPDformat.ps or one of the large files, either ask for the
.ps.Zba version (which has been run through "compress" and "btoa" to
make it smaller) or send SEPARATE REQUESTS, one for each of the pieces
of the file you need (for example, struct1.ps and struct2.ps).  If you
just ask it to "send struct.ps", it will probably just waste time,
because it cannot be delivered.  Similarly, DON'T request struct1.ps 
and struct2.ps in the SAME message.  The server will try to cram the
reply into one message, too, and then you're back to the same file size
limitation problem.  [The server is not smart enough to break many 
requests from one message into several reply messages. Sorry.]

***YOU need to be aware of the amount of data you are asking for, and
break those requests across multiple mail messsages, if needed.
That is why you will see many similar files for the same document--
because it is a big one.  Thanks.

<foo>.ps    This is the PostScript language file for document <foo>. 
            This file can be sent directly to the printer.
<foo>#.ps   This is the original <foo>.ps file broken down into mutiple
            pieces. When concatenated together, all of the <foo>#.ps
            files will produce the original <foo>.ps file that can be
            sent directly to a printer.
<foo>.ps.Zba This is the original <foo>.ps file that was run through the 
            UNIX(TM) utilities "compress" and "btoa". Don't retrieve
            these files unless you have "atob" and "compress".
<foo>.ps.Zuu This is the original <foo>.ps file that was run through the
            UNIX(TM) utilities "compress" and "uuencode". Don't retrieve
            these files unless you have "uudecode" and "compress".
<bar>.txt   This is just an ASCII file.
<bar>.info  This is just an ASCII file.	

**DO NOT use asterisks (i.e. wild cards) when requesting files.

NOTE: The DPS* documents are *huge*. You can also obtain a hardcopy in a
nice binder at a small cost (for postage & binder) by calling the
Developer Support line at (415) 961-4111.

NX_Dial.ps               132440 Mar  9 18:51
NX_Dial.ps.Zba            83043 Mar 12 15:49
NX_Dial.ps.Zuu            90339 Mar 12 15:56
NX_Dial1.ps               71274 Mar 12 15:50
NX_Dial2.ps               61166 Mar 12 15:50
	This document is the fifth in a series of technical notes that
	cover issues about programming for the Display PostScript system
	on a NeXT machine. This document discusses issues related to 
	efficient path construction and rendering, including the use of
	user paths.
	You can retrieve a large PostScript language file, the same file
	broken into 2 pieces, a compressed/btoa version, or a 
	compressed/uuencoded version. 

NX_Hello.ps              137593 Mar 12 15:25
NX_Hello.ps.Zba           89220 Mar 12 15:55
NX_Hello.ps.Zuu           97056 Mar 12 15:57
NX_Hello1.ps              67481 Mar 12 15:58
NX_Hello2.ps              70112 Mar 12 15:59
	This document is the second in a series of technical notes that
	cover issues about programming for the Display PostScript system
	on a NeXT machine. This document briefly discusses the use of 
	the NeXT Interface Builder application.
	You can retrieve a large PostScript language file, the same file
	broken into 2 pieces, a compressed/btoa version, or a 
	compressed/uuencoded version. 

NX_Lines.ps              285422 Mar  9 19:25
NX_Lines.ps.Zba          179257 Mar 12 15:55
NX_Lines.ps.Zuu          195046 Mar 20 11:11
NX_Lines1.ps              75018 Mar 12 16:00
NX_Lines2.ps              75776 Mar 12 16:01
NX_Lines3.ps              75292 Mar 12 16:03
NX_Lines4.ps              59336 Mar 12 16:03
	This document is the third in a series of technical notes that
	cover issues about programming for the Display PostScript system
	on a NeXT machine. This document discusses the use of wraps versus
	single operator calls.
	You can retrieve a large PostScript language file, the same file
	broken into 4 pieces, a compressed/btoa version, or a 
	compressed/uuencoded version. 

NX_Overview.ps            79393 Mar  9 19:14
NX_Overview.ps.Zba        47770 Mar 12 16:04
NX_Overview.ps.Zuu        51957 Mar 12 15:57
	This document is the first is a series of technical notes
	that cover issues about programming for the Display PostScript
	system on a NeXT machine. While these documents contain code 
	examples that specifically target the NeXT machine, some of the
	information is useful for programming on any platform that uses
	the Display PostScript system. 
	You can retrieve a PostScript language file, a compressed/btoa
	version of the file, or a compressed/uuencoded version. 

NX_StrAdj.ps             100276 Mar  9 19:19
NX_StrAdj.ps.Zba          59402 Mar 12 15:56
NX_StrAdj.ps.Zuu          64611 Mar 12 15:57
NX_StrAdj1.ps             52042 Mar 12 16:05
NX_StrAdj2.ps             48234 Mar 12 16:05
	This document is the fourth in a series of technical notes that
	cover issues about programming for the Display PostScript system
	on a NeXT machine. This document discusses the automatic stroke
	adjustment feature that is present in Display PostScript systems.
	You can retrieve a large PostScript language file, the same file
	broken into 2 pieces, a compressed/btoa version, or a 
	compressed/uuencoded version.