Convert to postscript without opening dialog window?

[Soul Forge]

Do you guys know a way to convert files to postscript without opening the acrobat dialog window?

I need to convert hundreds of files daily, but since acrobat keeps popping up, I can't use the VM to change other flows while it's processing.
It's been a week since I'm trying to understand Ghostscript CLI so I could use it instead. But I can't figure out how to make it work and it seems like it will also open windows while it's processing.

[jan_suhr]

Just out of curiosity, why do yo need stoneage PostScript?

[Soul Forge]

Just out of curiosity, why do yo need stoneage PostScript?

Well, we still use print machines that are literally older than me, and we are getting a lot of font problems with those machines.
I opened another post a while back asking for help on what the problem could be and I thought I found a solution while digging the printer's configurations, but no luck there.
Here's the link to the post: viewtopic.php?t=4975

[NEOSA]

Hi !

You should consider look toward callas pdfToolbox in your case : you can output files as Postscript.



You can also try this App :

https://www.enfocus.com/en/appstore/product/pdfprinter

[magnussandstrom]

You can use Ghostscript to convert from PDF to postscript and run it in Switch using Execute Command.

If you are on Windows you can install Ghostscript using Chocolatey: https://community.chocolatey.org/packag ... script.app

[tdeschampsBluewest]

You can also create a droplet with distiller/acrobat, and execute it trough CLI.
This way you won't have any popup, and keep your actual habit/flaws that you had with acrobat.

But i agree with Magnus, Ghostscript in CLI is also a safe bet.

[Soul Forge]

You can use Ghostscript to convert from PDF to postscript and run it in Switch using Execute Command.

If you are on Windows you can install Ghostscript using Chocolatey: https://community.chocolatey.org/packag ... script.app

So, I've been trying to make Ghostscript work. I've never used CLI before, but I was able to make it work through Windows Command Prompt. Though, when I try to use the command through switch it doesn't work.

Multiple of the attempts were made using the %1 and %2 variables. I was able to run the ghostsctipt command, no matter what config I used, it didn't sent the result through Switch again.

So I thought the problem was the path it was using for the output. Now I'm trying to make a script, to make the output be created in the same folder the original job was sent. But for some reason, even though I'm usign quotes to identify the path, Ghostscript is considering the space in the Switch Sever folder as the end of the parameter.



Here' the script I'm running:

Code: Select all

async function calculateScriptExpression(s: Switch, flowElement: FlowElement, job: Job): Promise<string> {
    const jobName: string = job.getName(false);

    let jobPath = String.raw`${await job.get(AccessLevel.ReadOnly)}`;
    jobPath = jobPath.replace(/\\/g, "/");

    const temp: string[] = jobPath.split("/");
    const folderPath: string = `${temp.slice(0, temp.length -1).join("/")}`;
    const modifiedPath: string = `${folderPath}/${jobName}.ps`;

    job.log(LogLevel.Info, `jobPath: "${jobPath}" \n modifiedPath: "${modifiedPath}"`);

    return `-dNOPAUSE -dBATCH -sDEVICE=ps2write -sOutputFile="${modifiedPath}" "${jobPath}"`;
    }

[tdeschampsBluewest]

You went for a really complicated way to do it!

If you have scripting module, and want to execute CLI, i suggest you to create a script element, and to use "cross spawn" library


If you want to use Execute command, it can be sometime tricky, but i think this parameter should work (not in front of my switch at the moment) :

Command or path : Path to Ghostscript exe
Arguments : -dNOPAUSE -dBATCH -sDEVICE=ps2write -sOutputFile="%2" "%1"
Output : File at path
Copy output job : Yes
Output extension : *.ps
Exit code : discard
stdout : discard
stderr : discard
Fail if exit code : disregard exit code

[magnussandstrom]

Here is a working flow. I used the Run Command app in this case.

Command: "C:\path-to-ghostscript\gswin64c.exe" -dSAFER -dBATCH -dNOPAUSE -sDEVICE=ps2write -sOutputFile="[Job.NameProper].ps" "%%InputFilePath%%"

GhostScript - PDF 2 PS.zip

(7.42 KiB) Downloaded 778 times

[Soul Forge]

Hi !

You should consider look toward callas pdfToolbox in your case : you can output files as Postscript.



You can also try this App :

https://www.enfocus.com/en/appstore/product/pdfprinter

I have tried pdfprinter before, but for some reason it does not allow me to set the media properly.

Callas, on the other hand, didn't respond my resseler for us to get a quote.

You can also create a droplet with distiller/acrobat, and execute it trough CLI.
This way you won't have any popup, and keep your actual habit/flaws that you had with acrobat.

But i agree with Magnus, Ghostscript in CLI is also a safe bet.

Took a quick look at that droplets option, but didn't find a way to convert to PS.

Here is a working flow. I used the Run Command app in this case.

Command: "C:\path-to-ghostscript\gswin64c.exe" -dSAFER -dBATCH -dNOPAUSE -sDEVICE=ps2write -sOutputFile="[Job.NameProper].ps" "%%InputFilePath%%"

GhostScript - PDF 2 PS.zip

That worked, but for some reason it didn't allow me to use the Ghostscript exe path. I used only the gswin64c.

Well, in the end the font problem is solved when I convert the pdfs to ps. BUUUUT, unfortunately it won't solve my problem, as there are files that takes 10-30 min just to convert to poscript...

[strataprepress]

Here is a working flow. I used the Run Command app in this case.

Command: "C:\path-to-ghostscript\gswin64c.exe" -dSAFER -dBATCH -dNOPAUSE -sDEVICE=ps2write -sOutputFile="[Job.NameProper].ps" "%%InputFilePath%%"


GhostScript - PDF 2 PS.zip

I tried this yesterday and all I get is a blank 1 page document after I run it through Distiller. There should be 20 pages after it is distilled. I have a folder of the high-res PDF I want to convert to postscript to make it much smaller file size for emailing, going into the Run Command App and then an output folder. Should there be anything else in between the folders and the Run Command App?