"James B. Byrne" <[log in to unmask]>  Wrote:
 
>>  UNN vs. NUM controls whether or not line numbers are seen, independent of
>>  the file being a numbered or unnumbered file.  UNN is the default.
>>
>>  RAW vs. unRAW?? controls whether or not data in the file can be interpreted
>>  as line numbers.  RAW means no. unraw?? means yes and is the default.
>>
>>  Lab welcomes your suggestions for an OPTION name opposite to RAW, and
>>  solicits feedback on this proposal. We expect that this enhancement will
>>  be available on 5.0 and 5.5 patches.
>
>My suggestion would be :
>
>PRINT [[FILE=]filename]
>           [[;OUT=]outfile]
>           [[;START=]m]
>           [[;END=]n]
>           [[;PAGE=]p]
>           [;{UNN}]
>             {NUM}
>           [[;FMT=]{B[inary]}]
>                   {A[scii[,"c"|'c']}
>
>Binary = binary stream, no editing by PRINT
>Ascii = printable characters only (default) - non printing characters
replaced by
>optional ,"c" character. If double quote mark is the desired replacement
>character then '"'.
>
>Default is ;FMT=Ascii,"."
>
>Regards,
>Jim
 
 
I tend to agree.  From the description I read in the original posting, RAW
doesn't sound so raw since the "." replaces non-printing characters.  Sounds
"COOKED" to me.  Jim's suggested syntax makes a lot more sense to me, but
then I'm a throwback that uses a couple of UDCs to invoke FCOPY (with $STDIN
and $STDLIST diverted) rather than use PRINT, and use a "TYPE" UDC to invoke
a program that does "cooks" files so that large expanses of blanks in lines
are converted to HP Terminal ESC sequences (<esc>&a+12C  as an example).
 
Just my opinion.
 
John
--------------------------------------------------------------
John Korb                            email: [log in to unmask]
Innovative Software Solutions, Inc.
 
The thoughts, comments, and opinions expressed herein are mine
and do not reflect those of my employer(s), or anyone else.