T.R | Title | User | Personal Name | Date | Lines |
---|
2861.1 | Is this easier to answer? | LEMAN::PUNKIE::REGINA | Carrie's in the carrot land | Wed Jun 16 1993 09:36 | 14 |
| Well, maybe I can phrase it even shorter.
Why does neither GOLD-G nor DT RV put at least the partial begin/end control
blocks with the mentionning SIXEL in the file (as it should like said in
STARS)?
How can we put/merge/append/whatever a begin control block in front of the
sixel and an end control block at its end then, dear programming gurus?
Thanks for your help.
Regina
|
2861.2 | Maybe write out one single file using TEXT_FILE? | IOSG::HULIN | Ian Hulin, IOSG: REO, DTN 830-6141 | Wed Jun 16 1993 11:37 | 23 |
| Regina,
You could modify the script to use TEXT_FILE and its subfunctions to open each
of file and construct the WPS-PLUS output file a line at a time, i.e. write the
records starting the control block, append the SIXEL file, then write the
control block end using TEXT_FILE again. I haven't tried this but it should
work.
One question however, why not just do what A1ENCODE does?
>SIXEL<
loads of SIXEL data lines ...
><
Once a file is in this format ALL-IN-1 will happily <LIST it.
Hope this helps,
Cheers,
Ian
|
2861.3 | tks, A1ENCODE modified in V3.0 | GVPROD::JORHAT::BOWERS | | Wed Jun 16 1993 14:52 | 10 |
| haven't tried TEXT_FILE, will do so
A1ENCODE doesn't work properly anymore after ALL-IN-1 V3.0 (cf STARS
article 163564 (?))
A DT RV erases the word SIXEL, and GOLD GET removes the END CONTROL. sigh
which is why we are trying to append an END CONTROL but <LIST works
any other ideas appreciated
Hilary
|
2861.4 | I meant you could use TEXT_FILE to do what A1ENCODE should do | IOSG::HULIN | Ian Hulin, IOSG: REO, DTN 830-6141 | Wed Jun 16 1993 19:12 | 44 |
| Hilary,
�A1ENCODE doesn't work properly anymore after ALL-IN-1 V3.0 (cf STARS
�article 163564 (?))
�A DT RV erases the word SIXEL, and GOLD GET removes the END CONTROL. sigh
�which is why we are trying to append an END CONTROL but <LIST works
�
�any other ideas appreciated
�
I meant something like
TEXT_FILE OPEN Hilary "HILARY.TXT"/WRITE
TEXT_FILE SET TEXT Hilary
TEXT_FILE WRITE Hilary ">SIXEL<"
TEXT_FILE OPEN Sixel "Sixel.Drw"/READ
TEXT_FILE READ Sixel #Sixel_record
GET #Read_Sts = OA$STATUS
.LABEL Sixel_loop
TEXT_FILE RETURN LINE_TYPE #Sixel_record_type
.IF #Sixel_record NES "" AND #Sixel_record_type EQ 7
.THEN
TEXT_FILE SET LINE_TYPE/SIXEL Hilary
TEXT_FILE SET TEXT #Sixel_record Hilary
TEXT_FILE PUT Hilary
.END_IF
TEXT_FILE READ Sixel #Sixel_record
GET #Read_Sts = OA$STATUS
.IF #Sixel_record NES "" AND #Read_status NE 0 THEN .GOTO Sixel_loop
TEXT_FILE SET TEXT Hilary
TEXT_FILE WRITE Hilary "><"
TEXT_FILE CLOSE Sixel
TEXT_FILE CLOSE Hilary
.EXIT
I think you can make it a WPS-PLUS file by using the .WPL extension for
data-set Hilary and writing out a line of type RULER at the start of file.
I don't think WPS-PLUS will handle a control block with an illegal command
in it, but if I'm wrong, let us know,
Cheers,
Ian
|
2861.5 | It's for a fax attachment | LEMAN::PUNKIE::REGINA | Carrie's in the carrot land | Mon Jul 05 1993 10:14 | 18 |
| Ian,
I finally got the procedure working, but the output is no longer sixel and
therefore does not display as graphic.
I couldn't find a line_type/Sixel in the books? Is there anything else that
lets me write a control block begin and end to a file.
We are in fact trying to read and print an attachment that is a fax. We had
to go with sixel, because the DDIF possibility ate too much disk space.
Noone out there who knows how to envelope a sixel file with control blocks?
Noone out there who has another solution for incoming DECfax'es to read and
print?
/rhr
|