Conference 7.286::digital

	He's in ELF (CLT::WHITESIDE). Why don't you ask him?

			Alfred

>	He's in ELF (CLT::WHITESIDE). Why don't you ask him?

Just be careful if you ask him by EMAIL,

:)

-steve-

I have used DELIVER to do that, and more.

Pete

    I just rely on saying "take me off that distribution list".
    
    Works wonderfully.   Real low CPU overhead too.

The Office Systems and Application Advanced Development Group is now
announcing network availability of the OFFICE FILTER Prototype Version 3.2. 
Your are being sent this letter because you have expressed an interest in 
this prototype to either Geoff Bock, Jim Miller, or myself, or because you 
installed a previous version of the prototype.

OFFICE FILTER Version 3.2 has been focused to greatly improve the usability
of the filtration features. Specifically, OFFICE FILTER Version 3.2 offers the
following important improvements:

      * Massively improved performance, particularly for the VMS MAIL version.
	A revised Information Interface gives VMS MAIL users much faster
	filtration execution, particularly for folders with more than
	a few messages in them. Performance improvements range from %50
	for a folder of 10 messages to over %90 for a folder of 100
	messages. Performance improvements abound in ULTRIX too.

      * Greatly improved ULTRIX support including: no renumbering of messages
	within folders, filtration of standard input for use in pipes or in
	the .forward file for filtration upon delivery, a spool file interface,
	a Distribute To: Then Action, and a greatly reduced executable size for 
	command line filtering.
	
      * Greatly improved field parsing including multiple line header fields,
	and reverse parsing of all Internet header information at the bottom of
	VMS MAIL arriving through the Gateway.

      * Improved user interface including the use of multiple rule sets
	within single filter invocations. This allows users to organize their 
	rules into "task-oriented" sets and filter for multiple tasks.

      * Complete rule usage tracking which allows users to identify which 
	rules have been active and which rules have become stale and unused.

      * Miscellaneous Bug Fixes and Feature Enhancements suggested by
	User Feedback.

      * Updated "Getting Started" guide documenting all new features
	including installation instructions. 

If you are interested in reading a "getting started guide" before installation,
the VMS version is in 
	
	XANADU::USER$2:[POST.FILTER.V32]GETTING_STARTED_VMS.PS

while the ULTRIX version is in

	XANADU::USER$2:[POST.FILTER.V32]GETTING_STARTED_ULTRIX.PS

If you are already an OFFICE FILTER user, and would like to examine the
release notes before installation, they are in

	XANADU::USER$2:[POST.FILTER.V32]V32_RELEASE_NOTES.TXT

OFFICE FILTER requires no special privileges for installation on either VMS
or ULTRIX. Total storage used to contain all files and directories, including
PostScript documentation, is approximately 9 MB for ULTRIX and less than 2 MB 
for VMS. No special privileges are required to install the OFFICE FILTER
on either VMS or ULTRIX. All files and directory trees are created within a 
user's login directory.

The OFFICE FILTER can be installed by accessing node XANADU at DECNET address
2.709.

OFFICE FILTER can be newly installed or upgraded on VMS 5.4 or later by 
running the following command at the DCL prompt:

      $ @XANADU::USER$2:[POST.FILTER.V32]OF_VMS_INSTALL

If you are upgrading from a previous VMS version, then the installation creates
new versions of the OFFICE FILTER files described below. You are free to
PURGE any of the previous version files.


The OFFICE FILTER can be installed or upgraded on (RISC) ULTRIX 4.1/UWS 4.1 by
running the following two commands at the csh prompt:

      % dcp xanadu::'user$2:[post.filter.v32]of_risc_install.sh' riscinstal
      % source riscinstal

OFFICE FILTER can be installed or upgraded on (VAX) ULTRIX 3.2/UWS 2.2 by 
running the following two commands at the csh prompt:

      % dcp xanadu::'user$2:[post.filter.v32]of_vaxult_install.sh' vuinstal
      % source vuinstal

If you are upgrading from a previous ULTRIX version, then the installation
overwrites the old executables, the Rule Set demo.rs, and the initialization
script ofinit described below.  It is recommended for safety that you make a 
copy of the previous version's directory tree.  ULTRIX installations requires 
an additional 4.5 MB on /usr/users to PERFORM the installation.  

The OFFICE FILTER installation creates the following directory tree in your
sys$login: (VMS) or $HOME (ULTRIX) directory:

		VMS					ULTRIX
		---					------

    sys$login:					$HOME/
	    |					    |
	    | --- [.FILTER]			    | --- filter/
		       |				    |
		       | --- [.MSGTYPES]		    | --- msgtypes
		       | --- [.RULESETS]		    | --- rulesets
		       | --- [.LOGS]			    | --- logs
		       | --- [.EXE]			    | --- exe
		       | --- [.DOC]			    | --- doc

The "MSGTYPE" sub-directory will contain the file 'msgtype.dat'. This ASCII 
file contains the user/group customizable set of message types available to the 
OFSEND and OFEDIT commands.

The "RULESETS" sub-directory will contain all of your personal rule set files
(ASCII) used for your filtration tasks. It initially contains the rule set 
"DEMO.RS". FOR ULTRIX INSTALLATIONS, THE PREVIOUS VERSION OF DEMO.RS WILL
BE OVERWRITTEN.

The "LOGS" sub-directory will contain all the log files generated by the 
OFFILTER command. It is initially empty.

The "EXE" sub-directory contains all the OFFICE FILTER binaries, .COM, and
.UID files. It will contain the file "OFINIT.COM"(VMS) or "ofinit"(ULTRIX)
which defines the logicals/environment variables and symbols necessary for the 
OFFICE FILTER. FOR ULTRIX INSTALLATIONS, THE PREVIOUS VERSION OF ofinit WILL
BE OVERWRITTEN. It must be run before using any OFFICE FILTER command 
presumably in your "LOGIN.COM" file(VMS) or via "source ofinit"(ULTRIX) in
your .login file.

The "doc" sub-directory contains:

"getting_started.ps" is a brief user's guide describing OFFICE FILTER's 
			operation (in PostScript format). 
"v32_release_notes.txt" is a brief release note documenting differences
			between the previous version.

THESE DOCUMENTS ARE A "MUST READ" BEFORE ATTEMPTING TO USE THE OFFICE FILTER.

The OFFICE FILTER commands described in "GETTING_STARTED.PS" require no special
privileges to be run. 

Finally, there is a public notes conference set up in which OFFICE FILTER 
users and developers share their experiences and technical 
problems/information. It is located at ABBOTT::OFFICE_FILTER. It is strongly
suggested that users at least read, if not participate, in this conference.

This version of the prototype will be the last version released by OSAG AD.
Our successful prototyping efforts have resulted in the transfer of this
project into product engineering. Future product efforts will be building off
of this existing prototype source code base, with a rapid Time to Profitability
the key measure of the development cycle. OSAG AD continues to completely
support all aspects of this prototype. If you have ANY questions or problems 
concerning installation or operation, please contact me at ANY time at 
XANADU::POST or DTN 381-0897. 

Our future prototyping efforts use this filtration technology as a core 
component.  Part of our goal in releasing this prototype is to get extensive 
user feedback.  PLEASE either post in the ABBOTT::OFFICE_FILTER notes 
conference, or send directly to me, any suggestions or bug reports.

Mark J. Post
Principal Engineer
OSAG Advanced Development
XANADU::POST
DTN 381-0897

Would you trust anything that uses "%50" instead of "50%" in its description?

    Sounds like a C printf() format string...
    

Well,  Thanks everyone for the information.  I copied the postscript
document, and in spare time have been trying to figure out if Office
Filter is something I can use.

Meanwhile I notice in 'digital today' (8/26 edition, pg. 2) that 
Terry Sciore has been attempting to solve a related problem by cir-
culating hard copy memos with a list of names attached.  I've noticed
also that our department hasn't quite reached the "paperless" stage
yet.  Maybe some of the old ways were not that bad.  Any other ideas?

Regards,
Chuck

p.s. Re .8, guess I'll have to go to Kernighan and Ritchie on that.
     At least we know that they're not into BASIC-PLUS.  ;-)

    The use of post-script files is also keeping us from heading toward a
    paperless office.  Most of these files cannot be reasonably converted
    into text that I can read on my terminal.  Therefore I have to get hard
    copy.

    Some of them have enough pictures in them that there is no other
    reasonable way to convey the information.  But many of them could just
    as well be written using RUNOFF (or DSR+).

Re .10:

>    The use of post-script files is also keeping us from heading toward a
>    paperless office.  Most of these files cannot be reasonably converted
>    into text that I can read on my terminal.  ...

A-men.  Many of the documents make one wonder whether there's a previewer font
family titled "Crayola".  Trying to read a PostScript mail message yesterday
was so resource-intensive, my workstation wedged and I had to reboot...

A year or two ago a group from a peer cost center sent out a request for phase 0
requirements which stated that only input in the form of flat ASCII mail would
be considered.  Since hardcopy, PostScript and .LN03 files were not manipulable
by the recipients, they would be ignored.  Inspiring.
				/AHM

    Why Postscript?  For the same reason we're forced to use:
    
    VTX ELF  instead of the old/better ELF
    A1 vs VAXmail
    etc.

>    Why Postscript?  For the same reason we're forced to use:
>    
>    VTX ELF  instead of the old/better ELF
>    A1 vs VAXmail
>    etc.

I think they use the word "progress" when justifying things like this.

:(

-steve-

    
    Postscript et al have given us the ability to create the most
    beautiful, eye-catching content-free documents imaginable.
    
    (perhaps I should move this to the "Old DEC vs. New Digital" topic)
    

    Whatever my opinion of ELF may be, I don't think it relates to
    postscript vs runoff:  the new ELF was imposed on us; using postscript
    is voluntary, and anybody who wants to can use runoff at any time.

    re .6
    
    if you're mailing this out to the "world", you ought to correct the
    gramatical/spelling error that starts the 2nd sentence.

    re -1
    
    << if you're mailing this out to the "world", you ought to correct the 
       ^    ^^^                           ^ 
       gramatical/spelling error that starts the the 2nd sentence. >>
          ^
    
    
    Meet me after class finishes.
    
    :-)
    
    John

    Well, why not carry this further ?
    
 << if you're mailing this out to the "world", you ought to correct the 
    ^    ^^^			       ^
    
    The abbreviation "you're" is correct in the usage quoted, and so is
    the non-capitalization of "world".
    
    Scooter
    
    

    Move it to the spelling complaints note!
    
    
         buzz

    Wind your respective necks in !  Frank and I had already moved it to
    mail.
    
    Read the mails if you are interested why you are _still_ wrong.
    
    JOhn