T.R | Title | User | Personal Name | Date | Lines |
---|
3846.1 | Not possible | IOSG::NEWLAND | Richard Newland, IOSG, REO2-G/L2 | Fri Feb 04 1994 10:17 | 23 |
| The EDT editor supports simple ASCII text files which do not provide any way
of storing information other than the text. Consequently it is not
possible to save other information such as format settings in the ASCII
file.
In comparison the WPS-PLUS editor supports WPL files, which have a complex
structure capable of storing text, format settings, rulers, etc., and
therefore format settings can be saved in the .WPL file.
You could create new Handling type similar to STANDARD ASCII which:
o edited the document with EDT
o formatted the document with the WPS-PLUS formatter using one of the
user's set of stored WPS-PLUS print settings.
If you need more information on how to create such a Handling type let me
know.
Richard
|
3846.2 | Yup, I need your help | ANGLIN::CARLSON | | Fri Feb 04 1994 16:27 | 10 |
| I'm just getting back into ALL-IN-1 support from a couple of years ago.
Yup, I could use your help in setting up this handling type. What you
suggest is exactly what the customer wants, to edit in EDT but pick up
the stored print settings.
What about this EDT initialization file, OAUSER:EDTCUSTOM.EDT?
Thanks for your support!
Julie
|
3846.3 | Try this.... | IOSG::NEWLAND | Richard Newland, IOSG, REO2-G/L2 | Fri Feb 04 1994 18:52 | 84 |
| The following script and FORMAT master will create and edit an ASCII
document using the EDT editor, and format the document with the WPS-PLUS
Formatter using the user's #5 saved settings. The script will also be used
when the user reads the document.
The user can set the Handling when the document is created, or use the U
(Update) option to change the handling of an existing document.
My example shows the #5 settings being used but obviously could be modified
to use a different saved settings. Multiple scripts and FORMAT master
entries could be created to support additional saved settings.
Note that it is the user's own #5 settings which are used so the resulting
output file will be different for each user according to their own
settings.
Richard
Use customization management to create a script called WPL_SS5.SCP
!
! WPL_SS5.SCP
!
! WPS-PLUS format file with user's saved #5 print settings
!
get #PRINT_OUTFILE = #PRINT_LISTFILE ".LIS"
format #PRINT_FILE, #PRINT_OUTFILE, #PRINT_DEVICE_TYPE, 5
.if #PRTSET_CHOICE nes '1' then get #PRINT_STATUS = '-1'
.exit
!
! Inputs:
! #PRINT_FILE is the filename to process
! #PRINT_LISTFILE is the 'root' filename for output
! i.e. with no file type
! #PRINT_DEVICE_TYPE WPS-PLUS device type
! #PRINT_STATUS initially set to '1' to indicate success
!
! Outputs:
! #PRINT_OUTFILE is the file specification of the output
! #PRINT_STATUS status of print operation
Create a new FORMAT master entry called 'ASCII WPL #5'
Name: ASCII WPL #5
Description: ASCII -- WPS-PLUS format with user's #5 settings
Revisable (Y/N): Y
Default file type: .TXT
Object default file type:
Text data set (Y/N): Y
Data set name: ASCII
Template filename:
Template form:
Edit function: EDIT OA$CURDOC_FILENAME
Initialization file: EDTCUSTOM.EDT
Purge count: 3
Editor type: EDT
List function:
Print function: DO WPL_SS5.SCP
Always print nofeed (Y/N): N
Always print passall (Y/N): N
Printer level:
WPS-PLUS formatting (Y/N): Y
DCL compile command:
CDA format (Y/N): Y
Front end converter name: TEXT
Back end converter name: TEXT
Converter options file:
|