forrest@Csa3.LBL.GOV (04/21/88)
We need some way to convert Print Screen output from Vax Stations into something that can be printed on a Postscript laser printer. This must be a common need so maybe someone has already done something about it. Jon Forrest FORREST@LBL.GOV (arpa) FORREST@LBL (bitnet) ...!ucbvax!lbl-csam!forrest (uucp) -------
frei@rubmez.UUCP (Matthias Frei ) (05/17/88)
In article <880420161326.202019aa@Csa3.LBL.Gov>, forrest@Csa3.LBL.GOV writes: > We need some way to convert Print Screen output from Vax Stations > into something that can be printed on a Postscript laser printer. I think DEC provides a program called "render" converting to some printers and plotters. There is a switch to produce postscript-files too. It works for output-files from the demo-program "[vwsdemo]sight", and was running on mVMS 4.3 (I think) with pixel-files too. Now on mVMS 4.5 it stops with an errormessage. DEC said it should be working ... (anybody from DEC reading this ???) It would be interesting, if newer versions do the same mismatch. Here are the commands to test: - create a pixel-file in any directory - type "render pixel_file/device_type=laserwriter/output=postscript_file I hope anybody succeeds ... Matthias Frei -------------------------------------------------------------------- Snail-mail: | E-Mail address: Microelectronics Center | UUCP frei@rubmez.uucp University of Bochum | (...uunet!unido!rubmez!frei) 4630 Bochum 1, P.O.-Box 102143 | West Germany |
WHEELER@CC.UTAH.EDU (05/19/88)
Posting-Version: unknown; site unknown Subject: Re: Sixel to Postscript Converter Wanted I think that the render program can only translate UIS metafiles and can not translate sixel information. I had to write the same type of program to transfer sixel files to imPRESS for our imagen printer. I think you will have to write some code for this one, I couldn't find a way around it. Bob Wheeler Howard Hughes Medical Institute at Salt Lake City BOB%HOWARD@CC.UTAH.EDU
LEICHTER@VENUS.YCC.YALE.EDU ("Jerry Leichter ", LEICHTER-JERRY@CS.YALE.EDU) (05/23/88)
> We need some way to convert Print Screen output from Vax Stations > into something that can be printed on a Postscript laser printer. I think DEC provides a program called "render" converting to some printers and plotters. There is a switch to produce postscript-files too. It works for output-files from the demo-program "[vwsdemo]sight", and was running on mVMS 4.3 (I think) with pixel-files too. Not likely! RENDER is essentially a user interface and central distributor for a set of translators; the arguments you give it let it determine what translator to use, and what detailed data to give that translator. Trans- lators live in SYS$LIBRARY, and have names of the form TRN$from-syntax_to-syntax where from- and to-syntax define the data representation syntaxes to read and write. The only translators I've ever seen have a from-syntax of UIS; they use the HCUIS$ routines to read UIS metafiles, which are essentially stored representations of UIS display lists. The SIGHT program produces such files. Thus, TRN$UIS_PS will translate a SIGHT UIS output to Postscript. To read sixel files, you would need a TRN$SIXEL_something translator. I've never seen one. Now on mVMS 4.5 it stops with an errormessage. WHAT stops? What error message? DEC said it should be working ... (anybody from DEC reading this ???) If you've paid for DEC support, why don't you ask through the channels you have paid to get access to? If you HAVEN'T paid, why do you think someone from DEC should answer you here? It would be interesting, if newer versions do the same mismatch. What "same mismatch"? Is this a reference to the mysterious "error message" you mentioned earlier? Is it perhaps a shared image mismatch? When you updated your system did you update UIS? Did you also update HCUIS? It's a separate kit; RENDER comes as part of HCUIS. Here are the commands to test: - create a pixel-file in any directory - type $ render pixel_file - /device_type=laserwriter/output=postscript_file This hasn't a prayer of working unless "pixel_file" is anything but - the default input data representation is "UIS metafile". At the very least, you would need a /SOURCE_DATA_TYPE=<something> qualifier to specify a non- default input data type - but, as I said, I've yet to see any translators FROM anything but UIS metafile. -- Jerry
WILLIAMS_B@svax05.pcr.co.UK (06/16/88)
After reading Jerry's article, it occurred to me that Render must use the same format translation program as the LN03R symbiont uses... so I tried Render/source=ansi/dev=ln03r/out=login.ps login.com and lo and behold, an almost perfect PS output file from an ansi file. (Almost, because I had to use the wonderful Meadow's FILE utility to convert the file to NOIMPLIEDCC) So I guess if you wrap the appropriate escape codes around it, and you have the LN03R software, you _can_ translate sixel to postscript... Which brings me to a flame for dec salesman (who I am sure _don't_ read this! Uk salesmen anyway...) I complained to my salesman that the LN03R method of translation on the fly was an extra burden on a slow device. The 'R' is advertised as an 8ppm printer... unfortunately it requires about 2 mins to download the stupid form between each job. Add to that the intermediate translation from ansi/regis/tek to postscript and you have queues of users waiting for their output. "Why not have a standalone translator?" I asked? "dunno" the reply. Now I wonder if Render is licensed to run on a cluster.... Brian.